Plat-Admn-201 Salesforce Certified Platform Administrator Exam Topics and Questions

Configuration and Setup establishes the foundation of your Salesforce org, and exam questions here test whether you can distinguish cosmetic changes from decisions that ripple through security, data access, and user experience. The weight is moderate, but the domain is broad and candidates often misjudge the scope of what counts as setup versus what belongs in customization.

– Company settings and user interface configuration

Company settings govern fiscal years, business hours, currency management, and defaults that affect reporting, forecasting, and how records display across the org. You need to know which settings cascade to new records and which apply retroactively. UI configuration through Lightning App Builder, app menus, list views, and global actions determines what users see and how they navigate. The exam tests your ability to choose the right declarative tool for a given requirement without writing code. You should understand when a global action differs from an object-specific quick action, and how list view filters interact with sharing rules to determine visibility.

– User setup, licenses, and login management

User setup covers creating and maintaining users, assigning licenses, and managing login methods. Usernames must be unique across all Salesforce orgs, not just yours. You need to understand the difference between user licenses and permission set licenses, and when to assign feature licenses for specific capabilities. Deactivating a user preserves their records and reassigns ownership without deletion, while deleting a user is rarely the right choice. The exam will present scenarios where you must decide whether to override login restrictions, assign a profile, or configure multi-factor authentication. Working hours and locales affect when users receive scheduled reports and how dates display, and these settings are tested in context rather than in isolation.

– Security controls and the sharing model

Organization security controls include identity verification, the Setup Audit Trail, login hours, session settings, and controlling access to records via the sharing model. The exam expects you to apply org-wide defaults, roles, role hierarchy, public groups, and manual sharing in combination to meet a stated requirement. You must know when to use a team versus a public group, and how the role hierarchy grants access to subordinates without explicit sharing rules. Report and dashboard folder sharing operates differently from record sharing, and questions often hinge on understanding which users can see a folder versus which can see the data inside. The Setup Audit Trail tracks configuration changes, and you need to know what it logs and what it omits.

– Profiles and permission sets

Profiles define a baseline of permissions and settings, while permission sets and permission set groups grant additive access. The exam tests when to create a custom profile versus layering permission sets onto a standard one. Permission set groups bundle multiple permission sets, and muting permission sets remove specific permissions from a group without editing the underlying sets. You should understand how profile settings like login hours and IP restrictions interact with permission set assignments, and when to use a permission set license to unlock premium features. Scenarios will require you to balance least-privilege access with operational efficiency, and the wrong choice often grants too much or too little access.

How Configuration and Setup is tested

Questions present a business requirement and ask you to select the configuration that meets it without side effects. A scenario might describe a multinational org needing different fiscal years for reporting, or a user who should see all opportunities in their region but not modify them. The exam expects you to distinguish settings that affect all users from those scoped to profiles or permission sets. You will encounter items where multiple answers seem plausible, and the correct one hinges on understanding what happens when you deactivate a user versus freeze them, or when a role hierarchy conflicts with org-wide defaults. Candidates lose marks by choosing answers that solve the immediate problem but introduce unintended access or break existing workflows. The weight of fifteen percent means you will see multiple items from this domain, and weak coverage of user setup or the sharing model will cost you points across several questions.

Object Manager and Lightning App Builder shift the focus from org-wide settings to the structure of your data and how users interact with it. This domain tests your command of relationships, field types, page layouts, and record types. The weight matches the previous topic, and the exam expects fluency in both standard object behavior and custom object design.

– Object architecture and relationships

Standard objects like Account, Contact, Opportunity, and Case form the backbone of Salesforce, and you need to understand their default relationships and how they extend through custom objects. Master-detail relationships create tight coupling where the child inherits sharing and the parent controls the child's lifecycle, while lookup relationships allow independent records. Junction objects use two master-detail relationships to model many-to-many associations. Schema Builder provides a visual representation of your data model, and the exam tests your ability to identify which relationship type fits a requirement. You must know the implications of each choice, including roll-up summary fields on master-detail relationships and the inability to reparent certain child records. Record types allow different page layouts and picklist values on the same object, and scenarios will ask you to configure them to support multiple business processes.

– Field creation, deletion, and customization

Creating fields involves choosing the right data type, setting field-level security, and understanding dependencies. Deleting a field removes it from all records, breaks formulas and validation rules that reference it, and may disrupt integrations. The exam presents scenarios where you must decide whether to delete or hide a field, and the wrong choice leaves orphaned data or broken automation. Roll-up summary fields aggregate child records on a master-detail relationship, and you need to know their limitations. Cross-object formulas span relationships to pull data from parent or child records, and picklist dependencies restrict values based on a controlling field. Relationship fields create lookups or master-detail links, and the exam tests what happens when you change a lookup to master-detail or vice versa.

– Page layouts, record types, and Lightning App Builder

Page layouts control field visibility and order, and you assign them by profile and record type. Lightning App Builder lets you create custom pages with components, and you need to know when to use a Lightning page versus a page layout. Record types drive business processes by presenting different picklist values and page layouts to different user groups. The exam expects you to configure record types and page layouts together to meet a requirement, such as showing a simplified layout to sales reps and a detailed one to managers. Quick actions and global actions appear on page layouts and utility bars, and you must understand the difference. Visibility on Lightning page layouts respects field-level security and page layout assignments, and questions often test the interaction between these layers.

How Object Manager and Lightning App Builder is tested

Items in this domain describe a data model requirement or a user experience problem and ask you to configure objects, fields, relationships, or layouts to solve it. You might see a scenario where a custom object needs to inherit sharing from a parent, or where a field must aggregate values from child records. The exam tests whether you know the constraints of each relationship type, such as the limit of two master-detail relationships per object or the inability to create roll-up summaries on lookup relationships. Candidates lose marks by choosing a relationship type that seems to fit but introduces unintended behavior, like preventing record reparenting when a lookup would suffice. Questions about field deletion test whether you recognize the downstream impact on formulas, validation rules, and reports. The fifteen percent weight means this domain appears frequently, and weak understanding of relationships or page layout assignment will cost you across multiple items. The exam expects precision, not approximation.

Sales and Marketing Applications cover the tools that track leads, opportunities, campaigns, and forecasts. The exam assumes you know the standard sales process and tests your ability to configure productivity features and automation. At ten percent, this domain is lighter than Configuration or Object Manager, but it spans lead management, opportunity tracking, and campaign tools, so weak coverage in any one area will still cost you marks.

– Lead management and conversion

Leads represent potential customers before they enter the sales pipeline, and lead conversion creates an account, contact, and optionally an opportunity. The exam tests when to use lead assignment rules to route leads based on criteria, and how the conversion process maps lead fields to account and contact fields. You need to understand the implications of converting a lead, including what happens to lead history and related records. Path guides users through stages on a lead or opportunity, and you should know how to configure path steps and key fields. Lead scoring and grading rank leads based on behavior and fit, and the exam expects you to distinguish these tools from manual lead prioritization.

– Opportunity management and sales productivity

Opportunities track deals through stages, and the exam tests your knowledge of opportunity tools like forecasting, territory management, and Einstein features. Forecasting aggregates opportunity amounts by stage and owner, and you must know how to enable and configure it. Territory management assigns accounts and opportunities to sales teams based on rules, and the exam presents scenarios where you choose between role hierarchy and territory hierarchy. Einstein for Sales includes opportunity scoring, lead scoring, and the home page assistant, which surfaces insights to sales reps. You need to understand when these AI features apply and what data they require. Dashboards and reports provide visibility into the pipeline, and questions test your ability to configure them to meet a sales manager's requirements.

– Campaign management and automation

Campaigns group marketing efforts and track responses through campaign members. The exam tests how to create campaigns, add members, and report on campaign influence. Campaign hierarchies roll up metrics from child campaigns to parents, and you must know when to use a hierarchy versus independent campaigns. Lead assignment rules automate lead routing based on criteria like geography or product interest, and the exam expects you to configure rules that assign leads without creating duplicates or routing loops. Campaign member statuses track responses, and you should understand how to customize statuses and report on conversion rates.

How Sales and Marketing Applications is tested

Questions describe a sales process requirement and ask you to configure lead assignment, opportunity stages, or campaign tracking to meet it. You might see a scenario where leads should route to different queues based on region, or where a sales manager needs a dashboard showing pipeline by territory. The exam tests whether you understand the difference between lead conversion and manual account creation, and what data carries over in each case. Candidates lose marks by choosing tools that seem relevant but do not fit the requirement, such as using a workflow rule when a lead assignment rule is the standard tool. Items about forecasting and territory management test your knowledge of when to enable these features and what permissions users need. The ten percent weight means you will see several items from this domain, and weak coverage of lead conversion or opportunity tools will cost you marks. The exam expects you to apply sales productivity features in context, not recite definitions.

Service and Support Applications focus on case management, which is how Salesforce tracks customer issues from creation to resolution. The weight is equal to Sales and Marketing, and the exam tests your ability to configure case automation and support processes. This domain is narrower in scope but deeper in detail, and candidates who underestimate case escalation or assignment rules will lose marks quickly.

– Case management and routing

Cases represent customer inquiries or problems, and the exam tests how to create, assign, and escalate them. Case assignment rules route cases to queues or users based on criteria like product, priority, or customer tier. Queues hold cases until an agent claims them, and you need to know how to create queues, assign members, and configure list views for queue visibility. The exam expects you to distinguish when to use a queue versus direct assignment to a user. Support processes define case record types and stage values, allowing different workflows for different case types. You must understand how to create a support process and assign it to a record type, and what happens when a case changes record types mid-lifecycle.

– Case automation and escalation

Case auto-response rules send emails to customers when a case is created, and the exam tests when to use them and how to configure response templates. Case escalation rules trigger when a case remains open beyond a threshold, and you need to know how to define escalation criteria and actions. Einstein for Service includes case classification, which predicts case fields based on the description, and recommended articles, which surfaces knowledge articles to agents. The exam presents scenarios where you choose between escalation rules and manual escalation, or between Einstein recommendations and static assignment. You should understand the order of execution for case rules: assignment runs first, then auto-response, then escalation. Questions often hinge on knowing which rule fires when multiple criteria match.

How Service and Support Applications is tested

Items describe a support workflow requirement and ask you to configure case assignment, escalation, or automation to meet it. You might see a scenario where high-priority cases should escalate after four hours, or where cases from a specific region should route to a specialized queue. The exam tests whether you understand the interaction between assignment rules and queues, and what happens when a case matches multiple escalation rules. Candidates lose marks by choosing answers that solve part of the requirement but miss a constraint, such as configuring an escalation rule without ensuring the case assignment rule runs first. Questions about support processes test your knowledge of how record types and stage values work together, and what happens when a user lacks access to a record type. The ten percent weight means this domain appears less frequently than Configuration or Object Manager, but each item carries more weight per question. Weak coverage of case escalation or Einstein for Service will cost you marks, and the exam expects you to apply automation tools in the correct order.

Productivity and Collaboration covers the tools that help users work together and stay organized: activity management, Chatter, the Salesforce mobile app, and AppExchange. The exam tests your ability to configure these features to improve user adoption and efficiency. The weight is moderate, and questions span a range of tools rather than concentrating on one area, so you need breadth more than depth.

– Activity management and Chatter

Activities include tasks and events, which track work items and calendar entries. The exam tests how to create tasks, assign them to users, and configure reminders. You need to know the difference between a task and an event, and when to use a recurring task versus individual tasks. Chatter enables collaboration through feeds, groups, and posts. Chatter groups can be public, private, or unlisted, and you must understand who can access each type. Internal users see all Chatter activity unless restricted, while external users in communities see only the groups and records they have access to. The exam presents scenarios where you configure Chatter groups to support a project team or customer community, and the wrong answer often grants too much visibility or too little.

– Salesforce mobile app and AppExchange

The Salesforce mobile app delivers Lightning pages to phones and tablets, and the exam tests how to customize the app menu, configure branding, and build a mobile-optimized Lightning page. You should know the difference between the mobile browser experience and the native app, and when to use each. Mobile app visibility respects profiles, permission sets, and page assignments, so a user sees only what their permissions allow. The launchpad presents quick actions and key objects, and you need to know how to configure it. AppExchange provides pre-built solutions, and the exam tests your knowledge of managed versus unmanaged packages. Managed packages come from vendors and receive updates, while unmanaged packages are one-time installs that you can modify. You must understand who can publish to AppExchange, and what prompts appear when installing a package. Flows and other automation can be included in packages, and questions test whether you recognize the implications of installing them.

How Productivity and Collaboration is tested

Questions describe a user adoption or collaboration requirement and ask you to configure tasks, Chatter, the mobile app, or AppExchange to meet it. You might see a scenario where a sales team needs a private Chatter group, or where mobile users need quick access to a custom object. The exam tests whether you understand the visibility rules for Chatter groups and how the mobile app menu reflects profile settings. Candidates lose marks by choosing answers that configure the desktop experience when the requirement specifies mobile, or by selecting a public Chatter group when the scenario requires privacy. Items about AppExchange test your knowledge of package types and what happens when you install a managed package with custom objects and automation. The ten percent weight means you will see several items from this domain, and weak coverage of mobile configuration or Chatter access will cost you marks. The exam expects you to apply these tools in context, not describe their features in isolation.

Data and Analytics Management carries the highest weight on the exam, and it spans importing, exporting, validating, and reporting on data. This domain tests your ability to move data in and out of Salesforce, enforce data quality, and build reports and dashboards that surface the right insights. Candidates who treat this as a light review of reporting basics will struggle, because the exam tests nuances in report types, sharing, and dashboard configuration.

– Data import, export, and backup

Importing data involves choosing between the Data Import Wizard and Data Loader based on volume and complexity. The wizard handles up to 50,000 records and supports accounts, contacts, leads, and custom objects, while Data Loader works with larger datasets and all objects. The exam tests when to use each tool and what happens when you import duplicates. Updating records requires matching on record ID or an external ID field, and mass deleting removes records in bulk. You need to know the implications of deleting records that have child records or are referenced in formulas. Exporting data creates a snapshot for backup or analysis, and you should understand the difference between export and backup. Archiving moves old records out of Salesforce, and the exam tests when archiving is appropriate versus retaining data.

– Data validation and quality

Data validation tools include duplicate rules, matching rules, and validation rules. Duplicate rules identify potential duplicates during record creation or editing, and matching rules define the criteria for comparison. The exam tests how to configure duplicate rules to block or allow duplicates, and what happens when a user overrides a rule. Validation rules enforce data quality by preventing saves when criteria are not met, and you must understand how to write validation rule formulas and what error messages users see. Questions often test the interaction between validation rules and other automation, such as when a validation rule fires during a Flow or an import.

– Report creation and customization

Reports aggregate data from one or more objects, and the exam tests your ability to create report types, customize reports, and use formulas, buckets, and groupings. Report types define which objects and fields are available, and you must know how to join objects with or without related records. Renaming fields in a report type makes labels clearer for end users. Report formulas calculate values, buckets group rows by criteria, and joined reports combine multiple report blocks. Chart settings control how data displays visually, and you should know when to hide details and show only totals. Grouping totals aggregate data at each group level, and the exam tests how to configure groupings to meet a requirement. Troubleshooting reports involves understanding why a field does not appear or why a total seems incorrect.

– Report sharing and dashboard configuration

The sharing model affects report visibility, and the exam tests how folder structure and sharing settings control who sees a report. Reports in private folders are visible only to the owner, while public folders grant access to all users or specific groups. Sharing fields in a report respects object-level and record-level security, so a user sees only the records they have access to. Dashboards display multiple report charts on one page, and you need to know how to create dashboard components, choose data sources, and configure chart types. Subscribing to a dashboard sends periodic snapshots, and dynamic dashboards show data based on the viewer's access. Org licensing limits restrict the number of dynamic dashboards, and you must know when to use a dynamic dashboard versus a static one. The view-as setting lets you see a dashboard as another user, and schedule refresh controls when data updates. Dashboard filters let users change criteria without editing the underlying reports.

How Data and Analytics Management is tested

Questions present a data or reporting requirement and ask you to choose the right tool or configuration. You might see a scenario where you need to import 100,000 records with related data, or where a manager needs a dashboard that shows pipeline by rep. The exam tests whether you understand the difference between the Data Import Wizard and Data Loader, and when to use a validation rule versus a duplicate rule. Items about reports test your knowledge of report types, groupings, and formulas, and the wrong answer often misses a nuance like whether to include records without related child records. Questions about dashboards test your ability to configure components, choose chart types, and apply filters, and candidates lose marks by choosing a static dashboard when the requirement demands dynamic data. The sharing model questions test whether you understand how folder access interacts with record-level security. At seventeen percent, this is the heaviest domain, and weak coverage of report types or dashboard configuration will cost you multiple marks. The exam expects precision in how you apply these tools, not vague familiarity.

Automation is where Salesforce reduces manual work by triggering actions based on criteria or user input. This domain tests your command of flows, approval processes, and assignment rules, and at fifteen percent it is one of the heavier topics. The exam expects you to choose the right tool for a given requirement and understand the order in which automation executes.

– Choosing the right automation tool

Salesforce offers multiple automation tools, and the exam tests your ability to choose the one that fits the requirement. Escalation rules, case assignment rules, and lead assignment rules are purpose-built for specific objects and scenarios, and you should use them when they apply. The default automation user runs certain processes when the triggering user lacks permissions, and you need to know when this applies. AI-driven automation like Einstein recommendations and next-best-action suggestions appear in scenarios where you must decide whether to automate a decision or leave it to users. The exam presents scenarios where multiple tools could work, and the correct answer is the one that meets the requirement with the least configuration and the fewest side effects.

– Flow capabilities and configuration

Flow is the primary automation tool in Salesforce, and the exam tests screen flows, record-triggered flows, and autolaunched flows. Screen flows guide users through a series of steps and collect input, and you need to know when to use a screen flow versus a Lightning page. Record-triggered flows execute when a record is created, updated, or deleted, and you must understand the difference between before-save and after-save flows. Autolaunched flows run without user interaction, triggered by other automation or an API call. The order of execution determines when flows run relative to validation rules, assignment rules, and other automation, and questions often hinge on knowing what has already happened when a flow executes. You should understand how to configure flow criteria, actions, and decision elements, and when to use a loop or a subflow.

– Approval processes

Approval processes route records to approvers based on criteria, and the exam tests how to configure entry criteria, approver selection, and actions for approval or rejection. You need to know the difference between unanimous, first-action, and consensus approval, and when to use each. Approvers can be specified by user, role, or a related field on the record, and the exam presents scenarios where you choose the right method. Rejection actions return the record to the submitter or perform other tasks, and approval actions might update fields, send emails, or lock the record. Questions test your understanding of what happens when an approver is unavailable, and how to configure delegated approvers or approval chains.

How Automation is tested

Questions describe a business process and ask you to configure the automation that implements it. You might see a scenario where a discount requires manager approval, or where a case should escalate when it remains open for two days. The exam tests whether you know the capabilities and limits of each tool, and when to use a flow versus a process or an assignment rule. Candidates lose marks by choosing answers that configure the wrong tool or miss a constraint, such as using a screen flow when the requirement demands a record-triggered flow. Items about the order of execution test whether you understand when validation rules fire relative to flows, and what data is available at each stage. Questions about approval processes test your knowledge of approver selection, rejection handling, and what happens when an approver delegates their responsibility. The fifteen percent weight means this domain appears frequently, and weak coverage of flows or approval processes will cost you across multiple items. The exam expects you to apply automation in context and understand the consequences of each choice.

Agentforce represents Salesforce's AI-driven agent capabilities, and this domain tests your understanding of when and how to deploy AI agents to handle customer or employee interactions. At eight percent, it is the lightest topic, but it is also the newest, and the exam expects you to know use cases, security considerations, and how to configure agents in Agent Builder. Candidates who skip this domain or treat it as optional will lose marks they cannot afford to lose elsewhere.

– Agentforce capabilities and use cases

Agentforce agents handle tasks like answering customer questions, routing cases, or guiding users through processes without human intervention. The exam tests when it is appropriate to use AI agents versus traditional automation or manual processes. You need to understand the scenarios where an agent adds value, such as high-volume inquiries or repetitive tasks, and where human judgment remains necessary. Security is a key consideration, and questions test your knowledge of how agents respect object-level, field-level, and record-level security. Troubleshooting agent permissions involves understanding what data the agent can access and why a user might see an error when interacting with an agent. The exam presents scenarios where you decide whether to deploy an agent or configure a flow, and the correct answer depends on the volume, complexity, and need for conversational interaction.

– Agent Builder configuration and testing

Agent Builder is where you create and maintain agents, and the exam tests how to install, update, and configure prompts and instructions. Prompts guide the agent's responses, and instructions define the agent's behavior in specific situations. You need to know how to write clear instructions that align with business requirements, and when to update an agent's configuration based on feedback. Light testing and conversation preview let you validate an agent's behavior before deploying it to users, and the exam tests your understanding of how to interpret preview results and refine the agent. Questions might present a scenario where an agent gives incorrect responses, and you must identify whether the issue is in the prompt, the instruction, or the agent's permissions.

How Agentforce is tested

Questions describe a business scenario and ask whether an AI agent is appropriate, or how to configure an agent to meet a requirement. You might see a scenario where a company receives hundreds of similar inquiries daily, and you must decide whether to deploy an agent or use case assignment rules. The exam tests whether you understand the security model for agents, including what data an agent can access and how permissions are enforced. Candidates lose marks by choosing to deploy an agent when the scenario requires human judgment, or by configuring an agent without ensuring it has the necessary permissions. Items about Agent Builder test your knowledge of prompts, instructions, and how to use conversation preview to validate behavior. The eight percent weight means you will see fewer items from this domain than from Configuration or Data Management, but each one carries weight and you cannot afford to guess. The exam expects you to apply Agentforce in context and understand its limitations as well as its capabilities.