Business Logic and Process Automation Flashcards
A dev wants to create a formula field that calculates the number of days between the “Close Date” and “Created Date” of an Opp. Which function should be used in the formula field?
DATEVALUE()
Question: Which of the following is true about validation rules during lead conversion?
A) Validation rules are ignored during lead conversion.
B) Validation rules only run on the lead object, not on related objects.
C) Validation rules on the Account, Contact, or Opportunity objects can prevent lead conversion.
D) Lead conversion always ignores validation rules for performance reasons.
C) Validation rules on the Account, Contact, or Opportunity objects can prevent lead conversion.
Explanation: Validation rules run on all objects involved in lead conversion. If a validation rule exists on the Account, Contact, or Opportunity, it can block the process.
Question: When a record is updated, which is the correct order of execution?
A) Before triggers → Workflow rules → After triggers → Roll-up summary recalculation → Commit
B) Before triggers → After triggers → Workflow rules → Roll-up summary recalculation → Commit
C) Before triggers → After triggers → Workflow rules → Commit → Roll-up summary recalculation
D) Before triggers → Workflow rules → After triggers → Commit → Roll-up summary recalculation
Answer: B) Before triggers → After triggers → Workflow rules → Roll-up summary recalculation → Commit
Question: A Process Builder process updates a field on the Contact object, which triggers another Process Builder process on the Account object. What is a possible consequence?
A) Process Builder does not allow cross-object references.
B) An error will occur due to a recursive loop.
C) The process will execute successfully without issues.
D) The process will fail due to governor limits.
B) An error will occur due to a recursive loop.
Explanation: If updates trigger another process in a loop, Salesforce prevents excessive recursion, leading to an error.
Question: A Screen Flow updates three different objects in one transaction. What happens if the third update fails?
A) The first two updates remain, and the third update fails.
B) All updates are rolled back, and an error is displayed.
C) The flow retries the update three times before stopping.
D) The flow completes, but an error is logged for the third update.
nswer: B) All updates are rolled back, and an error is displayed.
Explanation: Flows follow a single transaction model, meaning if any update fails, all previous updates in that transaction are rolled back.
- Approval Process and Record Locking
What happens when a record enters an approval process?
A) The record becomes read-only for all users, including administrators.
B) The record is locked for non-admin users until approval is complete.
C) The record can still be edited by anyone with the Modify All permission.
D) The record is locked only for users who do not have Edit access.
✅ Answer: B) The record is locked for non-admin users until approval is complete.
Explanation: When a record is in an approval process, Salesforce locks it for all users except those with the Modify All Data permission.
Default Actions in Flow
A flow is set up to run when a user updates a Case record. The flow should only execute if the case status is changed to Closed. How should you implement this?
A) Use a decision element to check the new status before proceeding.
B) Add an entry condition in Process Builder.
C) Use a record-triggered flow with a filter condition on Status = ‘Closed’.
D) Use an approval process to control the flow execution.
✅ Answer: C) Use a record-triggered flow with a filter condition on Status = ‘Closed’.
Explanation: Record-triggered flows can run immediately upon a record update and filter based on field conditions.
- Custom Roll-Up Summary Field Limitation
Which of the following scenarios cannot be achieved using a declarative roll-up summary field?
A) Counting the number of open opportunities related to an account.
B) Summing the total amount of all won opportunities related to an account.
C) Calculating the average value of all cases related to an account.
D) Rolling up data from a child object in a lookup relationship.
- Custom Roll-Up Summary Field Limitation
✅ Answer: D) Rolling up data from a child object in a lookup relationship.
Explanation: Roll-up summary fields only work for Master-Detail relationships, not Lookup relationships.
- Cross-Object Formula Field Limitations
You need to create a cross-object formula field on the Case object that pulls in the Account Rating field from the related Account object. What limitation should you be aware of?
A) Formula fields cannot reference lookup relationships.
B) Cross-object formulas can only reference parent fields, not child records.
C) Formula fields do not support picklist values from related objects.
D) This is not possible without an Apex trigger.
✅ Answer: B) Cross-object formulas can only reference parent fields, not child records.
Explanation: Formula fields can reference fields from a parent object but not aggregate data from child records.
- Process Builder Bulk Handling
Which of the following is a best practice when configuring Process Builder to handle bulk record updates?
A) Use ISNEW() and ISCHANGED() to minimize unnecessary executions.
B) Always include a scheduled action to prevent bulk failures.
C) Use record-triggered flows instead, as Process Builder does not handle bulk operations.
D) Process Builder is optimized for bulk operations and does not require additional handling.
✅ Answer: A) Use ISNEW() and ISCHANGED() to minimize unnecessary executions.
Explanation: ISNEW() and ISCHANGED() prevent unnecessary execution of logic in bulk updates.
- Field Updates in Approval Processes
Which field update behavior is expected when a record is in an approval process?
A) Field updates from workflow rules override approval process field updates.
B) Field updates in an approval process bypass validation rules.
C) Field updates in approval processes do not trigger workflow rules.
D) Approval process field updates execute after record save.
Answer: C) Field updates in approval processes do not trigger workflow rules.
Explanation: Approval process field updates do not trigger workflow rules to prevent unnecessary loops.
- Auto-Response Rules and Process Automation
A company wants to send an auto-response email when a new case is created, but only if the case origin is Email. How should this be implemented?
A) Create an Auto-Response Rule with a condition for Case Origin = Email.
B) Use a Workflow Rule to send an email alert when a case is created.
C) Configure an Email-to-Case forwarding rule.
D) Use a Process Builder process to trigger an email alert.
- Auto-Response Rules and Process Automation
✅ Answer: A) Create an Auto-Response Rule with a condition for Case Origin = Email.
Explanation: Auto-response rules are designed to send email notifications based on case criteria automatically.
- Looping Considerations in Flow
A Flow is set to loop over a collection of Opportunity Line Items and update them. What is the main limitation to consider?
A) Each iteration of the loop counts as a separate DML statement.
B) Flow loops cannot modify records directly.
C) Salesforce limits the number of iterations to 10.
D) Flow loops can only iterate over a maximum of 200 records.
- Looping Considerations in Flow
✅ Answer: A) Each iteration of the loop counts as a separate DML statement.
Explanation: Flow loops execute DML operations separately, which can hit governor limits.
- Record-Triggered Flow vs. Apex Trigger
Which scenario would require an Apex Trigger instead of a record-triggered flow?
A) Sending an email when a record is updated.
B) Updating a parent record when a child record is inserted.
C) Implementing complex recursive logic with multiple DML operations.
D) Creating a new related record based on a field value.
- Record-Triggered Flow vs. Apex Trigger
✅ Answer: C) Implementing complex recursive logic with multiple DML operations.
Explanation: Apex Triggers are better suited for complex recursion and multiple related record updates.
- Future Actions in Process Automation
Which automation tool allows you to schedule a future action without requiring a user-defined time field?
A) Workflow Rule Time-Dependent Actions
B) Approval Process Actions
C) Scheduled Actions in Process Builder
D) Scheduled Flows
- Future Actions in Process Automation
✅ Answer: C) Scheduled Actions in Process Builder
Explanation: Scheduled actions in Process Builder allow future execution without a time field.
