Salesforce DEX-450 Exam - Topic 7 Question 66 Discussion

Actual exam question for Salesforce's DEX-450 exam

Question #: 66
Topic #: 7

Universal Containers implemented a private sharing model for the Account object. A custom Account search tool was developed with

Apex to help sales representatives find accounts that match multiple criteria they specify. Since its release, users of the tool report they can see

Accounts they do not own.

What should the developer use to enforce sharing permissions for the currently logged in user while using the custom search tool?

AUse the with sharing keyword on the class declaration.

BUse the without sharing keyword on the class declaration.

CUse the userInfo Apex class to filter all SOQL queries to returned records owned by the logged-in user.

DUse the schema describe calls to determine if the logged-in user has access to the Account object.

Show Suggested Answer

Suggested Answer: B

by Elza at Jan 04, 2023, 07:57 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Lasandra

5 months ago

Isn't there a risk with B? That seems risky for data access.

upvoted 0 times

...

Teddy

6 months ago

A is correct, it enforces the sharing rules properly.

upvoted 0 times

...

Shenika

6 months ago

Surprised they can see accounts they don't own at all!

upvoted 0 times

...

Dorothy

6 months ago

I disagree, I think C makes more sense for filtering.

upvoted 0 times

...

Mignon

6 months ago

Definitely A, using with sharing is the way to go!

upvoted 0 times

...

Raylene

6 months ago

I vaguely recall something about schema describe calls, but I don't think they actually enforce sharing. I feel like the answer has to be related to the sharing keyword.

upvoted 0 times

...

Brock

6 months ago

I think we had a practice question about filtering records based on user permissions. Using userInfo to filter SOQL queries sounds familiar, but I'm not confident it's the best approach here.

upvoted 0 times

...

Ronnie

6 months ago

I'm not entirely sure, but I feel like "without sharing" would allow users to see more records than they should. That doesn't seem right for this scenario.

upvoted 0 times

...

Ardella

6 months ago

I remember we discussed the importance of using the "with sharing" keyword to enforce sharing rules. I think that might be the right choice here.

upvoted 0 times

...

Daisy

7 months ago

Based on my understanding, the Customer Success Manager is the one who works closely with the customer executives to align the purchased solutions with their business goals.

upvoted 0 times

...

Georgene

7 months ago

Definitely A. You can't just start shopping around without knowing your specific needs first. Classic project management approach.

upvoted 0 times

...

Sage

7 months ago

The way I see it, the main purpose is to obtain agreement on the requirements, so I'm going to go with option A. Feels like the most straightforward answer.

upvoted 0 times

...

Lashon

11 months ago

Using without sharing? Bold strategy, Cotton. Let's see if it pays off. Just kidding, that's a hard pass from me. C is the way to go, keep that data safe and sound.

upvoted 0 times

...

Cyril

11 months ago

Option A with sharing? More like 'with no access' amirite? Gotta go with C on this one, my dudes. Keeping that data locked down is the way to go.

upvoted 0 times

Alline

10 months ago

C) Use the userInfo Apex class to filter all SOQL queries to returned records owned by the logged-in user.

upvoted 0 times

...

Rolande

11 months ago

B) Use the without sharing keyword on the class declaration.

upvoted 0 times

...

Freeman

11 months ago

A) Use the with sharing keyword on the class declaration.

upvoted 0 times

...

Jina

12 months ago

Hmm, schema describe calls? That seems a bit overkill for this use case. Why complicate things when you can just use the userInfo class like in Option C? It's a no-brainer.

upvoted 0 times

Micah

11 months ago

C) Use the userInfo Apex class to filter all SOQL queries to returned records owned by the logged-in user.

upvoted 0 times

...

Alline

11 months ago

B) Use the without sharing keyword on the class declaration.

upvoted 0 times

...

In

11 months ago

A) Use the with sharing keyword on the class declaration.

upvoted 0 times

...

Markus

12 months ago

Whoa, without sharing? That's a bold move, but I wouldn't recommend it. Sounds like a security nightmare waiting to happen. Option C is the clear winner here.

upvoted 0 times

Leota

10 months ago

C) Use the userInfo Apex class to filter all SOQL queries to returned records owned by the logged-in user.

upvoted 0 times

...

Stephaine

11 months ago

B) Use the without sharing keyword on the class declaration.

upvoted 0 times

...

Xuan

11 months ago

A) Use the with sharing keyword on the class declaration.

upvoted 0 times

...

Geraldine

1 year ago

Option C sounds like the way to go. Using the userInfo class to filter the SOQL queries ensures that only the records the user has access to are returned. Keeps things simple and secure.

upvoted 0 times

Cyndy

10 months ago

Option C sounds like the way to go. Using the userInfo class to filter the SOQL queries ensures that only the records the user has access to are returned. Keeps things simple and secure.

upvoted 0 times

...

Han

10 months ago

C) Use the userInfo Apex class to filter all SOQL queries to returned records owned by the logged-in user.

upvoted 0 times

...

Alyce

10 months ago

B) Use the without sharing keyword on the class declaration.

upvoted 0 times

...

Estrella

10 months ago

A) Use the with sharing keyword on the class declaration.

upvoted 0 times

...

Bulah

10 months ago

Option C sounds like the way to go. Using the userInfo class to filter the SOQL queries ensures that only the records the user has access to are returned. Keeps things simple and secure.

upvoted 0 times

...