Salesforce Certified Administrator — All Questions
5 questions
In Salesforce, what determines the baseline object-level permissions (create, read, edit, delete) a user has, along with the apps and tabs they can access?
- a.The user's role in the role hierarchy
- b.The user's profile✓
- c.The organization-wide default sharing settings
- d.The user's public group membership
A profile defines baseline object and field permissions, tab and app visibility, and system permissions for a user. The role hierarchy influences record-level access for reporting and sharing, org-wide defaults set the baseline record sharing, and public groups are used in sharing rules. Object-level CRUD comes from the profile (and any assigned permission sets).
An administrator needs to grant a small group of users an extra permission without changing their profile, which is shared by many others. What is the recommended tool?
- a.Change the organization-wide defaults
- b.Modify the role hierarchy
- c.Assign a permission set to those users✓
- d.Create a new profile and migrate everyone
Permission sets grant additional permissions to specific users on top of their profile, without altering the profile that others share. This keeps profiles lean and follows the modern least-privilege approach. Editing org-wide defaults or the role hierarchy changes record sharing broadly, and creating new profiles for a few users is unnecessary overhead.
Which feature lets an administrator temporarily assume a user's view of the application to troubleshoot an access issue, when it has been enabled?
- a.Login As the user via the user's detail page✓
- b.Resetting the user's password
- c.Changing the org-wide default to Public
- d.Deleting and recreating the user
When granted login access, an administrator can use Login As to see Salesforce exactly as that user does, which is the standard way to reproduce and diagnose access or visibility problems. Resetting a password, changing sharing defaults, or recreating the user does not let you see the user's specific experience.
Where would an administrator go to control the company's default locale, currency, and business hours settings that apply org-wide?
- a.The individual user's profile
- b.A validation rule
- c.A sharing rule
- d.Company Information and related Setup pages✓
Org-wide defaults for locale, default currency, and related company settings are configured in Company Information and related organization Setup pages. Profiles and individual settings can override locale per user, but the company baseline lives in these organization-level Setup areas. Validation and sharing rules serve entirely different purposes.
Organization-Wide Defaults (OWD) for an object are set to Private. What does this mean for record access before any sharing rules are applied?
- a.Every user can view and edit every record of that object
- b.Users can access only records they own, plus records shared with them through other means✓
- c.The object becomes read-only for all users
- d.Records are automatically deleted after 30 days
A Private org-wide default means users can only see and edit records they own by default; access to others' records must be granted through the role hierarchy, sharing rules, manual sharing, or teams. Private does not make records read-only or cause deletion, and it is the most restrictive baseline you can then open up selectively.