An Apex trigger creates a Contract record every time an Opportunity record is marked as Closed end Won. This trigger is working great, except (due to a recent acquisition) historical Opportunity records need to be loaded into the Salesforce instance.
When a test batch of records are loaded, the Apex trigger creates Contract records. A developer is tasked with preventing Contract records from being created when mass loading the Opportunities, but the daily users still need to have the Contract records created.
What is the most extendable way to update the Apex trigger to accomplish this?
A. Use a List Custom Setting to disable the trigger for the user who loads the data.
B. Add a Validation Rule to the Contract to prevent Contract creation by the user who loads the data.
C. Use a Hierarchy Custom Setting to skip executing the logic inside the trigger for the user who loads the data.
D. Add the Profile ID of the user who loads the data to the trigger so the trigger will not fire for this user.
How To Pass Certified Platform Developer II Exam?Certified Platform Developer II PDF dumps.High quality Certified Platform Developer II pdf and software. VALID exam to help you pass. |
 |
|
Download Printable PDF. VALID exam to help you PASS. |
|