Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam Advanced-Administrator Topic 7 Question 80 Discussion

Actual exam question for Salesforce's Salesforce Certified Advanced Administrator exam
Question #: 80
Topic #: 7
[All Salesforce Certified Advanced Administrator Questions]

The administrator at Cloud Kicks noticed that a before trigger, which handles saving the original version of a record to an external database, fails. However, a flow configured for fast field updates runs successfully.

How should the administrator advise the developer?

Show Suggested Answer Hide Answer

Contribute your Thoughts:

Raymon
2 months ago
Could the code be causing duplicates in the archive?
upvoted 0 times
...
Hayley
2 months ago
That's a good point. The developer should check on that.
upvoted 0 times
...
Sabra
2 months ago
Ahh, I see what's going on. The developer must have forgotten to turn off their 'Accidental Duplicate Creator' mode in the code.
upvoted 0 times
...
Sommer
2 months ago
Hmm, I'm going with D. The trigger might be trying to create duplicates in the archive, which is causing the issue.
upvoted 0 times
Haley
1 months ago
D) The code could be trying to create duplicates in the archive when it is unable to.
upvoted 0 times
...
Raul
1 months ago
A) Record-triggered flows that are configured to run before save execute prior to all before triggers.
upvoted 0 times
...
...
Bonita
2 months ago
I think C is the answer. The developer is probably saving the data to the wrong place in the external archive.
upvoted 0 times
...
Jerrod
3 months ago
Nah, it's gotta be B. The validation rule is probably messing with the trigger's ability to save the record.
upvoted 0 times
Omer
2 months ago
B) A validation rule could be preventing records from ever meeting the conitions in the trigger.
upvoted 0 times
...
Lisbeth
2 months ago
A) Record-triggered flows that are configured to run before save execute prior to all before triggers.
upvoted 0 times
...
...
Rutha
3 months ago
The trigger might be trying to write to the wrong place in the external database.
upvoted 0 times
...
Pa
3 months ago
I'm pretty sure it's option A. The flow runs first, before the trigger, so that's why the trigger is failing.
upvoted 0 times
Edward
2 months ago
A) I agree, the flow running before the trigger could be causing the issue.
upvoted 0 times
...
Kami
2 months ago
B) A validation rule could be preventing records from ever meeting the conitions in the trigger.
upvoted 0 times
...
Terrilyn
2 months ago
A) Record-triggered flows that are configured to run before save execute prior to all before triggers.
upvoted 0 times
...
...
Hayley
3 months ago
That could be a possibility. It might be conflicting with the trigger.
upvoted 0 times
...
Raymon
3 months ago
Maybe the validation rule is causing the problem.
upvoted 0 times
...
Hayley
3 months ago
I think the trigger failing is a big issue.
upvoted 0 times
...
Janine
4 months ago
The code might be trying to create duplicates in the archive
upvoted 0 times
...
Izetta
4 months ago
Could the trigger be writing data to the wrong place?
upvoted 0 times
...
Camellia
4 months ago
Maybe there's a validation rule causing issues with the trigger
upvoted 0 times
...
Dona
4 months ago
I think the flow runs successfully because it executes after all before triggers
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