Discuss Salesforce DEX-450 Exam Topic 4 Question 100

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.

Suggested Answer: A

Get Premium DEX-450 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

36 comments · newest first

Dulce 11 months ago

Adding a LIMIT clause seems like a quick fix, but is it really the best solution?

Burma 11 months ago

Wait, can a trigger really handle that many updates without hitting limits?

Cornell 12 months ago

Not sure if moving to a Queueable class is necessary, though.

Gail 12 months ago

I think option C is the best way to handle this.

Elke 1 year ago

Sounds like a classic bulk processing issue!

Jacki 1 year ago

I feel like just iterating over the assets in the for loop might not be efficient enough, but I can't recall if that's a good strategy in this case.

Ronnie 1 year ago

This question reminds me of a similar practice one where we had to optimize a trigger. I think moving logic to a Queueable class could really help here.

Lashawn 1 year ago

I'm not entirely sure, but I think adding a LIMIT clause might just mask the issue instead of solving it.

Ressie 1 year ago

I remember we discussed how bulk processing is crucial to avoid governor limits, so option C seems like a good approach to handle this.

Maxima 1 year ago

This seems straightforward to me. Option A looks like the best solution - we can process all Accounts in one call and avoid the limit issues.

Denae 1 year ago

I'm a bit confused by the code and the options. I'll need to spend some time really understanding what's going on before I can decide on the best solution.

Bulah 1 year ago

Okay, let me think this through. The issue seems to be that the nightly integration is failing due to limit issues, so we need to optimize the code to handle more Accounts and Assets at once. I'm leaning towards Option A or C.

Annalee 1 year ago

Hmm, I think the key here is to find a way to reduce the number of SOQL queries and DML operations to avoid hitting governor limits. Option B or C might be the way to go.

Madalyn 1 year ago

This looks like a tricky one. I'll need to carefully read through the code and the options to figure out the best approach.

Wilda 1 year ago

But wouldn't a primary risk be the original one? This is confusing—I just want to make sure I get this right!

Solange 2 years ago

Option A is just asking for trouble. Trying to process all Accounts in one call? That's just begging for a governor limit exception.

Tegan 2 years ago

↳ replying to Solange

Yeah, Option A sounds like a disaster waiting to happen. Processing all Accounts at once is a sure way to hit governor limits.

Jess 2 years ago

↳ replying to Solange

I agree, breaking up the processing into smaller chunks will help prevent limit failures. Option A is too risky.

Jina 2 years ago

↳ replying to Solange

Option A is definitely risky. It's better to process the Accounts in smaller batches to avoid hitting governor limits.

Colette 2 years ago

Haha, this question is a real head-scratcher. I'm just glad I'm not the one who has to figure it out!

Sherita 2 years ago

I think moving all the logic to a Queueable class and calling it from the trigger could also be a good option.

Agustin 2 years ago

D is the way to do it! Iterating over the Assets list directly is the most straightforward approach in my opinion.

Krystina 2 years ago

↳ replying to Agustin

Let's go with option D then, hopefully it will fix the issue with the bulk updates.

Geraldine 2 years ago

↳ replying to Agustin

That makes sense, it should help address the failure with the nightly integration.

Blair 2 years ago

↳ replying to Agustin

Agreed, iterating over the Assets list directly seems like the way to go.

Josephine 2 years ago

↳ replying to Agustin

I think D is the best option too. It's the most straightforward approach.

Bernadine 2 years ago

I agree with Viola, changing the code to process all Accounts in one call seems like the best solution.

Marcelle 2 years ago

I'd go with option B. Limiting the number of Assets queried per Account is a simple and effective solution.

Marjory 2 years ago

↳ replying to Marcelle

Let's hope it solves the issue.

Vicky 2 years ago

↳ replying to Marcelle

It should help with the limit failures during the nightly integration.

Precious 2 years ago

↳ replying to Marcelle

That sounds like a good idea.

Leigha 2 years ago

↳ replying to Marcelle

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

Viola 2 years ago

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

Dino 2 years ago

Option C seems like the way to go. Queueable classes are perfect for handling bulkier operations like this without hitting limits.

Cheryl 2 years ago

↳ replying to Dino

Yes, it's a good choice to avoid hitting limits.

Brittani 2 years ago

↳ replying to Dino

I agree, Queueable classes are great for bulk operations.

Salesforce DEX-450 Exam - Topic 4 Question 100 Discussion