Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam Platform Developer I Topic 1 Question 102 Discussion

Actual exam question for Salesforce's Platform Developer I exam
Question #: 102
Topic #: 1
[All Platform Developer I Questions]

A developer identifies the following triggers on the Expense __c object:

The triggers process before delete, before insert, and before update events respectively.

Which two techniques should the developer implement to ensure trigger best practices are followed?

Choose 2 answers

Show Suggested Answer Hide Answer
Suggested Answer: A, D

Contribute your Thoughts:

Clorinda
2 months ago
D is the winner! Keeping the triggers lean and mean is the hallmark of a true Salesforce ninja.
upvoted 0 times
Melita
23 days ago
Using helper classes for logic execution is also a good practice. But D is definitely the winner here.
upvoted 0 times
...
Francoise
1 months ago
I agree, keeping triggers lean and mean is key. D is the winner!
upvoted 0 times
...
Alpha
1 months ago
D is definitely the way to go. Flow for delete action is a game changer.
upvoted 0 times
...
...
Cathrine
2 months ago
C is a big no-no. Putting all the logic in a single trigger is a recipe for disaster. Triggers should be focused and specific.
upvoted 0 times
Crissy
1 months ago
C is a big no-no. Putting all the logic in a single trigger is a recipe for disaster. Triggers should be focused and specific.
upvoted 0 times
...
Fredric
2 months ago
B) Create helper classes to execute the appropriate logic when a record is saved.
upvoted 0 times
...
Scarlet
2 months ago
A) Unify all three triggers in a single trigger on the expense__c object that includes all events.
upvoted 0 times
...
Dion
2 months ago
A) Unify all three triggers in a single trigger on the expense__c object that includes all events.
upvoted 0 times
...
Isabelle
2 months ago
B) Create helper classes to execute the appropriate logic when a record is saved.
upvoted 0 times
...
...
Madelyn
3 months ago
B is the choice for the lazy developer - let Flow do all the work while you sip your coffee!
upvoted 0 times
...
Audria
3 months ago
Option D is the way to go. Separating the trigger logic into helper classes is a best practice to keep the triggers clean and maintainable.
upvoted 0 times
Ricki
1 months ago
B) Unify the before insert and before update triggers and use Flow for the delete action.
upvoted 0 times
...
Leonida
2 months ago
A) Create helper classes to execute the appropriate logic when a record is saved.
upvoted 0 times
...
Rosendo
2 months ago
D) Maintain all three triggers on the Expense__c object, but move the Apex logic out of the trigger definition.
upvoted 0 times
...
...
Elena
3 months ago
I think we should also consider moving the Apex logic out of the trigger definition.
upvoted 0 times
...
Karima
3 months ago
I agree with Karon, it will help us follow best practices.
upvoted 0 times
...
Karon
3 months ago
I think we should create helper classes for better organization.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77