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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Salesforce Certified Platform Developer II (Plat-Dev-301) Exam - Topic 11 Question 32 Discussion

Universal Containers has an existing automation where a custom record called Account Plan is created upon an Account being marked as a Customer. Recently, a Workflow Rule was added so that whenever an Account is marked as a Customer, a 'Customer Since' date field is updated with today's date.Now, since the addition of the Workflow Rule, two Account Plan records are created whenever the Account is marked as a Customer.What might cause this to happen?
C) The Workflow Rule responsible for the record creation fires twice because the 'Customer Since' field Update Is marked as 'Re-evaluate Workflow Rules After Field Change
A) The Apex Trigger responsible for the record creation is not bulk sate and calls insert inside of a for loop.
B) The Apex Trigger responsible for the record creation does not use a static variable to ensure It only fires once.
D) The Process Builder responsible for the record creation fires before and after the Workflow rule.

Salesforce Certified Platform Developer II (Plat-Dev-301) Exam - Topic 11 Question 32 Discussion

Actual exam question for Salesforce's Salesforce Certified Platform Developer II (Plat-Dev-301) exam
Question #: 32
Topic #: 11
[All Salesforce Certified Platform Developer II (Plat-Dev-301) Questions]

Universal Containers has an existing automation where a custom record called Account Plan is created upon an Account being marked as a Customer. Recently, a Workflow Rule was added so that whenever an Account is marked as a Customer, a 'Customer Since' date field is updated with today's date.

Now, since the addition of the Workflow Rule, two Account Plan records are created whenever the Account is marked as a Customer.

What might cause this to happen?

Show Suggested Answer Hide Answer
Suggested Answer: C

by Gladys at May 05, 2022, 07:01 AM

Limited Time Offer

25%

Off

Get Premium Salesforce Certified Platform Developer II (Plat-Dev-301) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Van
7 months ago
Option B could also be a reason, but I lean towards C.
upvoted 0 times
...
Stevie
7 months ago
I agree with C, but I’m surprised it wasn’t caught earlier!
upvoted 0 times
...
Tess
7 months ago
Wait, are we sure it's not the Apex Trigger causing this?
upvoted 0 times
...
Luis
8 months ago
I think it's definitely option C. That re-evaluation can cause issues.
upvoted 0 times
...
Janae
8 months ago
Sounds like a classic case of double-triggering.
upvoted 0 times
...
Desmond
8 months ago
I wonder if the Process Builder is involved somehow. I vaguely recall that it can run before or after other automation, but I’m not confident about the order of execution.
upvoted 0 times
...
Shakira
8 months ago
I feel like I've seen a similar question before where the static variable was the key to preventing multiple triggers. Could that be the issue here too?
upvoted 0 times
...
Gearldine
8 months ago
I'm not entirely sure, but I think if the Apex Trigger isn't bulk-safe, it could lead to unexpected behavior. I need to double-check that concept.
upvoted 0 times
...
Ruthann
8 months ago
I remember studying how Workflow Rules can trigger multiple times, especially if they're set to re-evaluate after a field change. That might be what's happening here.
upvoted 0 times
...
Layla
8 months ago
Okay, I think I've got this. Based on the key vault information, the correct answer is Key1 only. I'll make sure to read the question carefully and select the right option.
upvoted 0 times
...
Josphine
8 months ago
This seems like a straightforward network design question. I'll need to carefully consider the requirements around NAS failover and securing against malicious threats.
upvoted 0 times
...

Save Cancel