New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Certified Platform Sharing and Visibility Architect (Plat-Arch-205) Exam - Topic 3 Question 38 Discussion

Actual exam question for Salesforce's Salesforce Certified Platform Sharing and Visibility Architect (Plat-Arch-205) exam
Question #: 38
Topic #: 3
[All Salesforce Certified Platform Sharing and Visibility Architect (Plat-Arch-205) 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:

0/2000 characters
Brynn
3 months ago
Sounds like a classic oversight in Apex development!
upvoted 0 times
...
Felicidad
3 months ago
I disagree, runAs in test class doesn't solve the visibility problem.
upvoted 0 times
...
Jade
3 months ago
Wait, sales reps can see shipment amounts? That's a big issue!
upvoted 0 times
...
Bobbye
4 months ago
I think it's more about the isAccessible() method.
upvoted 0 times
...
Murray
4 months ago
They definitely missed the isShareable keyword.
upvoted 0 times
...
Zana
4 months ago
I feel like the isShareable keyword could be the right answer since it deals with sharing rules, but I’m not completely confident about the specifics.
upvoted 0 times
...
Precious
4 months ago
I’m a bit confused about the runAs method; I thought it was mainly for testing user permissions, not necessarily for controlling visibility in the app itself.
upvoted 0 times
...
Gracia
4 months ago
I think we practiced a similar question about field accessibility, and I recall that the isAccessible() method is crucial for checking if users can see certain fields.
upvoted 0 times
...
Kenia
5 months ago
I remember discussing the importance of the isShareable keyword in class, but I'm not entirely sure how it directly impacts record visibility.
upvoted 0 times
...
Earlean
5 months ago
The answer is clear to me - the development team should have used the isAccessible() method to properly control field-level permissions. That's the feature they missed.
upvoted 0 times
...
Micah
5 months ago
I'm a bit confused on the different options here. I'll need to review the Apex security documentation to make sure I understand the differences between these approaches.
upvoted 0 times
...
Dusti
5 months ago
This is a classic Salesforce security challenge. I'm confident I can identify the missing feature and provide a solid solution.
upvoted 0 times
...
Truman
5 months ago
Okay, I've seen this kind of problem before. I think the key is to really understand the different access control features in Apex and how to properly implement them.
upvoted 0 times
...
Janella
5 months ago
Hmm, this seems like a tricky one. I'll need to think carefully about how to approach the security and visibility issues.
upvoted 0 times
...
Sherita
5 months ago
I think this question is testing our understanding of SLB's capabilities in handling SSL/TLS certificates for two-way authenticated HTTPS websites. I'll need to carefully review the options and think through the requirements.
upvoted 0 times
...
Jarod
5 months ago
I'm pretty confident I know the answer to this one. It's about the team-specific context that story points are based on.
upvoted 0 times
...
Esteban
5 months ago
This seems like a straightforward question about solution approaches. I'm pretty confident I can figure this out.
upvoted 0 times
...
Hermila
5 months ago
I'm a bit confused here. The question talks about the load-balancing method being set to least bandwidth, but doesn't specify what the default is during startup. I'll have to think this through carefully.
upvoted 0 times
...
Justine
5 months ago
The organic materials issue feels like it could be related to social responsibility, but I keep questioning if it really fits with ethics directly.
upvoted 0 times
...
Marion
9 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
9 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
Elina
8 months ago
User 3: Agreed, that should help with the visibility issues.
upvoted 0 times
...
Rupert
8 months ago
User 2: Yeah, using the isAccessible() method in Apex classes seems like the right choice.
upvoted 0 times
...
Glenn
8 months ago
I'm with you on Option B, it seems like the most logical solution.
upvoted 0 times
...
Daren
8 months ago
Yeah, 'isShareable' does sound like a spell. Option B is the safer choice.
upvoted 0 times
...
Roxane
9 months ago
I think using 'isAccessible()' method is the way to go here.
upvoted 0 times
...
Brock
9 months ago
I agree, 'isShareable' does sound like magic. Option B seems more practical.
upvoted 0 times
...
Sanda
9 months ago
User 1: I think Option B is the way to go.
upvoted 0 times
...
...
Joesph
10 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
8 months ago
Yes, 'isAccesible()' method is the best option to ensure field accessibility.
upvoted 0 times
...
Gilma
9 months ago
Definitely, using 'isAccesible()' method will solve the issue with visibility.
upvoted 0 times
...
Juan
9 months ago
I agree, 'isAccesible()' method is the way to go for field-level security.
upvoted 0 times
...
...
Jeannetta
10 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
10 months ago
Definitely, option C is the best solution to enforce user permissions and field level permissions.
upvoted 0 times
...
Darell
10 months ago
I agree, using runAs in the test class would have prevented this issue.
upvoted 0 times
...
...
Robt
10 months ago
I think using runAs in test class could also help enforce user permissions and field level permissions.
upvoted 0 times
...
Laura
10 months ago
I agree with Lashonda. They should have used isShareable keyword to assure record visibility.
upvoted 0 times
...
Rosita
11 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
9 months ago
Sales Manager: That makes sense. The development team missed that feature.
upvoted 0 times
...
Ming
10 months ago
Developer: The isAccessible() method should have been used to check field-level permissions.
upvoted 0 times
...
Alease
10 months ago
Sales Rep: I can see the shipment amount, even though I'm not a manager.
upvoted 0 times
...
Kimberely
10 months ago
Sales Manager: The shipment records are visible to other users. This is a problem.
upvoted 0 times
...
...
Lashonda
11 months ago
I think the development team missed using isShareable keyword in Apex classes.
upvoted 0 times
...

Save Cancel