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 2)

Questions 6–10

1. 6foundation · easy

   An organization-wide default for the 'Opportunity' object is set to Private. A sharing rule grants a group of users access to opportunities owned by a specific role. What is the effective access for those users?

   • AThey can access only the opportunities explicitly shared with them via the sharing rule.
   • BThey can access all opportunities in the organization because sharing rules override OWD.
   • CThey can access all opportunities owned by users in the same role as themselves.
   • DThey cannot access any opportunities because OWD Private blocks all sharing.
   Reveal Solution Discussion Select an answer first
2. 7application · medium

   A user has Read access to the Contact object via their profile. The org-wide default for Contact is Private, but the user is granted read access to a set of Contacts via a sharing rule. The user's profile has the 'Email' field set to Read Only. What is the user's effective access to the 'Email' field on the shared Contacts?

   • ARead/write access to the 'Email' field.
   • BRead-only access to the 'Email' field.
   • CNo access to the 'Email' field.
   • DAccess depends on the sharing rule's field permissions.
   Reveal Solution Discussion Select an answer first
4. 8application · medium

   A user has Read access to the Account object via their profile, but the org-wide default for Account is Private. The user is a member of a public group that is granted read access to a set of Accounts via a sharing rule. The user also has a permission set that grants Create and Edit access to the Account object. What is the user's effective access to the Accounts shared via the sharing rule?

   • ANo access to the shared Accounts.
   • BRead/write access to the shared Accounts.
   • CRead-only access to the shared Accounts.
   • DFull CRUD access to the shared Accounts.
   Reveal Solution Discussion Select an answer first
5. 9foundation · easy

   A Salesforce administrator needs to prevent a group of users from viewing any records of the custom object 'Invoice'. Which object-level security setting should be changed?

   • ASet the organization-wide default for Invoice to Private.
   • BSet the Invoice object's 'Visible' checkbox to false in the user's field-level security.
   • CCreate a sharing rule that denies access to all Invoice records.
   • DRemove the 'Read' permission on the Invoice object for the users' profile or permission set.
   Reveal Solution Discussion Select an answer first
6. 10expert · hard

   A company has a Private org-wide default for the Account object. A group of users needs to view Accounts that are in the 'Prospect' record type, but they should not be able to view Accounts in other record types. What is the most appropriate solution?

   • ASet the org-wide default for Account to Public Read Only, and create a sharing rule that denies access to Accounts with Record Type != 'Prospect'.
   • BCreate a sharing rule that grants read access to Accounts with Record Type = 'Prospect'.
   • CCreate a public group of the users and set the org-wide default for Account to Public Read Only.
   • DUse field-level security to hide the 'Record Type' field from the users.
   Reveal Solution Discussion Select an answer first