Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

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

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?
B) Use runAs system method in test classes to test using different users and profiles.
A) Use isSharesble keyword in Apex classes to assure record visibility will be followed.
C) Use isAccesible keyword in Apex classes to assure record visibility will be followed.

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

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

by Oretha at Mar 10, 2024, 05:42 PM

Limited Time Offer

25%

Off

Get Premium Salesforce Certified Platform Sharing and Visibility Architect (Plat-Arch-205) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Yesenia
9 months ago
I agree with A, it’s crucial for proper access control.
upvoted 0 times
...
Fannie
10 months ago
Wait, can we really trust Apex managed sharing?
upvoted 0 times
...
Janey
10 months ago
C seems off, isn't that for different purposes?
upvoted 0 times
...
Walton
10 months ago
I think B is more important for testing access.
upvoted 0 times
...
Nguyet
10 months ago
A is definitely the way to go for visibility!
upvoted 0 times
...
Lasandra
10 months ago
We practiced a similar question, and I think the isShareable option was emphasized as a best practice for managing access.
upvoted 0 times
...
Nancey
11 months ago
I feel like the isAccessible keyword might be the right choice, but I can't recall the specifics of how it works in Apex.
upvoted 0 times
...
Shakira
11 months ago
I think using runAs in test classes is important for checking access, but I'm not sure if it directly mitigates the risk of improper access.
upvoted 0 times
...
Dolores
11 months ago
I remember we discussed the isShareable keyword in class, but I'm not entirely sure how it directly relates to record visibility.
upvoted 0 times
...
Kirk
11 months ago
I'm pretty confident that the isShareable keyword is the right approach here. It should help enforce the proper record visibility rules.
upvoted 0 times
...
Rossana
11 months ago
I'm a bit confused on the difference between isAccessible and isShareable. I'll need to review the documentation to make sure I understand which one is more appropriate here.
upvoted 0 times
...
Bernadine
11 months ago
Okay, I think I've got this. Using the isAccessible keyword in Apex classes should help ensure record visibility is properly followed.
upvoted 0 times
...
Barney
11 months ago
Hmm, this seems like a tricky one. I'll need to think carefully about the best way to mitigate the risk of improper access to records.
upvoted 0 times
...
Deonna
11 months ago
The runAs system method in test classes could be a good way to test access using different user profiles. That might help identify any potential issues.
upvoted 0 times
...
Sonia
11 months ago
I've seen questions like this before. I'm pretty confident I can figure out the right answer.
upvoted 0 times
...
Augustine
11 months ago
I'm confident that option C is the correct answer. Setting the rendered attribute to true and then re-rendering the component should make it visible on the page. The other options don't seem to address the core issue of re-rendering the hidden component.
upvoted 0 times
...
Pamella
11 months ago
I think it's about sending logs when hardware changes, right? I recall a similar question where alert groups were significant.
upvoted 0 times
...
Dana
1 year 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
1 year 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
1 year ago
C) Use runAs system method in test classes to test using different users and profiles.
upvoted 0 times
...
Carol
1 year ago
B) That's a good point. We need to make sure the access is controlled properly.
upvoted 0 times
...
Merilyn
1 year ago
A) Use isSharesble keyword in Apex classes to assure record visibility will be followed.
upvoted 0 times
...
...
Lanie
1 year 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 year 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
Veronika
1 year ago
A) The `isSharesble` keyword can help maintain record visibility and prevent unauthorized access.
upvoted 0 times
...
Gerald
1 year ago
C) Use runAs system method in test classes to test using different users and profiles.
upvoted 0 times
...
Vonda
1 year ago
B) That sounds like a good recommendation to ensure proper access to shipment records.
upvoted 0 times
...
Raymon
1 year ago
A) Use isSharesble keyword in Apex classes to assure record visibility will be followed.
upvoted 0 times
...
...
Beula
1 year 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
1 year ago
C) Use isAccesible keyword in Apex classes to assure record visibility will be followed.
upvoted 0 times
...
Melodie
1 year ago
C) Use isAccesible keyword in Apex classes to assure record visibility will be followed.
upvoted 0 times
...
Tarra
1 year ago
B) Use runAs system method in test classes to test using different users and profiles.
upvoted 0 times
...
Tasia
1 year ago
B) Use runAs system method in test classes to test using different users and profiles.
upvoted 0 times
...
Buddy
1 year ago
A) Use isSharedable keyword in Apex classes to assure record visibility will be followed.
upvoted 0 times
...
Micaela
1 year ago
A) Use isSharedable keyword in Apex classes to assure record visibility will be followed.
upvoted 0 times
...
...
Tawanna
1 year ago
But wouldn't using runAs system method in test classes also be helpful?
upvoted 0 times
...
Hui
1 year ago
I agree with Odelia, it will help ensure proper record visibility.
upvoted 0 times
...
Odelia
1 year ago
I think we should use isSharesble keyword in Apex classes.
upvoted 0 times
...

Save Cancel