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 4 Question 31 Discussion

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

To grant Universal Containers sales managers access to shipment records properly, it was necessary to leverage Apex managed sharing. The IT team is worried about improper access to records.

What should an architect recommend to mitigate this risk?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Dana
28 days ago
I heard the IT team is so worried about this issue, they're considering implementing a system where every record comes with a built-in self-destruct mechanism. Just in case.
upvoted 0 times
...
Dolores
29 days ago
Wait, we're supposed to mitigate the risk of improper access? I thought the goal was to grant the sales managers full access to everything, no questions asked!
upvoted 0 times
Melvin
2 days ago
C) Use runAs system method in test classes to test using different users and profiles.
upvoted 0 times
...
Carol
10 days ago
B) That's a good point. We need to make sure the access is controlled properly.
upvoted 0 times
...
Merilyn
14 days ago
A) Use isSharesble keyword in Apex classes to assure record visibility will be followed.
upvoted 0 times
...
...
Lanie
1 months ago
Ah, the `isAccessible` keyword, the holy grail of record access control! This is definitely the way to go, but I hope the IT team doesn't mind a few extra lines of code.
upvoted 0 times
...
Tracie
1 months ago
The `runAs` system method in test classes could be useful for testing different user scenarios, but it doesn't directly address the issue of record visibility in production.
upvoted 0 times
Vonda
5 days ago
B) That sounds like a good recommendation to ensure proper access to shipment records.
upvoted 0 times
...
Raymon
20 days ago
A) Use isSharesble keyword in Apex classes to assure record visibility will be followed.
upvoted 0 times
...
...
Beula
2 months ago
Using the `isSharedable` keyword seems like a good option to ensure record visibility, but I'm not sure it's the best approach to mitigate the overall risk of improper access.
upvoted 0 times
Caitlin
13 days ago
C) Use isAccesible keyword in Apex classes to assure record visibility will be followed.
upvoted 0 times
...
Melodie
17 days ago
C) Use isAccesible keyword in Apex classes to assure record visibility will be followed.
upvoted 0 times
...
Tarra
27 days ago
B) Use runAs system method in test classes to test using different users and profiles.
upvoted 0 times
...
Tasia
1 months ago
B) Use runAs system method in test classes to test using different users and profiles.
upvoted 0 times
...
Buddy
1 months ago
A) Use isSharedable keyword in Apex classes to assure record visibility will be followed.
upvoted 0 times
...
Micaela
1 months ago
A) Use isSharedable keyword in Apex classes to assure record visibility will be followed.
upvoted 0 times
...
...
Tawanna
2 months ago
But wouldn't using runAs system method in test classes also be helpful?
upvoted 0 times
...
Hui
2 months ago
I agree with Odelia, it will help ensure proper record visibility.
upvoted 0 times
...
Odelia
3 months ago
I think we should use isSharesble 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