Salesforce
PDII · Question #45
An org has a requirement that an Account must always have one and only one Contact listed as Primary. So selecting one Contact will de-select any others. The client wants a checkbox on the Contact…
The correct answer is D. Write a single trigger on Contact for both after update and before update and callout to helper. See the full explanation below for the reasoning.
Question
An org has a requirement that an Account must always have one and only one Contact listed as Primary. So selecting one Contact will de-select any others. The client wants a checkbox on the Contact called 'Is Primary' to control this feature. The client also wants to ensure that the last name of every Contact is stored entirely in uppercase characters. What is the optimal way to implement these requirements?
Options
- AWrite an after update trigger on Contact for the Is Primary logic and a separate before update
- BWrite a Validation Rule on the Contact for the Is Primary logic and a before update trigger on
- CWrite an after update trigger on Account for the Is Primary logic and a before update trigger on
- DWrite a single trigger on Contact for both after update and before update and callout to helper
How the community answered
(24 responses)- A17% (4)
- B8% (2)
- C4% (1)
- D71% (17)
Community Discussion
No community discussion yet for this question.