SHARING-AND-VISIBILITY-DESIGNER practice question 6 of 30

What is the best practice for testing sharing and visibility changes?

Full set: 212 questions
Answer options
A: Use Administrative and User reports to view the Active Users.
B: Use the Login As feature for a sample user in each role and profile. Correct answer
C: Use Field Audit Trail to audit the field meta-data and visibility.​
D: Use the Sharing button to test Profile and Permission set changes.
Correct Answer:
B. Use the Login As feature for a sample user in each role and profile.
Explanation

Sharing and visibility settings are user-context specific, determined by a combination of a user's profile, role, permission sets, and various sharing rules. The most effective and comprehensive best practice to validate these changes is to use the "Login As" feature. This allows an administrator or tester to experience the application exactly as a specific user would, providing a direct and accurate view of their data access and permissions. This method tests the cumulative effect of all visibility settings for that user.

Why Incorrect

A. User reports can identify which users to test as, but they do not perform the actual visibility test or show what those users can see.
C. Field Audit Trail tracks historical changes to data within fields; it does not audit or test metadata visibility settings like Field-Level Security.
D. The "Sharing" button is a diagnostic tool for a single record. It does not test a user's overall object permissions, FLS, or what they see in list views or reports.

References

1. Salesforce Help, Salesforce Security Guide, "Test Your Sharing Model". This guide explicitly recommends using the "Log In as Another User" feature to test the visibility settings for users in different roles and profiles.

2. Salesforce Help, Set Up Your Org, "Log In as Another User". The documentation describes this feature as a troubleshooting tool for "any user-related issue," which directly includes permission and data visibility problems.

Scroll to Top