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

Questions 1–5

1. 1application · medium

   A developer is designing a trigger on the Opportunity object that updates the Account's AnnualRevenue field. The developer is concerned about the trigger causing recursive calls when the Account update triggers other automation. What should the developer consider to minimize the risk of hitting governor limits?

   • AUse a static flag to prevent the trigger from running more than once per transaction
   • BUse a workflow rule to update the Account instead of a trigger
   • CUse a future method to perform the Account update asynchronously
   • DUse the addError method to block the Account update if it would cause recursion
   Reveal Solution Discussion Select an answer first
2. 2foundation · easy

   Which scenario is most likely to cause recursion in a trigger on the Contact object?

   • AThe trigger updates the Description field on the same Contact records that fired the trigger.
   • BThe trigger queries related Accounts and updates their AnnualRevenue.
   • CThe trigger creates a Task record for each Contact.
   • DThe trigger sends an email to the Contact's email address.
   Reveal Solution Discussion Select an answer first
4. 3application · medium

   A developer wrote an Apex trigger on the Account object that updates the AnnualRevenue field. When a user edits an Account record, the trigger runs and updates AnnualRevenue, which causes the trigger to fire again, leading to repeated executions. The developer wants to ensure the trigger only processes the initial update. What should the developer implement?

   • AA workflow rule that updates the AnnualRevenue field instead of the trigger
   • BA recursive call to the trigger using the System.enqueueJob method
   • CA validation rule that prevents the AnnualRevenue field from being updated more than once per day
   • DA static Boolean flag that is set to true after the first execution and checked at the start of the trigger
   Reveal Solution Discussion Select an answer first
5. 4application · medium

   An organization has a workflow rule on the Opportunity object that updates the Stage field when the Amount exceeds $100,000. There is also an Apex trigger on Opportunity that sends an email notification when the Stage changes. After a user updates an Opportunity to meet the workflow criteria, the email is sent multiple times. What is the most likely cause?

   • AThe trigger is using a before update event instead of an after update event
   • BThe trigger is not using the addError method to prevent duplicate emails
   • CThe workflow rule's field update causes the trigger to fire again, and the trigger runs on the updated record, sending the email again
   • DThe workflow rule is configured to evaluate on create and edit, causing it to run twice
   Reveal Solution Discussion Select an answer first
6. 5expert · hard

   A developer is troubleshooting a trigger on the Account object that updates a custom field on all related Contacts. The trigger is recursive and is causing the transaction to fail with a 'System.LimitException: Too many DML operations: 151'. The developer has already added a static flag to prevent recursion, but the issue persists. What is the most likely reason?

   • AThe trigger is using a workflow rule that updates the Account, which bypasses the static flag
   • BThe static flag is not being set correctly, or the trigger is being invoked from a different context that resets the flag
   • CThe trigger is using a future method that runs in a separate transaction, causing the flag to be reset
   • DThe trigger is using a before update event, which does not support static flags
   Reveal Solution Discussion Select an answer first