CareerExamPro

Salesforce Certified Administrator (ADM-201) practice test

10 practice questions for this exam, each with a full explanation and cited rule or blueprint reference.

Start practising

ServiceNow, Databricks, Snowflake & K8s: practice drill

10 realistic exam questions, graded as you go, with the exact rule or statute citation for every answer. Start free, no sign-up.

Timed mock exam

10 questions in 12 minutes, drawn from every topic. No answers shown until the end, then a full score breakdown, your weakest topics and a review of what you missed.

Practice tests that prepare you for this exam

Practise by topic

About this exam

Agency / Issuer
Salesforce
Region
Global / Online

Exact question counts, passing scores, and allowed reference materials vary by testing window and state/agency. Always confirm current rules with the official testing provider.

Sample questions

In Salesforce, an administrator sets the Organization-Wide Default (OWD) for a custom Invoice__c object to Public Read/Write. A sales director later asks to prevent West Region reps from editing East Region invoices using a Sharing Rule. Can a Sharing Rule accomplish this?

  1. Yes; creating a Criteria-Based Sharing Rule set to Read Only overrides Public Read/Write OWD for matching users.
  2. No; OWD sets the baseline and Sharing Rules can only open up access, so OWD must first be tightened to Private or Public Read Only.
  3. Yes; unchecking Grant Access Using Hierarchies on Invoice__c automatically blocks cross-region edits while keeping OWD Public Read/Write.
  4. No; Sharing Rules only apply to standard objects (Account, Opportunity, Case) and cannot control custom object access.
Show the answer

B. No; OWD sets the baseline and Sharing Rules can only open up access, so OWD must first be tightened to Private or Public Read Only.

In Salesforce's record-level access hierarchy (OWD -> Role Hierarchy -> Sharing Rules -> Teams -> Manual Sharing), OWD establishes the most restrictive baseline. Every layer above OWD can only open up access, never restrict it—so OWD must be set to Private or Public Read Only first, then opened selectively via Sharing Rules.

Reference: Salesforce Record-Level Security: OWD, Role Hierarchy & Sharing Rules

A Salesforce admin assigns a Sales_Ops_PSG Permission Set Group containing three shared Permission Sets (Leads_Full, Accounts_Edit, Reports_Create) to 40 operations users. Management asks to remove Delete on Lead strictly for members of Sales_Ops_PSG without affecting 200 other users who hold Leads_Full directly. What is the cleanest solution?

  1. Remove Delete on Lead directly from the Leads_Full Permission Set, since Permission Set Groups isolate edits from standalone assignments.
  2. Uncheck Delete on Lead in the users' base Profile, because Profile restrictions always override permissions granted by Permission Sets.
  3. Add a Muting Permission Set inside Sales_Ops_PSG and mute Delete on Lead, revoking it only within that group.
  4. Create an Organization-Wide Default of Private on Lead, which strips object-level Delete permission from Sales_Ops_PSG.
Show the answer

C. Add a Muting Permission Set inside Sales_Ops_PSG and mute Delete on Lead, revoking it only within that group.

Permission Sets are purely additive on top of Profiles, so modifying the Profile cannot revoke a Permission Set grant. Adding a Muting Permission Set to Sales_Ops_PSG selectively mutes Delete on Lead only for members of that Permission Set Group without altering Leads_Full for other users.

Reference: Salesforce Profiles, Permission Sets & Permission Set Group Muting

An admin is modeling Project__c (parent) and Expense_Line__c (child) in Salesforce. Business requirements state: (1) every expense line must belong to a project, (2) deleting a project must automatically delete its expense lines, (3) expense lines must inherit sharing from the project, and (4) Project__c needs a native Roll-Up Summary field totaling expense amounts. Which relationship type meets all four requirements?

  1. A Master-Detail relationship on Expense_Line__c pointing to Project__c.
  2. A Lookup relationship on Expense_Line__c with Required checked on the field definition.
  3. A Many-to-Many junction object using two Lookup relationships to Project__c.
  4. A Hierarchical relationship on Expense_Line__c, which automatically enables Roll-Up Summaries.
Show the answer

A. A Master-Detail relationship on Expense_Line__c pointing to Project__c.

A Master-Detail relationship enforces a required parent, inherits ownership and OWD/sharing from the master, performs cascade delete when the master is deleted, and enables native Roll-Up Summary fields (SUM, COUNT, MIN, MAX) on the master object. Lookup relationships do not inherit sharing or support native Roll-Up Summaries.

Reference: Salesforce Data Modeling: Master-Detail vs. Lookup Relationships

Taking this exam soon?

Tell us which exam domains or calculation drills you want more practice on.

Other Enterprise Cloud & Data exams