Free Salesforce Certified Sharing and Visibility Architect Exam Sharing-and-Visibility-Architect Exam Practice Test

Universal Containers (UC) works with a dealer network to sell their products. There are approximately 5,000 dealers that do business with UC and UC has purchased a Partner Community to interact with each of their dealers on Opportunities. Each dealer is structured so that there are a group of managers who will oversee a larger team of agents. UC would like to set the Organization-Wide Defaults to Private for the Opportunity object, both internally and externally. Within each dealer, there are a few agents called Lead Agents who should be able to see the Opportunities for all of the other Agents at the dealer. What is the optimal solution for an Architect to recommend?

• Add a Sharing Set that shares Opportunities to the Lead Agent based on the Lead Agents Account.
• Build an Apex Managed Sharing rule that will assign specific Opportunities to Lead Agents.
• Grant Super User access to the Lead Agents as part of the Community user setup.
• Create a Sharing Rule to share opportunities to the owner's manager's role and below.

Which three capabilities are available with Enterprise Territory Management? Choose 3 answers

• Create a public group with Territory
• Share a report or dashboard folder with a Territory
• Metadata API Support
• Integration with Collaborative Forecasting
• Assignment of Territory on Opportunities

Universal Containers (UC) has created a public group with certain Sales Engineers to help on complex deals and a sharing rule to grant access to these opportunities. Opportunity OWD is private.What is the impact of these sharing settings?

• Subordinates of Managers who have Sales Engineers in the public group will also have access to these records.
• Sales Engineers that have a similar role of the Sales Engineers of the public group will also have access to these records.
• Sales Engineers Managers and their managers in the role hierarchy will also have access to these records.
• Sales Engineers direct reports will also have access to these records.

Universal Containers (UC) has a team that analyzes customer orders looking for fraud. This team needs access to Invoice records (Custom object, Private OWD). UC \as complex rules to control users' access. The Salesforce Architect recommended using Apex managed sharing to meet these requirements.Which two recommendations should a Salesforce Developer consider when implementing the changes7 Choose 2 answers

• Use 'With Sharing' keyword to make sure record visibility will always be considered.
• Use 'Without Sharing' keyword to make sure record visibility will be considered.
• Use runAs system method to test different users accessing these records.
• Use 'With Sharing' keyword to enforce field-level security.

Universal Containers has enabled External Default Sharing and wants to allow for external users to have the External Sharing Default set to Public Read-Only for a custom object. Which two options are valid Internal Default sharing settings for the custom object?

• Controlled by Parent
• Public Read/Write
• Private
• Public Read Only

Universal Containers (UC) implemented Sales Cloud and requested that sales agents have access to products the company sells and be able to create opportunities for its customers.What should the Organization-Wide Defaults (OWD) be for pricebook?

• Public Read Only
• Pubic Read Write
• View
• Use

Which two objects support creating queues?Choose 2 answers.

• Account.
• Opportunity.
• Lead.
• Case.

A sales rep at Universal Containers (UC) has manually shared an Opportunity record withinternal pre-sales users. After some time, the sales rep moved to another position and all opportunities records that were owned were transferred to a new sales rep. What happened to the internal pre-sales users access to the opportunity?

• They still have access to the record due to inherited sharing.
• They still have access to the record due to implicit sharing.
• They will no longer have access to the record.
• They still have access to the record due to team access.

Universal Containers (UC) has a private Organization-Wide Defaults (OWD) model for theAccount object and needs to control the access of records and fields according to theserequirements:* Sales reps can view/edit only their own records and cannot access the field 'segment' inaccount page.* Service reps need to view all accounts but cannot edit any information.* Sales managers can modify any account of reps reporting to them.* Service managers can modify any account.How can a Salesforce architect provide an optimal solution for this scenario?

• Use profiles, sharing rules, and change OWD to public read-only.
• Use profiles, manual sharing, and field-level security.
• Use profiles, permission sets, and field-level security.
• Use profiles, permission sets, role hierarchy, and field-level security.

Universal Containers has just deployed a change to its role hierarchy. A manager is reporting that their staff can now see Accounts that they do not own and should not have access to. How should the Architect troubleshoot?

• While logged in as the System Administrator, use the Field Accessibility Viewer to view a matrix of who has access to Accounts.
• While logged in as the one of the Staff members, navigate to a sample account and use the Sharing button to determine who has access.
• While logged in as the one of the Staff members, navigate to their user record and inspect their profile and role membership.
• While logged in as the System Administrator, use the Field Accessibility Viewer to view a matrix of who has access to Accounts.