2026 Updated Verified Pass Sharing-and-Visibility-Architect Study Guides & Best Courses [Q18-Q32]

4/5 - (2 votes)

2026 Updated Verified Pass Sharing-and-Visibility-Architect Study Guides & Best Courses

Ultimate Guide to the Sharing-and-Visibility-Architect – Latest Edition Available Now

Salesforce Certified Sharing and Visibility Architect Exam is designed for experienced Salesforce professionals who have a deep understanding of the platform’s sharing and visibility architecture. This includes architects, consultants, and developers who are responsible for designing and implementing sharing and visibility solutions for their organizations. To be eligible to take the exam, individuals must have already obtained other Salesforce certifications, such as the Salesforce Certified Administrator or Salesforce Certified Advanced Administrator.

To become a Salesforce Certified Sharing and Visibility Architect, candidates must pass a rigorous certification exam, which consists of 60 multiple-choice questions that must be completed within two hours. Sharing-and-Visibility-Architect exam covers a wide range of topics, including sharing models, access control, data visibility, data security, and data access patterns.

Q18. Universal Containers has a set of Account Management users that should only see Accounts once the Account becomes a customer. The Type field on the Account identifies whether the Account is a Prospect, Customer, Partner or Other. Which two methods could an Architect use to enable this sharing requirement, assuming a private sharing model for Accounts?
Choose 2 answers.

Institute a process that calls for the Account Manager to be added to the Account Team once the Account becomes a customer.

Create an Account Sharing Rule that shares all Accounts owned by Sales to be shared with Account Management roles and subordinates.

Create a Public List View, where Accounts of Type Customer are included and share the List view with the Account Management public group.

Create a Criteria-based Sharing rule that shares the Account to the Account Management Group when the Type is Customer.

Q19. Which option can be selected to share data when creating a sharing rule?

users

Profiles

Roles

Q20. Universal Containers has implemented a strict software architecture for their custom Apex code. One of the requirements is that all SOQL queries are contained within reusable classes. Depending on the context of the Apex transaction, the queries should be able to run either “With Sharing” or “Without Sharing”. Which two ways allow the Architect to meet these requirements?
Choose 2 answers.

Create a reusable SOQLQueries class; do not specify “With” or “Without Sharing” on the SOQLQueries class.

Create a reusable SOQLQueries class; do not specify “With” or “Without Sharing” on the SOQLQueries class and use the runAs() method to dynamically set the context.

Create a reusable SOQLQueries class; specify “With Sharing” on the methods that require user context and “Without Sharing” on the methods requiring system context.

Create a SystemSOQLQueries class and a UserSOQLQueries class; set the “With Sharing” keyword on the User SOQLQueries class and “Without Sharing” on the SystemSOQLQueries class.

Q21. Partner users can access records belonging to users in their account at their same role or lower in the role hierarchy, for Cases, Leads, Opportunities and Custom Objects. Which of the following access has to be given ?

Super user permission

Q22. Universal Containers implemented Sales Cloud and requested that only certain branch staff trained to sell high-risk products can create opportunities for high-risk products.
How should an architect allow only specific branch staff to sell high-risk products?

Set the price book OWD to View Only and share the (High Risk) price book with the trained staff via manual sharing.

Set the price book OWD to View Only and share the (High Risk) price book with the trained staff via a sharing rule.

Set the price book organization-wide default (OWD) to View Only and share the price book (High Risk) with the trained staff.

Q23. The sales managers at the Universal Containers (UC) requested their teams to define each user’s role on their accounts in order to provide an easy way to establish accountability and collaboration. Sales managers also requested that sales associates should only get the following permissions:
* Read access to the accounts.
* Read access to cases related to the accounts
* No access to deals related to the accounts
The sales associates may be granted access to opportunities when needed.
Assuming the overall sharing model of the organization is private and no sharing rules are configured on the account object. How can an Architect achieve these requirements?

Use Account teams and use Sharing rules to share cases with sales associates. No change required to the opportunity object

Use Account teams, Case teams. No configuration required for the opportunity object.

Use Account teams, Opportunity teams, and Case teams.

Use Account Teams to define access to accounts as well as opportunities and cases related to accounts

Q24. Universal Containers has implemented Customer Community with Customer Community Plus licenses for its distributors. Retail distributors have part-time agents who work for multiple distributors. Those agents should have access to other distributor accounts as well.
What should be configured to grant agents access to different distributor accounts?

Create a sharing set to share distributor accounts with agents using account contact relationship.

Use Apex sharing to share distributor accounts with agents using the Account__Share table.

Create sharing rules to share distributor accounts with agents.

Q25. Universal Containers (UC) service reps are assigned to a profile which has View All on the Case object. The organization-wide default (OWD) for the Account and Case objects is Private.
To make sure service reps have access to all relevant information (Accounts and Contacts) to attend to customer requests, which detail should an architect consider?

Service reps will NOT be able to access the relevant Accounts if their OWD is Private.

Service reps will NOT be able to access the relevant Contacts if their OWD is Controlled by Parent.

Service reps will be able to access the relevant Contacts if their OWD is Controlled by Parent.

Q26. What feature in Salesforce is needed to restrict access to a custom object that has Public Read/Write access?

Role Hierarchy

Record Type

Page Layout

Profile

Q27. Universal Containers (UC) has a mostly Private organization-wide default, as it Is a core principle of UC to respect client data privacy. UC has implemented complex processes for granting access to Opportunity data. A few key members of the sales reporting team need to always be able to see, but not change, Opportunity data for all opportunities.
What should an architect recommend as an approach to meet these requirements?

Create a permission set that grants the View All permission for Opportunity.

Create & permission set that grants the View All Data permission.

Give the View All Data permission to the Sales Reporting profile.

Q28. At Universal Containers, there’s a team of auditors distributed throughout the organization that all need access to high-value opportunities.
With a Private sharing model, which option should an architect recommend when designing a solution for this requirement?

Create a criteria-based sharing rule to grant a public group access to high-value opportunities.

Add the auditors to the default Opportunity Team.

Put the auditors at the highest level of the Role Hierarchy.

Q29. At Universal Containers, Accounts and Contacts are normally visible to all employees, and Proposals (custom object) are visible to the Account owner and managers. However, some Proposals are considered confidential and are managed by a Strategic Proposals team. These Proposals should not be visible to anyone in the Sales group other than the owner and the strategic team.
How should the architect design for this requirement?

Proposal Owner set to the Strategic Deals Team Queue and set the Account relationship to Master-Detail.

Disable Grant Access Using Hierarchies and set an Owner-Based Sharing rule for Strategic Deals team.

Proposal Owner set to the Strategic Deals Team Queue and create an owner-based sharing rule to grant visibility to the Account owner

Disable Grant Access Using Hierarchies and set a Criteria-Based Sharing rule for Strategic Deals team.

Q30. Universal Containers has a Private Sharing Model for the Opportunity object. Sales Rep A at Universal Containers created the Opportunity record and then transferred ownership of the Opportunity record to Sales Rep B.
Both Sales Rep A and B have the same role in the Role Hierarchy.
What access will Sales Rep A have to the Opportunity after the transfer?

Full Access

No Access

Read/Write

Read Only

Q31. Universal Containers (UC) is a fast-growing company that sells containers globally. It has thousands of dealerships throughout the world where local dealers service containers. UCimplemented a new Partner Community for its dealers. Each dealership has a dealer manager who manages the service agents. The community-sharing model is private.
What is the optimal option to give dealer managers visibility to customer cases only raised by their service agents?

Change external organization-wide default of case object to public read only.

Create a sharing rule to share cases created by service agents with their dealer manager.

Using the role hierarchy, the cases raised by service agents will be visible to their relevant dealer managers.

Create a sharing set to share cases created by service agents with their dealer manager.

Q32. Universal Computers (UC) is looking to expand its delivery capabilities through a network of distributors that use a Partner Community license. UC employees currently can view all delivery records through the organization-wide default (OWD) setting of Public Read Only.
Which approach would an architect recommend to limit the records a distributor can see?

Create a criteria-based sharing rule to grant access to the distributor

Set the External OWD to Private for the Delivery object.

Create an ownership-based sharing rule to grant access to the distributor.

Remove Read permission from the distributor profile.