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 Exam PDII Topic 5 Question 90 Discussion

Actual exam question for Salesforce's Platform Developer II exam
Question #: 90
Topic #: 5
[All Platform Developer II Questions]

Refer to the test method below:

The test method tests an Apex trigger that the developer knows will make a lot of queries when a lot of Accounts are simultaneously updated to be customers.

The test method fails at the Line 20 because of too many SOQL queries.

What is the correct way to fix this?

A.

B.

C.

D.

Show Suggested Answer Hide Answer
Suggested Answer: D

The correct way to fix this is to add Test.startTest() before and add Test.stopTest() after Line 18 of the code. This will reset the governor limits for the code that executes between these two methods, and allow the test to run without hitting the SOQL query limit.The Test.startTest() and Test.stopTest() methods are used to test code that makes a lot of queries or calls asynchronous methods12. By using these methods, the developer can isolate the code that needs more resources and verify that it does not exceed the governor limits.


Using Limits, startTest, and stopTest | Apex Developer Guide | Salesforce Developers

Test.StartTest & Test.StopTest - Salesforce Developer Community

Why would a developer use test startTest and test stopTest in Salesforce? | ForceTalks

by In at May 12, 2024, 08:57 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel
Xuan
3 months ago
Option A? Really? Adding a System.debug statement to the trigger? That's like trying to extinguish a forest fire with a water gun.
upvoted 0 times
...
Val
3 months ago
This is a tricky one, but I think Option D is the best solution. Using @TestVisible to expose the method for testing seems like a clean approach.
upvoted 0 times
Glory
1 months ago
I think Option C might also work, have you considered that?
upvoted 0 times
...
Maryann
2 months ago
I agree, Option D using @TestVisible is the way to go.
upvoted 0 times
...
Odette
2 months ago
I think Option C might also work, have you considered that?
upvoted 0 times
...
Linwood
2 months ago
I agree, Option D using @TestVisible is the way to go.
upvoted 0 times
...
Torie
2 months ago
I haven't tried Option C yet, but I'll give it a shot. Thanks for the suggestion!
upvoted 0 times
...
Viki
2 months ago
I think Option C might also work, have you tried that?
upvoted 0 times
...
Katy
2 months ago
I agree, Option D using @TestVisible is a good solution.
upvoted 0 times
...
...
Yuette
3 months ago
I'd probably go with Option B. Caching the results of the SOQL queries could help reduce the number of queries executed.
upvoted 0 times
Makeda
3 months ago
I agree, Option B seems like the most efficient solution to reduce the number of queries.
upvoted 0 times
...
Tammara
3 months ago
I think Option B is a good choice. Caching the results of the SOQL queries can definitely help.
upvoted 0 times
...
...
Eura
3 months ago
Option C looks like the way to go. Limit the number of SOQL queries and make sure the trigger is optimized for performance.
upvoted 0 times
Jamie
2 months ago
Definitely, Option C is the way to go to fix the issue with too many SOQL queries.
upvoted 0 times
...
Hannah
2 months ago
Option C seems to be the consensus, let's make sure to implement it correctly.
upvoted 0 times
...
Carry
3 months ago
I would go with Option C as well, optimizing the trigger is key.
upvoted 0 times
...
Arthur
3 months ago
Agreed, limiting the number of SOQL queries is crucial for performance.
upvoted 0 times
...
Shawna
3 months ago
I think Option C is the best choice here.
upvoted 0 times
...
...

Save Cancel