SF-Admin Configuration and Setup Practice Question
An administrator is setting up a new user. The user is currently assigned to a profile that has 'View All' on the Account object. What is the impact of this setting?
⚠ Common exam trap
Examinees often confuse 'View All' with 'Modify All' or assume it only applies to records owned by the user, missing that it grants broad read access across the entire organization.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The user can see all Account records in the org.
The 'View All' permission is a powerful administrative setting that overrides the organization-wide sharing model, role hierarchy, and manual sharing rules. It grants the user read access to all records of that object, regardless of ownership or sharing settings. This is a critical security consideration, as it bypasses standard data visibility controls, and administrators must be careful when granting this to avoid unintentional data exposure to users.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The user can edit all Account records.
Why it's wrong here
'View All' grants read-only access to all records. It does not grant the 'Edit' permission, which is a separate object-level permission. A user with 'View All' can see every record, but they cannot modify those records unless they also have the 'Modify All' or 'Edit' permissions explicitly granted.
- ✓
The user can see all Account records in the org.
Why this is correct
The 'View All' object permission bypasses the sharing model, role hierarchy, and sharing rules. It grants the user read access to every record of the specified object within the organization, making it a very broad permission that should only be assigned to users who truly require full visibility for reporting.
- ✗
The user can delete any Account record.
Why it's wrong here
The 'View All' permission only grants read access. It does not grant delete permissions. Deleting records requires the 'Delete' permission on the object, which is distinct from 'View All'. Administrators should strictly control 'Delete' access to prevent accidental or malicious removal of critical business data from the Salesforce system.
- ✗
The user can manage sharing for all Accounts.
Why it's wrong here
The 'View All' permission is strictly for data visibility. It does not allow users to modify the sharing settings of records they do not own. Managing sharing rules and record-level access is a separate capability typically reserved for administrators or users with specific delegated administrative permissions within the platform configuration.
About these practice questions
One of 202 original SF-Admin practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Salesforce exam blueprint
This SF-Admin practice question is part of Courseiva's free Salesforce certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SF-Admin exam.