Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam Sharing and Visibility Architect Topic 3 Question 38 Discussion

Actual exam question for Salesforce's Sharing and Visibility Architect exam
Question #: 38
Topic #: 3
[All Sharing and Visibility Architect Questions]

Universal Containers (UC) uses a custom Lightning component with an Apex class to display shipment information (custom object, Private organization-wide default). UC sales managers are complaining about two important points: Shipment records that belong to their teams can be seen by other users. Shipment amount should be visible only by managers, but sales reps are able to view it.

Which feature did the development team miss that is causing the problems?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Marion
1 months ago
Wait, they're not using the 'isAwesome()' method? Clearly, the development team needs to brush up on their coding skills. Option D: 'isAwesome()' should be the correct answer here.
upvoted 0 times
...
Sue
1 months ago
Hmm, the 'isShareable' keyword? Sounds like something straight out of a Hogwarts charms class. I'll stick with Option B, thank you very much.
upvoted 0 times
Daren
3 days ago
Yeah, 'isShareable' does sound like a spell. Option B is the safer choice.
upvoted 0 times
...
Roxane
11 days ago
I think using 'isAccessible()' method is the way to go here.
upvoted 0 times
...
Brock
13 days ago
I agree, 'isShareable' does sound like magic. Option B seems more practical.
upvoted 0 times
...
Sanda
19 days ago
User 1: I think Option B is the way to go.
upvoted 0 times
...
...
Joesph
2 months ago
Ah, the old 'isShareable' method, the classic go-to for record visibility issues. It's like they've never heard of field-level security. Option B is definitely the way to go here.
upvoted 0 times
Wayne
6 days ago
Yes, 'isAccesible()' method is the best option to ensure field accessibility.
upvoted 0 times
...
Gilma
9 days ago
Definitely, using 'isAccesible()' method will solve the issue with visibility.
upvoted 0 times
...
Juan
11 days ago
I agree, 'isAccesible()' method is the way to go for field-level security.
upvoted 0 times
...
...
Jeannetta
2 months ago
Wow, looks like they really dropped the ball on this one. Using the runAs method in the test class to enforce user permissions would have been a great idea. Option C is the way to go.
upvoted 0 times
Rebecka
1 months ago
Definitely, option C is the best solution to enforce user permissions and field level permissions.
upvoted 0 times
...
Darell
1 months ago
I agree, using runAs in the test class would have prevented this issue.
upvoted 0 times
...
...
Robt
2 months ago
I think using runAs in test class could also help enforce user permissions and field level permissions.
upvoted 0 times
...
Laura
2 months ago
I agree with Lashonda. They should have used isShareable keyword to assure record visibility.
upvoted 0 times
...
Rosita
2 months ago
The development team should have used the isAccessible() method in the Apex class to check field-level permissions. Option B is the correct answer here.
upvoted 0 times
Nickie
1 months ago
Sales Manager: That makes sense. The development team missed that feature.
upvoted 0 times
...
Ming
2 months ago
Developer: The isAccessible() method should have been used to check field-level permissions.
upvoted 0 times
...
Alease
2 months ago
Sales Rep: I can see the shipment amount, even though I'm not a manager.
upvoted 0 times
...
Kimberely
2 months ago
Sales Manager: The shipment records are visible to other users. This is a problem.
upvoted 0 times
...
...
Lashonda
2 months ago
I think the development team missed using isShareable keyword in Apex classes.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77