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 64 Discussion

Actual exam question for Salesforce's Salesforce Certified Platform Sharing and Visibility Architect (Plat-Arch-205) exam
Question #: 64
Topic #: 3
[All Salesforce Certified Platform Sharing and Visibility Architect (Plat-Arch-205) Questions]

Universal Containers (UC) requested that branch managers and UC branch staff should only see customers and related information in their geographic location.

Which options should be used together to achieve the requirements?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

0/2000 characters
Alysa
2 months ago
I’m surprised this is even a question, it’s pretty straightforward!
upvoted 0 times
...
Karan
2 months ago
Option A could work too, but I prefer C.
upvoted 0 times
...
My
3 months ago
Totally agree, sharing rules are key here!
upvoted 0 times
...
Shoshana
3 months ago
Wait, can we really limit access just by using sharing rules?
upvoted 0 times
...
Dorathy
3 months ago
I think option C makes the most sense.
upvoted 0 times
...
Corinne
3 months ago
I’m confused about the differences between sharing rules and role hierarchy. I might lean towards option C, but I need to double-check my notes.
upvoted 0 times
...
Armando
4 months ago
I feel like option B is less likely since it focuses on account teams, which doesn't seem to address the geographic restriction directly.
upvoted 0 times
...
Kris
4 months ago
I'm not entirely sure, but I remember something about role hierarchy from a similar question. Maybe option A could work too?
upvoted 0 times
...
Derrick
4 months ago
I think option C sounds right because it mentions organization-wide defaults and sharing rules, which we practiced in class.
upvoted 0 times
...
Delmy
4 months ago
I'm feeling pretty confident about this one. The requirements are clear, and I know the Salesforce security and sharing tools well. I'd go with option A - configure the role hierarchy and create sharing rules. That should do the trick.
upvoted 0 times
...
Elouise
4 months ago
Okay, I've got a strategy here. I think the key is using a combination of role hierarchy to control access at the org level, plus sharing rules to fine-tune access within each geographic location. That should let me meet the requirements.
upvoted 0 times
...
Cathern
5 months ago
Hmm, this one has me a bit stumped. I'm not totally sure about the differences between role hierarchy, sharing rules, and organization-wide defaults. I'll need to review those concepts before deciding which options to choose.
upvoted 0 times
...
Vallie
5 months ago
This seems like a pretty straightforward security and access control question. I think I'll start by carefully reading through the options and considering the key requirements - branch managers and staff should only see customers and info in their geographic location.
upvoted 0 times
...
Ammie
6 months ago
Option B sounds like a lot of work, but hey, if it gets the job done, I'm all for it. Just don't forget the snacks during the team meetings, am I right?
upvoted 0 times
Geraldine
5 months ago
B) Create the Account Team and add branch manager team members, and configure organization-wide defaults of the Account object.
upvoted 0 times
...
Dawne
5 months ago
A) Configure Role Hierarchy and create sharing rules.
upvoted 0 times
...
...
Bernardo
6 months ago
C is the answer, no doubt. Configuring the org-wide defaults and creating sharing rules is the way to go. It's like a one-two punch, you know?
upvoted 0 times
...
Dominga
7 months ago
I disagree, I believe option C is more effective.
upvoted 0 times
...
Rasheeda
7 months ago
I think option A is the best choice.
upvoted 0 times
...
Sarina
7 months ago
I'm leaning towards A. Role Hierarchy and sharing rules should give us the control we need. Just don't let the branch managers abuse their power, am I right?
upvoted 0 times
...
Arthur
7 months ago
B seems like the way to go. Setting up the Account Team and configuring the org-wide defaults should do the trick. Easy peasy!
upvoted 0 times
Sabina
6 months ago
B) Create the Account Team and add branch manager team members, and configure organization-wide defaults of the Account object.
upvoted 0 times
...
...
Teddy
7 months ago
Option C looks good, but don't forget to configure the organization-wide defaults as well. Gotta cover all the bases, you know?
upvoted 0 times
Refugia
6 months ago
C) Configure organization-wide defaults of the Account object and create sharing rules.
upvoted 0 times
...
Robt
7 months ago
B) Create the Account Team and add branch manager team members, and configure organization-wide defaults of the Account object.
upvoted 0 times
...
Jerilyn
7 months ago
A) Configure Role Hierarchy and create sharing rules.
upvoted 0 times
...
...

Save Cancel