Exam CRT-450 topic 1 question 173 discussion

Is 2 The ans is 2. Trigger is only before. So during creation will do nothing. 1 create account 2. Workflow increase value to:1 3. It will be treat as a edit 4. Trigger increase to 2. 5. Workflow ignore that change 6. Done

Answer is 3. Update trigger is called twice.

Brauliongon is correct.. I tested this in my playground..

I think it's 3 for the following reason: ... 9. Workflow rules execute 10. If there are workflow field updates, the record is updated again 11. Executes before update triggers and after update triggers, regardless of the record operation (insert or update), one more time (and only one more time) > so in my opinion the trigger is fired 2x (once when the workflow rule updates the record, and again after that. And the process ends there.

The trigger runs in the "before update" event, so it increments the count field by 1. The count field becomes 1. The workflow rule also runs and increments the count field by 1. However, since it's configured to not re-evaluate workflow rules, it doesn't re-run itself. So, it increments the count field based on the initial value, which was 1. Therefore, it becomes 2.

D is the right answer

The question in my opinion is badly worded. The docs for workflow rules provides 3 different evaluation criteria: https://help.salesforce.com/s/articleView?id=sf.workflow_rules_define.htm&type=5 But the question says that the workflow rule is configured on create and update fields events with the latter type of event configured to not fire the workflow rule a second time. So according to options on the docs, the workflow rule in reality it's configured to fire only on creation. The order of execution, https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_triggers_order_of_execution.htm, gives priority to triggers and then to workflow rules. In this case the first event is a record creation event so the trigger won't run since it's a before update trigger. So, workflow rule runs the first time on creation incrementing the field value to 1. This fires an update event that causes the before trigger to run hence incrementing the field value to 2. The workflow rule though ignores this update event, so the final field value remains 2.

I think the correct answer is 3. I tested in an org. The explanation: - starting with count=0; - According the order of execution, before triggers are the first to run, so count = 1; - Workflow are the next execution to run, so count = 2; - but, when evaluting workflows, the triggers are executed again, so count = 3; - the execution finishes once there is no more to do and the re-evaluate workflow is not checked. so the count will be 3

The value of the count field if an Account is inserted with an initial value of zero, assuming no other automation logic is implemented on the Account, would be: C. 4 Here's the explanation: When the Account is inserted, the workflow rule increments the count field once, making it 1. Since the workflow rule is configured to not re-evaluate workflow rules, the trigger on the before update event is not fired during the initial insert. Now, if the Account is updated, the workflow rule increments the count field again, making it 2. At this point, the trigger on the before update event is fired, and it increments the count field once more, resulting in a final value of 3. However, the workflow rule does not re-evaluate during this update, so it does not increment the count field again. Therefore, the count field would have a value of 4 (initial value of 0 + 1 + 2 + 1 from the trigger) if an Account is inserted with an initial value of zero, assuming no other automation logic is implemented on the Account.

Agree should be 2

Right Answer is 2 ! Explanation: On insertion of new record workflow rule will run and make count to 1 ( before update trigger won't run as it's an insertion). After the workflow rule before update trigger will run and make this count to 2 and it will again comeback to workflow rule but this time due to given logic it won't re-evaluate the count and then execution will finish with count as 2 only.

2 is correct imho

Answer should be 3 (trigger fires one time and workflow fires twice on create and on update) Initially Account is created and inserted hence value becomes 1 Then the update trigger fires and value becomes 2 At last the workflow rule again fires for update and the count becomes 3

Why answer is 3 ? It's not before insert/update.