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

Questions 1–5

1. 1application · medium

   A user has Read access to the Account object via their profile. The org-wide default for Account is Public Read Only. The user's profile has the 'Billing_Address__c' field set to Visible = False. What is the user's effective access to the 'Billing_Address__c' field on Accounts?

   • AAccess depends on the sharing rule's field permissions.
   • BRead/write access to the 'Billing_Address__c' field.
   • CNo access to the 'Billing_Address__c' field.
   • DRead-only access to the 'Billing_Address__c' field.
   Reveal Solution Discussion Select an answer first
2. 2foundation · easy

   A user has Read and Edit object permissions on the 'Case' object. What additional object-level permission is required for the user to permanently remove a Case record?

   • AView All
   • BTransfer
   • CDelete
   • DModify All
   Reveal Solution Discussion Select an answer first
4. 3foundation · easy

   Which statement accurately describes a limitation of field-level security?

   • AField-level security cannot restrict access to a field on a specific record; it applies to all records of the object.
   • BField-level security can be overridden by sharing rules.
   • CField-level security only applies to custom fields, not standard fields.
   • DField-level security can hide fields in reports and list views but not in search results.
   Reveal Solution Discussion Select an answer first
5. 4expert · hard

   A company has a Private org-wide default for the Custom_Object__c. A group of users needs to view records where the 'Owner' field is in a specific role hierarchy, but they should not be able to view records owned by users outside that hierarchy. What is the most appropriate solution?

   • ASet the org-wide default to Public Read Only, and create a sharing rule that denies access to records owned by users outside the hierarchy.
   • BCreate a sharing rule that grants read access to records where the Owner is in the specified role hierarchy.
   • CCreate a public group of the users and set the org-wide default to Public Read Only.
   • DUse field-level security to hide the 'Owner' field from the users.
   Reveal Solution Discussion Select an answer first
6. 5foundation · easy

   An administrator needs to allow a user to view only the 'Closed' cases in a queue, but not the 'Open' cases. Which security mechanism is best suited for this requirement?

   • AA page layout that hides the Open cases
   • BA sharing rule based on the Status field
   • CObject-level security on the Case object
   • DField-level security on the Status field
   Reveal Solution Discussion Select an answer first