Salesforce
Administrator (ADM-201)
Organization Setup, Security, Automation, Reports & Analytics
Exam: ADM-201
60 Questions & Verified Answers
Salesforce Administrator - 60 Exam Questions
Questions cover all exam domains: Organization Setup, User Management, Object Manager, Sales
& Service Applications, Productivity, Data Management, and Automation.
Q01. What is the difference between a Profile and a Permission Set?
A. Identical
B. Profile = baseline permissions every user must have; Permission Set = additional
permissions added on top without changing the profile
C. Permission Sets replace Profiles in Lightning
D. Profiles are for admins only
Answer: B. Profile = baseline permissions; Permission Set = additional permissions on top
Every user is assigned one profile - their minimum access level.
Permission Sets stack on top of profiles, granting extra access to specific individuals without
changing the profile for everyone.
Q02. What are the three components of Salesforce record-level security?
A. Profiles, Roles, Sharing Rules
B. OWD (Organization-Wide Defaults), Role Hierarchy, and Sharing Rules (plus manual
sharing and criteria-based sharing)
C. CRUD, FLS, and Roles
D. Profiles, Permission Sets, and Public Groups
Answer: B. OWD, Role Hierarchy, and Sharing Rules (plus manual sharing)
OWD sets the floor - the most restrictive access for all users.
Role Hierarchy opens access upward - managers see subordinates' records.
Sharing Rules extend horizontal access to peers or other groups.
Q03. What does OWD (Organization-Wide Default) of 'Private' mean for an object?
A. Everyone can see all records
B. Users can only see records they own, or records shared with them explicitly
, C. No one can see any records
D. Only admins can see records
Answer: B. Users can only see records they own or records shared with them explicitly
Private OWD is the most restrictive - it forms the security floor.
Access is then opened via Role Hierarchy, Sharing Rules, or Manual Sharing.
Use Private for sensitive objects like salary data or confidential deals.
Q04. What is a Role Hierarchy in Salesforce and how does it affect record visibility?
A. Determines which profile a user has
B. A tree structure where users higher in the hierarchy can view and report on records owned
by users below them
C. Controls which fields are visible
D. Determines which apps a user can access
Answer: B. Higher roles see records owned by users below them
If a Sales Rep owns an opportunity, their Sales Manager automatically sees it.
Role Hierarchy only grants READ access upward - not edit access (unless the OWD is Public
Read/Write).
Role Hierarchy does NOT restrict access - it only opens it.
Q05. What is Manual Sharing and when is it used?
A. Sharing a record by exporting it
B. Sharing a specific record with a specific user or group by clicking the Sharing button on the
record - for one-off access that doesn't fit general sharing rules
C. A type of sharing rule
D. Sharing data with external systems
Answer: B. Sharing a specific record with a specific user or group on a case-by-case basis
Manual shares are created by: record owners, users with 'Full Access' on the record, and admins.
Use when: a single record needs to be shared with someone who wouldn't normally see it.
Manual shares can be removed by the record owner or admin.
Q06. What is the difference between Roles and Profiles?
A. They are identical
B. Profiles control WHAT a user can do (object/field permissions, apps); Roles control WHAT
DATA a user can see (record visibility through hierarchy)
C. Roles are for admins; Profiles are for standard users
D. Profiles are for data access; Roles are for UI layout
Answer: B. Profiles = object/field/app permissions; Roles = record visibility
A user must have both a Profile AND a Role.
Profile question: 'Can this user create Accounts?' Role question: 'Which Accounts can this user
see?'
They work together to form the complete security model.
Q07. What is a Public Group in Salesforce?
A. A group of publicly listed companies
B. A collection of users, roles, or other groups that can be used as a target in sharing rules,
queues, or list view visibility
C. A type of community user
, D. A group visible to external customers
Answer: B. A collection of users/roles/groups used as sharing targets
Public Groups simplify sharing - instead of listing 50 individual users in a sharing rule, create one
group.
Used in: sharing rules (share with group), queues (members of queue), list views (visible to group).
Created in Setup > Public Groups.
Q08. What are the four types of Salesforce Sandbox and their storage limits?
A. Dev, QA, Staging, Production
B. Developer (200 MB data), Developer Pro (1 GB), Partial Copy (5 GB with sample data), Full
Copy (full production data copy)
C. Small, Medium, Large, Enterprise
D. Trial, Standard, Advanced, Full
Answer: B. Developer (200 MB), Developer Pro (1 GB), Partial Copy (5 GB), Full Copy (all
production data)
Developer: for individual development - no production data.
Partial Copy: subset of production data - for more realistic testing.
Full Copy: exact mirror of production - used for final UAT and performance testing.
Refresh intervals: Developer = 1 day, Partial = 5 days, Full = 29 days.
Q09. What is the difference between a Standard Object and a Custom Object?
A. Standard Objects are read-only
B. Standard Objects are pre-built by Salesforce (Account, Contact, Lead, Opportunity, Case);
Custom Objects are created by admins for unique business data needs
C. Custom Objects cost extra
D. Standard Objects cannot be customized
Answer: B. Standard = pre-built by Salesforce; Custom = created by admins for specific
needs
Custom objects use '__c' suffix in the API name (e.g., Invoice__c).
Custom fields added to standard objects also use '__c'.
Custom objects support all standard Salesforce features: fields, relationships, workflows, reports,
triggers.
Q10. What is a Lookup Relationship vs a Master-Detail Relationship?
A. Identical
B. Lookup: loose, child survives parent deletion, no roll-up summaries; Master-Detail: tight,
child requires parent, deletion cascades, roll-up summaries available
C. Master-Detail is only for standard objects
D. Lookup supports roll-up summaries
Answer: B. Lookup = loose (child survives); Master-Detail = tight (child requires parent,
cascades, roll-up summaries)
Master-Detail: if you delete the Account (master), all related Invoices (detail) are also deleted.
Roll-up Summary Fields (Count, Sum, Min, Max on parent) only work in Master-Detail.
A custom object can have up to 2 Master-Detail relationships.
Q11. What is a Formula Field?
A. A field populated by Process Builder
Administrator (ADM-201)
Organization Setup, Security, Automation, Reports & Analytics
Exam: ADM-201
60 Questions & Verified Answers
Salesforce Administrator - 60 Exam Questions
Questions cover all exam domains: Organization Setup, User Management, Object Manager, Sales
& Service Applications, Productivity, Data Management, and Automation.
Q01. What is the difference between a Profile and a Permission Set?
A. Identical
B. Profile = baseline permissions every user must have; Permission Set = additional
permissions added on top without changing the profile
C. Permission Sets replace Profiles in Lightning
D. Profiles are for admins only
Answer: B. Profile = baseline permissions; Permission Set = additional permissions on top
Every user is assigned one profile - their minimum access level.
Permission Sets stack on top of profiles, granting extra access to specific individuals without
changing the profile for everyone.
Q02. What are the three components of Salesforce record-level security?
A. Profiles, Roles, Sharing Rules
B. OWD (Organization-Wide Defaults), Role Hierarchy, and Sharing Rules (plus manual
sharing and criteria-based sharing)
C. CRUD, FLS, and Roles
D. Profiles, Permission Sets, and Public Groups
Answer: B. OWD, Role Hierarchy, and Sharing Rules (plus manual sharing)
OWD sets the floor - the most restrictive access for all users.
Role Hierarchy opens access upward - managers see subordinates' records.
Sharing Rules extend horizontal access to peers or other groups.
Q03. What does OWD (Organization-Wide Default) of 'Private' mean for an object?
A. Everyone can see all records
B. Users can only see records they own, or records shared with them explicitly
, C. No one can see any records
D. Only admins can see records
Answer: B. Users can only see records they own or records shared with them explicitly
Private OWD is the most restrictive - it forms the security floor.
Access is then opened via Role Hierarchy, Sharing Rules, or Manual Sharing.
Use Private for sensitive objects like salary data or confidential deals.
Q04. What is a Role Hierarchy in Salesforce and how does it affect record visibility?
A. Determines which profile a user has
B. A tree structure where users higher in the hierarchy can view and report on records owned
by users below them
C. Controls which fields are visible
D. Determines which apps a user can access
Answer: B. Higher roles see records owned by users below them
If a Sales Rep owns an opportunity, their Sales Manager automatically sees it.
Role Hierarchy only grants READ access upward - not edit access (unless the OWD is Public
Read/Write).
Role Hierarchy does NOT restrict access - it only opens it.
Q05. What is Manual Sharing and when is it used?
A. Sharing a record by exporting it
B. Sharing a specific record with a specific user or group by clicking the Sharing button on the
record - for one-off access that doesn't fit general sharing rules
C. A type of sharing rule
D. Sharing data with external systems
Answer: B. Sharing a specific record with a specific user or group on a case-by-case basis
Manual shares are created by: record owners, users with 'Full Access' on the record, and admins.
Use when: a single record needs to be shared with someone who wouldn't normally see it.
Manual shares can be removed by the record owner or admin.
Q06. What is the difference between Roles and Profiles?
A. They are identical
B. Profiles control WHAT a user can do (object/field permissions, apps); Roles control WHAT
DATA a user can see (record visibility through hierarchy)
C. Roles are for admins; Profiles are for standard users
D. Profiles are for data access; Roles are for UI layout
Answer: B. Profiles = object/field/app permissions; Roles = record visibility
A user must have both a Profile AND a Role.
Profile question: 'Can this user create Accounts?' Role question: 'Which Accounts can this user
see?'
They work together to form the complete security model.
Q07. What is a Public Group in Salesforce?
A. A group of publicly listed companies
B. A collection of users, roles, or other groups that can be used as a target in sharing rules,
queues, or list view visibility
C. A type of community user
, D. A group visible to external customers
Answer: B. A collection of users/roles/groups used as sharing targets
Public Groups simplify sharing - instead of listing 50 individual users in a sharing rule, create one
group.
Used in: sharing rules (share with group), queues (members of queue), list views (visible to group).
Created in Setup > Public Groups.
Q08. What are the four types of Salesforce Sandbox and their storage limits?
A. Dev, QA, Staging, Production
B. Developer (200 MB data), Developer Pro (1 GB), Partial Copy (5 GB with sample data), Full
Copy (full production data copy)
C. Small, Medium, Large, Enterprise
D. Trial, Standard, Advanced, Full
Answer: B. Developer (200 MB), Developer Pro (1 GB), Partial Copy (5 GB), Full Copy (all
production data)
Developer: for individual development - no production data.
Partial Copy: subset of production data - for more realistic testing.
Full Copy: exact mirror of production - used for final UAT and performance testing.
Refresh intervals: Developer = 1 day, Partial = 5 days, Full = 29 days.
Q09. What is the difference between a Standard Object and a Custom Object?
A. Standard Objects are read-only
B. Standard Objects are pre-built by Salesforce (Account, Contact, Lead, Opportunity, Case);
Custom Objects are created by admins for unique business data needs
C. Custom Objects cost extra
D. Standard Objects cannot be customized
Answer: B. Standard = pre-built by Salesforce; Custom = created by admins for specific
needs
Custom objects use '__c' suffix in the API name (e.g., Invoice__c).
Custom fields added to standard objects also use '__c'.
Custom objects support all standard Salesforce features: fields, relationships, workflows, reports,
triggers.
Q10. What is a Lookup Relationship vs a Master-Detail Relationship?
A. Identical
B. Lookup: loose, child survives parent deletion, no roll-up summaries; Master-Detail: tight,
child requires parent, deletion cascades, roll-up summaries available
C. Master-Detail is only for standard objects
D. Lookup supports roll-up summaries
Answer: B. Lookup = loose (child survives); Master-Detail = tight (child requires parent,
cascades, roll-up summaries)
Master-Detail: if you delete the Account (master), all related Invoices (detail) are also deleted.
Roll-up Summary Fields (Count, Sum, Min, Max on parent) only work in Master-Detail.
A custom object can have up to 2 Master-Detail relationships.
Q11. What is a Formula Field?
A. A field populated by Process Builder
