Salesforce Certified Platform Administrator (Plat-Admn-201 / ADM-201) Exam Questions & Study Guide

Correct answer: B. Transfer Records

Transfer Records. It lets a user hand off records they don't own to someone else.

• View All just grants read access, it doesn't let anyone move ownership.
• Modify All is broad and can touch ownership too, but Transfer Records is the dedicated permission built for bulk transfers.
• Edit lets you change records you can already reach. It doesn't give you rights over records you don't own.

Correct answer: A. Create a Muting Permission Set inside the Sales Operations Permission Set Group and mute Delete on Opportunity

A Muting Permission Set, added inside that Permission Set Group. It strips out just the one permission for that group, and leaves the underlying permission sets untouched for everyone else reusing them.

• Cloning permission sets for a small exception just creates duplicate maintenance work, which defeats the point of a reusable Permission Set Group.
• OWD controls record visibility, not object-level permissions like Delete.
• Permissions stack across Profile and Permission Sets. If the group already grants Delete, pulling it from the Profile won't take it away.

Correct answer: A. Freeze the user, reassign the dashboards and automation references, then deactivate

Freeze them first. That blocks login instantly without breaking the dashboards or email alerts that depend on them. Once those dependencies are reassigned, deactivate to free up the license.

• You can't delete a user record in Salesforce, full stop. Freeze or deactivate are the only options.
• Salesforce won't let you deactivate someone who's the sole recipient of active workflow emails or tied to critical automation, and the dashboards would break too.
• Moving a Role affects what gets shared up the hierarchy. It doesn't stop anyone from logging in.

Correct answer: C. Lightning App Builder for Home

Lightning App Builder. Use it to add and arrange components on a Home page.

• Validation rules check what gets entered into a record, they have nothing to do with Home page layout.
• Record types control which picklist values and layouts a record gets. They don't touch the Home page.
• Profiles control access and settings, not what shows up on Home. That's Lightning App Builder's job.

Correct answer: A. Component visibility filters

Component visibility filters, set right on the component in Lightning App Builder. The filter criteria decide when it shows up.

• Dynamic Forms is about arranging fields and sections, not about showing or hiding a component based on a condition.
• A record-triggered Flow reacts to record changes, it doesn't control whether a page component is visible.
• Page activation decides who sees the page at all. It's the visibility filter that decides when one component on it appears.

Correct answer: B. 2

Two. A custom object can carry up to two master-detail relationship fields.

• One is allowed, but the real cap is higher than that.
• Three is over the actual limit.
• It's not unlimited. Salesforce caps this to keep sharing and cascade-delete behavior sane.

Correct answer: D. Campaigns that influenced opportunities and closed revenue

It shows which campaigns actually influenced opportunities, and how much of that closed revenue they can take credit for.

• Email open rates are a separate marketing metric, not what Campaign Influence reports on in Sales Cloud.
• Campaign Influence ties campaigns to revenue, it isn't limited to spend.
• Lead source counts won't tell you which campaigns moved opportunities forward.

Correct answer: D. Product and Price Book

Products define what the company sells. Price books and their entries set the prices you can actually use on an opportunity.

• Leads matter earlier in the sales process, but they don't carry product or price book data.
• Campaigns track marketing activity. You don't need one to add products and pricing to an opportunity.
• Opportunities are where products and price books get used, but they aren't the source of the product data itself.

Correct answer: C. Both rule criteria and formula criteria

Both. You can build criteria from fields or from formulas.

• Assignment rules support formulas too, not just field-based criteria.
• They support field-based criteria too, not just formulas.
• Manual assignment isn't a criteria type at all, it's just what happens when no rule catches the case.

Correct answer: C. Give a team a shared list of cases to claim or work

So a team has one shared pool of work to pull from. Assignment rules or other routing can feed cases into that queue.

• Queues route and share work. Reporting is a separate feature.
• A queue might send a notification, but its real job is giving a team a shared list to work.
• Queues organize work, they don't delete anything.

Correct answer: A. Setup → Deliverability → Access to Send Email is set to System email only

Check Email Deliverability first. Every sandbox refresh resets it to System email only, so only password resets and system notices go out, nothing to real customers. Flip it to All email to let Flow and alert emails through again.

• OWD is about record visibility. It won't silently swallow an email action that already ran clean.
• Marketing User just controls Campaign creation. It has nothing to do with sandbox email settings.
• Field History Tracking logs field changes. It can't block an outbound email.

Correct answer: A. Shared Activities in Activity Settings

Shared Activities. Turn on 'Allow Users to Relate Multiple Contacts to Tasks and Events' and reps can tie up to 50 Contacts to one Event or Task.

• Einstein Activity Capture syncs email and calendar from Google or Microsoft. Relating multiple Contacts to a native Event still needs Shared Activities.
• You can't build a custom master-detail or junction object on Event or Task, Salesforce doesn't allow that.
• Opportunity Contact Roles link Contacts to an Opportunity, not to a Task or Event.

Correct answer: A. Tasks and Events

Use Tasks and Events. It pulls calls, meetings, and tasks for everyone in the org, so the manager can see call counts by rep.

• Activities with Accounts and Accounts with Activities are about account-level activity, not calls per rep.
• Activity History is just a list on a record page. It isn't a report type you can build this report from.

Correct answer: B. 20 fields

20. That's the cap, on every standard or custom object.

• 20 is the real number, so 10, 15, and 25 are all wrong.

Correct answer: A. Matrix

Matrix. It groups by rows and columns and totals up where they cross.

• Tabular is just a flat list, no grouped subtotals at all.
• Joined puts multiple report types side by side, it doesn't build the row-and-column grid a Matrix report does.
• Summary groups rows and subtotals them, but not at row-and-column intersections like Matrix does.

Correct answer: A. A standard Accounts report with a Cross Filter set to Accounts without Opportunities

A Cross Filter, right inside a standard Accounts report. It can filter by whether related Opportunities (or Cases, or Activities) exist or don't, with sub-filters on top, no custom report type needed.

• Bucket Fields just group values that are already in the report. An Opportunities report only ever shows Accounts that already have Opportunities.
• A Reporting Snapshot saves report results into a custom object over time, it's for trend tracking, not for finding parents missing a child record.
• A Row-Level Formula works on rows that are already in the report. It can't surface Accounts that are missing from an Opportunities report in the first place.

Correct answer: D. Before Save

Before Save. It runs before the record hits the database, so it can update or check fields on the way in.

• A Platform Event flow kicks off from an event message, that's a different trigger entirely, not a before-save timing option.
• After Save runs once the record is already saved, too late to change fields before that save.
• After Delete fires once a record is gone. It has nothing to do with saving a record.

Correct answer: A. Decision

A Decision element. It checks the condition and sends the flow down the matching path.

• Assignment just sets variable values, it doesn't route the flow between paths.
• Loop walks through a collection, that's not how you branch on a condition.
• Get Records just fetches data. It doesn't evaluate anything to decide a path.

Correct answer: A. Agentforce with an appropriate topic and actions

Agentforce, set up with the right topic and actions. Give it proper guardrails and a handoff path for anything it can't safely answer.

• A scheduled Flow just runs at a set time. It can't hold a conversation with a customer.
• A dashboard shows report data. It doesn't respond to anyone.
• A validation rule only checks data on save, it can't answer questions or route a conversation.

Correct answer: A. Grant Read on Asset and Warranty_Status__c to the Agent User's Permission Set, then verify with Conversation Preview in Agentforce Builder

Customer-facing Service Agents run as a dedicated Agent User, kept on a tight leash by design. No object or field access on Warranty_Status__c for that user means the action fails. Grant the access, then confirm it actually works with Conversation Preview before activating.

• OWD is about record sharing, not field-level security, and Prompt Builder just manages prompt wording, not permissions.
• The Trust Layer masks sensitive data going to the LLM and doesn't retain it. It's not what's blocking an internal Flow from reading a field, and turning off a security control isn't the fix anyway.
• Workflow Rules were retired at the end of 2025. They can't be wired up as an Agentforce action at all.