Salesforce Exam DEX-450 Topic 2 Question 112 Discussion

Actual exam question for Salesforce's DEX-450 exam

Question #: 112
Topic #: 2

[All DEX-450 Questions]

Consider the following code snippet:

As part of the deployment cycle, a developer creates the following test class:

When the test class runs, the assertion fails.

Which change should the developer implement in the Apex test method to ensure the test method executes successfully?

AQuery the Administrator use into memory and enclose lines 15 and 16 within the system,runAs (use); method.

BQuery the Standard User into memory and enclose lines 15 and 16 within the system ,runAs; method.

CAdd @Istest% seeAllDataTrue; to line 12 and enclose lines 15 and 16 within Test .set(Test); and test ste-ptest();.

DAdd System, runAs (Use; to line 14 and enclose line 15 within Test, startTest); and Test ().

Show Suggested Answer

Suggested Answer: D

by Justine at Apr 06, 2025, 10:06 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Oliva

1 months ago

Option A seems a bit excessive, querying the Admin user just to run a simple test? I'd stick with the Standard User approach in option B.

upvoted 0 times

Audra

12 days ago

I think sticking with the Standard User in option B is the way to go.

upvoted 0 times

...

Dalene

28 days ago

Yeah, querying the Admin user for a simple test does seem unnecessary.

upvoted 0 times

...

Margurite

1 months ago

I agree, option B seems like the most straightforward approach.

upvoted 0 times

...

Cyndy

2 months ago

Hmm, this is a tricky one. I'm torn between B and D, but I think I'll go with D. Might as well go all-in with the system calls and test wrappers.

upvoted 0 times

Teddy

28 days ago

User2

upvoted 0 times

...

Annelle

1 months ago

User1

upvoted 0 times

...

Aretha

2 months ago

I'm going to have to go with option D on this one. Enclosing the code within the System.runAs() and Test.start/stopTest() methods seems like the most straightforward approach.

upvoted 0 times

...

Cathrine

2 months ago

But option D doesn't seem to address the issue with the assertion failure.

upvoted 0 times

...

Amie

2 months ago

I disagree, I believe the correct answer is D.

upvoted 0 times

...

Cathrine

2 months ago

I think the correct answer is A.

upvoted 0 times

...

Ronnie

2 months ago

Option C looks interesting with the @IsTest(seeAllData=true) annotation. That might be the easiest solution to bypass any permission issues.

upvoted 0 times

Mee

1 months ago

Yeah, I agree. That annotation should help with any permission problems during testing.

upvoted 0 times

...

Aimee

1 months ago

I think option C is the best choice. It includes the @IsTest(seeAllData=true) annotation.

upvoted 0 times

...

Jody

2 months ago

The code seems to be dealing with permissions, so I think option B is the way to go. Querying the Standard User and running the test as that user should ensure the test passes.

upvoted 0 times

Rosamond

15 days ago

Let's go with option B then. Querying the Standard User seems like the most logical solution.

upvoted 0 times

...

Marguerita

18 days ago

I'm not sure about option A. I still believe option B is the best approach for this scenario.

upvoted 0 times

...

Hayley

19 days ago

But what about option A? Querying the Administrator user and using the system.runAs method could also work.

upvoted 0 times

...

Javier

30 days ago

I think option B is the correct choice. Running the test as the Standard User should solve the issue.

upvoted 0 times

...

Nina

1 months ago

True, enclosing lines 15 and 16 within Test.startTest() and Test.stopTest() is crucial for successful execution.

upvoted 0 times

...

Svetlana

1 months ago

I'm not sure about that. Maybe adding System.runAs(User) on line 14 could be the key.

upvoted 0 times

...

Alayna

2 months ago

But what about adding @Istest(seeAllData=true) to line 12? That could also solve the issue.

upvoted 0 times

...

Bong

2 months ago

I think option B is correct. Querying the Standard User should help with permissions.

upvoted 0 times

...