Salesforce Exam PDI Topic 3 Question 90 Discussion

Actual exam question for Salesforce's Platform Developer I exam

Question #: 90
Topic #: 3

A developer deployed a trigger to update the status__c of Assets related to an Account when the Account''s status changes and a nightly integration that updates Accounts in bulk has started to fail with limit failures.

What should the developer change about the code to address the failure while still having the code update all of the Assets correctly?

AChange the gerAssetsToUpdac= method to process all Accounts in one call and call it outside of the for loop that starts on line 03.

BAdd a LIMIT clause to the SOQL query on line 16 to limit the number of Assets queried for an Account.

CMove all of the logic to a Queueable class that queries for and updates the Assets and call it from the trigger.

DAdd List<Asset> assets = [SELECT Id, Status__c FROM Asset WHERE AccountId = :acctId] to line 14 and iterate over the assets list in the for loop on line 15.

Show Suggested Answer

Suggested Answer: A

by Carlee at Jun 01, 2024, 01:58 PM

Limited Time Offer

25%

Off

Get Premium PDI Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Margot

3 months ago

Hmm, I was thinking B at first, but C makes a lot of sense. Limit clauses can only take you so far, might as well go for the Queueable solution.

upvoted 0 times

Chu

2 months ago

Definitely, Queueable classes are designed for handling bulk operations like this. It's the way to go.

upvoted 0 times

...

Sheridan

2 months ago

Yeah, B might help in the short term, but C is a more scalable solution in the long run.

upvoted 0 times

...

Cecilia

2 months ago

I agree, C seems like the best option here. Queueable classes can handle bulk processing much more efficiently.

upvoted 0 times

...

Belen

3 months ago

I'm going to go with C as well. Gotta love that Queueable class - it's like the secret weapon for handling big data loads!

upvoted 0 times

...

Luisa

3 months ago

D is an interesting idea, but it might not scale well as the number of Assets grows. C is probably the cleanest approach.

upvoted 0 times

...

Marjory

3 months ago

I agree, C seems to be the most efficient solution. Splitting the work into a separate process is a smart move.

upvoted 0 times

...

Barrie

3 months ago

Option C looks like the best choice here. Offloading the bulk processing to a Queueable class should help avoid the limit issues.

upvoted 0 times

Kirk

2 months ago

Yes, that way the trigger won't be affected by the bulk processing limits.

upvoted 0 times

...

Amie

2 months ago

I agree, moving the logic to a Queueable class sounds like a good solution.

upvoted 0 times

...

Casie

2 months ago

Yeah, that way the trigger won't be affected by the bulk processing limits.

upvoted 0 times

...

Enola

2 months ago

I agree, moving the logic to a Queueable class seems like the best solution.

upvoted 0 times

...

Latrice

2 months ago

Let's go with option C then, it seems like the most efficient way to handle this.

upvoted 0 times

...

Doyle

2 months ago

That's a good point, it should help with the limit failures.

upvoted 0 times

...

Annalee

2 months ago

I agree, moving the logic to a Queueable class seems like the best solution.

upvoted 0 times

...

Colene

3 months ago

I agree with you, that way the code can update all Assets correctly without hitting limits.

upvoted 0 times

...

Merri

3 months ago

I think the developer should change the code to process all Accounts in one call.

upvoted 0 times

...