Valid Sharing-and-Visibility-Architect Dumps shared by ExamDiscuss.com for Helping Passing Sharing-and-Visibility-Architect Exam! ExamDiscuss.com now offer the newest Sharing-and-Visibility-Architect exam dumps, the ExamDiscuss.com Sharing-and-Visibility-Architect exam questions have been updated and answers have been corrected get the newest ExamDiscuss.com Sharing-and-Visibility-Architect dumps with Test Engine here:
Besides their own team accounts, sales managers at Universal Containers (UC) need Read access to all accounts of the same segment in other countries. Role Hierarchy was implemented accordingly (based on countries), but a sales manager in the U.S. is complaining that he cannot view account records of the same segment in Canad a. What should UC do to grant access properly?
Correct Answer: A
Recent Comments (The most recent comments are at the top.)
test - Nov 25, 2025
**Correct Answer: A. Create an owner-based sharing rule to grant access to account records, that have the same segment, to all sales-manager roles.**
### Explanation
The issue arises because **Role Hierarchy is based on countries**, so a U.S. sales manager is *not* above or equal to a Canadian sales manager in the hierarchy. That means they will **not** get visibility into Canadian accounts through roles alone, even if the accounts share the same business segment.
To enable visibility **across countries but within the same segment**, you need **criteria-based or owner-based sharing rules** that grant Read access horizontally across roles.
Let’s analyze the choices:
| Option | Analysis | | ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **A. Owner-based sharing rule** | ✔ **Correct**. Sharing rules allow sharing *across* role hierarchy branches—exactly what is needed. You can share accounts owned by Canadian segment teams with U.S. sales-manager roles, and vice-versa. | | **B. Public group + permission set** | ❌ **Incorrect.** Permission sets do not grant record-level access. A public group is fine, but permission sets only give object-level permissions. They cannot open up record visibility. | | **C. Change the Role Hierarchy** | ❌ **Incorrect.** Putting all sales managers in one role breaks the design and removes country-based hierarchical separation. It may also unintentionally expose more records than intended. Not recommended. |
Recent Comments (The most recent comments are at the top.)
**Correct Answer: A. Create an owner-based sharing rule to grant access to account records, that have the same segment, to all sales-manager roles.**
### Explanation
The issue arises because **Role Hierarchy is based on countries**, so a U.S. sales manager is *not* above or equal to a Canadian sales manager in the hierarchy. That means they will **not** get visibility into Canadian accounts through roles alone, even if the accounts share the same business segment.
To enable visibility **across countries but within the same segment**, you need **criteria-based or owner-based sharing rules** that grant Read access horizontally across roles.
Let’s analyze the choices:
| Option | Analysis |
| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **A. Owner-based sharing rule** | ✔ **Correct**. Sharing rules allow sharing *across* role hierarchy branches—exactly what is needed. You can share accounts owned by Canadian segment teams with U.S. sales-manager roles, and vice-versa. |
| **B. Public group + permission set** | ❌ **Incorrect.** Permission sets do not grant record-level access. A public group is fine, but permission sets only give object-level permissions. They cannot open up record visibility. |
| **C. Change the Role Hierarchy** | ❌ **Incorrect.** Putting all sales managers in one role breaks the design and removes country-based hierarchical separation. It may also unintentionally expose more records than intended. Not recommended. |
### Why Sharing Rules Are the Proper Solution
* They grant **lateral** acc...