Given a Particular Customer Scenario, Describe the Appropriate Use and Limitations of Relevant Object and Field Level Security Settings Needed to Allow and Limit User’s Access to Different Types of Information. SHARING-AND-VISIBILITY-ARCHITECT Practice Questions (Page 3)

Questions 11–12

1. 11expert · hard

   A company has a Private org-wide default for the Opportunity object. A group of users needs to view Opportunities that have a 'Stage' of 'Closed Won' and an 'Amount' greater than $50,000. They should not be able to view any other Opportunities. What is the most appropriate solution?

   • ACreate a sharing rule that grants read access to Opportunities where 'Stage' = 'Closed Won' AND 'Amount' > $50,000.
   • BUse field-level security to hide the 'Stage' and 'Amount' fields from the users.
   • CChange the org-wide default to Public Read Only, and create a sharing rule that denies access to Opportunities that do not meet the criteria.
   • DCreate two sharing rules: one for 'Stage' = 'Closed Won' and one for 'Amount' > $50,000.
   Reveal Solution Discussion Select an answer first
2. 12foundation · easy

   A user has Read object permission on 'Contact' but the organization-wide default is Private. The user is the owner of a Contact record. What is the user's effective access to that record?

   • ARead-only access, because they own the record.
   • BAccess only if a sharing rule grants it.
   • CNo access, because OWD Private overrides object permissions.
   • DFull access, including Edit and Delete, because they own the record.
   Reveal Solution Discussion Select an answer first