SF-Admin Configuration and Setup Practice Question
Exhibit
{
"Profile": "Sales User",
"Object": "Opportunity",
"Permission_Override": "None",
"System_Permission": "View All",
"Org_Wide_Default": "Private"
}Refer to the exhibit. A user with the 'Sales User' profile has 'View All' permissions on the Opportunity object, but the Org-Wide Default is set to 'Private'. What is the effective access for this user?
⚠ Common exam trap
Candidates mistakenly believe that 'Private' Org-Wide Defaults restrict access even for users with 'View All', ignoring the fact that system-level permissions override sharing settings entirely.
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 records for the object.
The 'View All' permission is a system-level permission that overrides sharing settings. When a user has this permission, they can view every record of that object in the organization, regardless of the Org-Wide Default or individual sharing rules. This is a powerful administrative permission used for management or audit roles, and it effectively ignores the private sharing model for the specific object enabled.
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 only see records they own.
Why it's wrong here
The 'Private' Org-Wide Default limits access to owners and those above them in the role hierarchy. However, the 'View All' permission supersedes these sharing restrictions, granting the user visibility into all records regardless of the record's ownership status.
- ✓
The user can see all records for the object.
Why this is correct
System permissions like 'View All' are designed to bypass standard sharing model constraints. By granting this permission, the administrator ensures that the user can access every record of that object within the organization, rendering the 'Private' Org-Wide Default irrelevant for this user.
- ✗
The user requires a manual share record.
Why it's wrong here
Manual sharing is used when a specific record owner wants to provide access to a user on a case-by-case basis. Since the user already has the 'View All' permission, they already have full visibility to all records without requiring individual manual shares.
- ✗
The user can only see records shared via roles.
Why it's wrong here
Role hierarchies allow users to see records owned by users below them. Because the user has the 'View All' system permission, they are not constrained by the role hierarchy or the Org-Wide Default, making this statement technically incorrect regarding their actual access.
About these practice questions
This SF-Admin question is part of Courseiva's 202-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. 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.