Describe the Ramifications of Field Updates and the Potential for Recursion. PLATFORM-APP-BUILDER Practice Questions (Page 3)

Questions 11–15

1. 11expert · hard

   An organization has a before-update trigger on the Case object that sets a custom field based on the Priority. They also have a workflow rule that updates the Priority field when the custom field is set to a certain value. A user changes the Priority on a Case, and the trigger runs. After the trigger completes, the workflow rule fires and updates the Priority again. What is the order of execution for these actions?

   • AThe workflow rule runs, then the trigger, but the trigger does not run again because workflow field updates do not cause triggers to fire
   • BThe trigger runs first, then the workflow rule, and then the trigger runs again because of the workflow's field update
   • CThe workflow rule runs first, then the trigger, and then the workflow rule runs again
   • DThe trigger runs, then the workflow rule, but the trigger does not run again because it is a before trigger
   Reveal Solution Discussion Select an answer first
2. 12application · medium

   A developer is designing a trigger on the Opportunity object that updates a custom field on the related Account. The developer wants to follow best practices to minimize the risk of recursion. What should the developer do?

   • AUse a workflow rule to update the Account instead of a trigger
   • BUse a static flag to prevent the trigger from processing the same change more than once
   • CUse a future method to update the Account asynchronously
   • DUse the addError method to block the Account update if it would cause recursion
   Reveal Solution Discussion Select an answer first
4. 13application · medium

   A developer is troubleshooting a trigger on the Contact object that updates the Account's AnnualRevenue field. The trigger is causing recursive calls, and after a few iterations, the transaction fails with a 'System.LimitException: Too many SOQL queries: 101'. What is the most likely reason for this failure?

   • AThe Account object has a validation rule that blocks the update, causing the trigger to retry
   • BThe trigger is using a DML operation that is not allowed in a before trigger
   • CThe trigger is using a SOQL query inside a loop, which is a best practice but still causes limits
   • DEach recursive trigger execution is consuming SOQL queries, and the cumulative count exceeds the governor limit
   Reveal Solution Discussion Select an answer first
5. 14foundation · easy

   What is a common way to manage the interaction between workflow field updates and triggers to avoid recursion?

   • ADisable all workflow rules that update fields.
   • BUse a before trigger instead of an after trigger.
   • CUse a different object for the workflow field update.
   • DUse a static flag in the trigger to skip logic when the update comes from a workflow rule.
   Reveal Solution Discussion Select an answer first
6. 15foundation · easy

   What is a best practice to minimize unintended recursion in triggers?

   • AUse a before trigger instead of an after trigger for all logic.
   • BAvoid using triggers altogether and rely only on workflow rules.
   • CUse a different object for all field updates.
   • DUse static flags to ensure the trigger logic runs only once per transaction.
   Reveal Solution Discussion Select an answer first