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 Platform Developer II Topic 2 Question 107 Discussion

Actual exam question for Salesforce's Platform Developer II exam
Question #: 107
Topic #: 2
[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 Carol at Dec 07, 2024, 01:19 PM

Limited Time Offer

25%

Off

Get Premium Platform Developer II Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Claribel
2 months ago
I will go with Option C then, thanks for the suggestion Zona.
upvoted 0 times
...
Zona
2 months ago
I believe Option C might be the solution to fix this issue.
upvoted 0 times
...
Rickie
2 months ago
I'm leaning towards Option C. Reducing the number of queries by using the @TestSetup annotation sounds like a solid approach. Let's see if it works!
upvoted 0 times
Boris
24 days ago
Let's update the test method with Option C and run it to see if it fixes the issue.
upvoted 0 times
...
Bobbie
28 days ago
I agree, using @TestSetup to reduce queries seems like the way to go.
upvoted 0 times
...
Dannie
1 months ago
I think Option C is a good choice too. Let's give it a try.
upvoted 0 times
...
...
Elke
2 months ago
Option A seems a bit too simple, but sometimes the simplest solution is the best. I'll keep it in mind.
upvoted 0 times
...
Isabella
2 months ago
I agree with Claribel, optimizing the queries will reduce the number of queries made.
upvoted 0 times
...
Lavina
2 months ago
Haha, Option D is like saying 'If you can't beat 'em, join 'em!' Increasing the limit? Bold strategy, let's see if it pays off.
upvoted 0 times
Corinne
17 days ago
Isadora: Corinne, you make a good point. Option C it is.
upvoted 0 times
...
Lorriane
19 days ago
User 3: Lorriane, I agree. Option D seems risky.
upvoted 0 times
...
Isadora
1 months ago
User 2: Isadora, I think Option C might be a better approach.
upvoted 0 times
...
Cyril
2 months ago
User 1: Haha, Option D is interesting.
upvoted 0 times
...
...
Lorean
2 months ago
Hmm, I'm not sure if Option B is the best choice. Isn't that just deleting the trigger altogether? Seems like a bit of an overkill.
upvoted 0 times
Robt
1 months ago
You might be right. Option B does seem a bit extreme. Option C could be the way to go.
upvoted 0 times
...
Leota
2 months ago
I think Option C might be a better solution. It looks like it's optimizing the queries instead of just deleting the trigger.
upvoted 0 times
...
...
Veda
2 months ago
Option C looks promising, it uses the @TestSetup annotation to create the test data. Worth a try!
upvoted 0 times
Brett
1 months ago
Let's go with Option C then and see if it resolves the issue with too many SOQL queries.
upvoted 0 times
...
Destiny
1 months ago
I agree, it helps in optimizing the test execution by creating common test data only once.
upvoted 0 times
...
Miesha
2 months ago
Yes, @TestSetup is a good way to reduce the number of queries in test methods.
upvoted 0 times
...
Erick
2 months ago
Option C looks promising, it uses the @TestSetup annotation to create the test data. Worth a try!
upvoted 0 times
...
...
Claribel
3 months ago
I think the correct way to fix this is by optimizing the SOQL queries.
upvoted 0 times
...

Save Cancel