Plat-Admn-202 Salesforce Certified Platform App Builder Exam Topics and Questions
These Salesforce Certified Platform App Builder (Plat-Admn-202) exam topics are organized according to official exam domains to help candidates quickly verify coverage and focus on assessment rather than theory. Each domain is paired with topic-wise Plat-Admn-202 sample questions that reflect how objectives are tested in the actual exam. This structure enables efficient review, targeted self-assessment, and rapid identification of weak areas when preparing for the Salesforce Certified Platform App Builder certification exam.
Let's Practice Free Salesforce Plat-Admn-202 Questions Aligned with Official Exam Topics
This topic sets the boundaries. You need to know where clicks stop and code starts, how far standard security stretches, and what reporting can actually deliver. The weight is modest, but the scope is wide: every decision about access, customization, and visibility traces back to principles tested here. β Declarative versus programmatic customization The exam wants you to recognize the edge of what clicks can do. Formula fields, validation rules, flows, and process automation handle most business logic without code....
This topic sets the boundaries. You need to know where clicks stop and code starts, how far standard security stretches, and what reporting can actually deliver. The weight is modest, but the scope is wide: every decision about access, customization, and visibility traces back to principles tested here.
β Declarative versus programmatic customization
The exam wants you to recognize the edge of what clicks can do. Formula fields, validation rules, flows, and process automation handle most business logic without code. You cross into Apex or Lightning Web Components when you need complex transaction control, callouts to external systems mid-process, or custom user interface behavior that standard components cannot deliver. The scenario will describe a requirement; your job is to pick the lightest tool that works. Over-engineering with code when a flow would suffice costs marks, as does trying to stretch declarative tools past their design limits. Know the ceiling of each approach and the moment it breaks.
β AgentExchange and extending the org
AgentExchange offers prebuilt solutions that extend Salesforce without custom development. The exam tests whether you can identify when an off-the-shelf component solves the problem faster than building from scratch. Scenarios describe a business need; you decide if an existing agent or packaged solution fits, or if the requirement is too specific and demands a custom build. The trap is assuming every problem needs a bespoke answer when a marketplace solution already exists, or conversely, forcing a generic package into a context that needs tailored logic.
β Object, record, and field access
Profiles, permission sets, permission set groups, field-level security, and page layouts all control what users see and do. The exam gives you a scenario with roles, responsibilities, and data sensitivity, then asks which combination locks it down correctly. You need to distinguish between object permissions that govern CRUD at the type level and field permissions that hide or expose individual attributes. Record access comes next: organization-wide defaults set the floor, and sharing rules or manual shares open doors from there. A common mistake is using field-level security when the real problem is record visibility, or trying to restrict with a validation rule when a permission already handles it.
β Sharing solutions and reporting
Sharing rules, teams, hierarchies, and manual sharing each solve different access problems. The exam describes who needs to see what, under which conditions, and you choose the mechanism. A role hierarchy grants upward visibility; sharing rules open lateral access based on criteria or ownership; teams distribute records among collaborators. Get the direction wrong and users either see too much or cannot do their work. Reporting and dashboards appear in scenarios about operational visibility: you need to know when a standard report type suffices, when to build a custom one, and what dashboard features like bucketing or conditional highlighting can deliver without code. The exam will not ask you to write a report formula, but it will ask which report type exposes the relationship you need.
How Salesforce Fundamentals is tested
Eighteen percent means roughly one in six items. Scenarios describe a business requirement and a set of constraints: user roles, data sensitivity, existing customization. You identify the correct boundary between clicks and code, or the right combination of security controls. The wrong answers either over-complicate with programmatic tools when declarative options exist, or try to force declarative features beyond their design. Items on sharing often present a role hierarchy and ask which additional mechanism fills the gap. Items on reporting describe the objects involved and ask which report type or feature surfaces the data. Candidates lose marks by confusing object access with field access, by reaching for Apex when a flow would work, or by choosing a sharing rule when organization-wide defaults already grant the access. Read the scenario for what users must do, then pick the simplest control that satisfies every condition.
The practice test for this exam covers all five topics in the same proportions the real exam uses. The PDF and online format both carry the same question bank, so you can review on paper and time yourself under test conditions later. Both come with a free demo.
The question below asks you to identify the correct combination of security controls given a set of user roles and data access requirements.
Universal Containers has a private sharing model for Accounts and Opportunities and uses Territory Management to grant access to records.
* Sales rep A manually shares an opportunity record with sales rep B.
* Sales rep B has access to the Account even though the Account Is NOT In sales rep B's territory.
* Sales rep C CANNOT see either record.
Based on the information given, why can sales rep B see the Account related to the Opportunity?
Where the first topic set boundaries, this one builds structure. Every object, field, and relationship decision you make shapes what users can see, what reports can join, and how data moves in and out. Twenty percent of the exam turns on whether your schema supports the business process or breaks it. Get the cardinality wrong and records orphan. Pick the wrong field type and data quality collapses. How Data Modeling and Management is tested One in five items. Scenarios describe...
Where the first topic set boundaries, this one builds structure. Every object, field, and relationship decision you make shapes what users can see, what reports can join, and how data moves in and out. Twenty percent of the exam turns on whether your schema supports the business process or breaks it. Get the cardinality wrong and records orphan. Pick the wrong field type and data quality collapses.
How Data Modeling and Management is tested
One in five items. Scenarios describe business entities and their interactions: accounts and contracts, cases and assets, custom objects tracking project phases. You choose the relationship type or explain what happens when you change it. Master-detail enforces tighter coupling than lookup, cascades deletes, and enables roll-up summaries, but it also restricts reparenting and requires a master. Lookup offers flexibility but no automatic aggregation. The exam will describe a requirement like "total contract value must appear on the account" and you decide if the relationship supports it. Field type questions present a current data type and a new business need; you identify what breaks when you convert text to number, or picklist to multi-select. Import and export scenarios describe volume, frequency, and data source; you choose Data Loader, Data Import Wizard, or external objects. Candidates lose marks by ignoring relationship limits, by assuming external objects behave like standard ones, or by picking a field type that cannot support the validation or formula the business needs later.
Relationship and field type decisions are abstract until you see them in context. The question bank shows you thirty or forty variations of the same schema problem, so patterns emerge that reading alone will not surface. Try the demo to confirm coverage before committing.
What follows tests your ability to choose the correct relationship type given a set of business requirements and constraints on record ownership.
Cloud Kicks asked the app builder to insert a list of 25,000 records using deduplication for the Race_Track__c customobject.
Which tool should be used?
This is the largest topic by far. Nearly a third of the exam tests your ability to automate without code. Formulas calculate, validation rules enforce, roll-ups aggregate, and flows orchestrate everything from field updates to multi-step approvals. You will spend more time here than anywhere else, and the questions assume you have built these tools in a live org, not just read about them. β Formulas and roll-up summaries Formula fields derive values from other fields, cross-object references, or functions....
This is the largest topic by far. Nearly a third of the exam tests your ability to automate without code. Formulas calculate, validation rules enforce, roll-ups aggregate, and flows orchestrate everything from field updates to multi-step approvals. You will spend more time here than anywhere else, and the questions assume you have built these tools in a live org, not just read about them.
β Formulas and roll-up summaries
Formula fields derive values from other fields, cross-object references, or functions. The exam gives you a business rule and asks which formula delivers it. You need to know which functions work in which contexts, what happens when a formula references a null value, and when a formula field is read-only versus when it recalculates. Cross-object formulas can span lookup relationships but have depth limits. Roll-up summary fields aggregate child records onto a master in a master-detail relationship. The exam tests whether you recognize when a roll-up is possible, what happens when the relationship type does not support it, and how filter criteria narrow the aggregation. A common mistake is trying to roll up across a lookup, or expecting a roll-up to fire instantly when the child record is part of a bulk operation that has not finished.
β Validation rules
Validation rules prevent saves when data violates a condition. Scenarios describe a business constraint: opportunity close date cannot precede created date, discount cannot exceed twenty percent, certain picklist combinations are forbidden. You write the error condition, not the success condition, so the logic inverts what feels natural. The exam will show you a rule and ask when it fires, or describe a requirement and ask which formula enforces it. You need to know evaluation order: validation runs after workflow field updates in older orgs, but flows can be configured to run before or after. A rule that references a field updated by a flow may pass or fail depending on order. Candidates lose marks by writing the condition backwards, by forgetting that blank fields behave differently in formulas, or by assuming validation fires on every record touch when it only fires on user edits and some automation.
β Flow types and configuration
Screen flows guide users through input steps. Record-triggered flows fire on create, update, or delete. Scheduled flows run at fixed intervals. Autolaunched flows are called by other automation or processes. The exam describes a business process and asks which flow type fits. A record-triggered flow set to run before save can update fields on the same record without a second update statement; after save requires an explicit update. Fast field updates are more efficient than full record updates when you only change a few fields. You need to know when to use a decision element versus a loop, when to call a subflow, and how to pass variables between elements. The exam also tests Flow Builder mechanics: how to reference related records, how to query with filters, and what happens when a query returns no results and the flow does not handle the null case.
β Approval processes, troubleshooting, and Agentforce
Approval processes in Flow define entry criteria, approval steps, and actions at each stage. The exam asks which configuration routes a record to the right approver, or what happens when a step rejects. You need to know how delegated approvers work, how to lock a record during approval, and when an approval recall is allowed. Troubleshooting questions describe a flow that fails or produces unexpected results. You identify whether the error is a null reference, a query that returned multiple records when the flow expected one, or a permissions issue where the running user context lacks access. Debug logs and flow interviews are the tools, but the exam tests conceptual understanding of why a flow broke, not how to read a log line by line. Agentforce automates processes by interpreting natural language instructions and triggering flows or actions. Scenarios describe repetitive tasks and ask when Agentforce is appropriate versus when a standard flow suffices.
How Business Logic and Process Automation is tested
Thirty-two percent means this topic appears twice as often as any other. Scenarios are concrete: a sales process, a service escalation, a contract renewal. You are given business rules and asked which formula, validation rule, or flow implements them. Items on formulas test function syntax, null handling, and cross-object span limits. Validation items describe a constraint and ask for the error condition, or show a rule and ask when it fires. Flow items are the most varied: some ask which flow type to use, others describe a broken flow and ask what went wrong, still others present a process and ask which elements to configure. Approval process items test routing logic and what happens at each decision point. Candidates lose marks by confusing before-save and after-save behavior in record-triggered flows, by writing validation rules that block legitimate data, by choosing a scheduled flow when a record trigger is needed, or by failing to account for null values in formulas. The volume of content is high, so practice identifying the right tool quickly. If you spend three minutes deciding between a formula and a flow, you will run out of time before finishing the exam.
Automation scenarios are hard to hold in your head without examples. The question bank gives you enough variations that you start recognizing the pattern: this constraint needs validation, that calculation needs a formula, this process needs a record-triggered flow. Work through a topic at a time and mark the ones you miss.
The scenario that follows asks you to choose the correct flow type and configuration given a multi-step business process with conditional branches.
After building the data model and the automation, you surface it to users. Page layouts, Lightning pages, actions, and components all shape what people see and how quickly they work. Seventeen percent of the exam tests whether your interface choices make the process faster or add friction. Mobile and desktop contexts diverge, and the exam expects you to know which layout or action fits each. How User Interface is tested Roughly one in six items. Scenarios describe user roles and...
After building the data model and the automation, you surface it to users. Page layouts, Lightning pages, actions, and components all shape what people see and how quickly they work. Seventeen percent of the exam tests whether your interface choices make the process faster or add friction. Mobile and desktop contexts diverge, and the exam expects you to know which layout or action fits each.
How User Interface is tested
Roughly one in six items. Scenarios describe user roles and tasks: a field technician closing a work order on a phone, an account manager updating an opportunity on a laptop, a support agent logging a case. You choose the page layout, the Lightning page template, the action type, or the component. Items on actions ask whether to use a global action, an object-specific action, a quick action that creates a record, or one that updates fields. Items on Lightning pages test when to use App Builder versus when you need a custom component, and which standard components deliver the requirement. Mobile scenarios focus on compact layouts, actions in the mobile publisher, and field order on smaller screens. Candidates lose marks by choosing a custom component when a standard one exists, by placing fields on a page layout that mobile users never see, or by creating a global action when an object-specific one is scoped correctly and avoids clutter. The exam also tests Lightning App Builder mechanics: dynamic forms, visibility filters, and component properties. If you have never built a Lightning page or configured an action in a live org, the abstract descriptions will not be enough.
Interface questions turn on knowing what each component and action type can do. Seeing forty examples of "which action fits this task" trains the pattern faster than memorizing definitions. The demo shows a sample of every topic, so you can confirm the question style before you buy.
What follows presents a mobile user scenario and asks you to select the correct combination of layout, action, and component to optimize the experience.
Building the app is half the job. Getting it from sandbox to production without breaking existing functionality is the other half. Thirteen percent of the exam tests whether you know which sandbox type to use, when change sets work, when they fail, and what packages deliver that change sets cannot. Deployment is where planning errors surface as downtime. How App Deployment is tested One in eight items. Scenarios describe a development pipeline: a new feature in a Developer sandbox, a...
Building the app is half the job. Getting it from sandbox to production without breaking existing functionality is the other half. Thirteen percent of the exam tests whether you know which sandbox type to use, when change sets work, when they fail, and what packages deliver that change sets cannot. Deployment is where planning errors surface as downtime.
How App Deployment is tested
One in eight items. Scenarios describe a development pipeline: a new feature in a Developer sandbox, a full regression test before release, a managed package for external distribution. You choose the sandbox type, the deployment method, or the sequence of steps. Developer sandboxes refresh quickly but hold limited data; Partial Copy sandboxes include a sample; Full sandboxes mirror production but refresh slowly and cost more. The exam asks which type fits the use case. Change set items test whether the component is supported, whether dependencies are included, and what happens when a change set fails mid-deployment. You need to know that change sets move metadata, not data, and that some components like Chatter settings or territory hierarchies cannot travel this way. Package questions ask when to use unmanaged versus managed, and what happens when you upgrade each. Unmanaged packages allow modification after install but offer no upgrade path; managed packages lock components but support versioning. Deployment plan scenarios describe multiple environments and ask for the correct sequence: develop in Developer, test in Partial Copy, stage in Full, deploy to production. Candidates lose marks by choosing a Full sandbox when a Developer would suffice, by attempting a change set that omits a dependency, or by recommending an unmanaged package when the requirement is ongoing updates to a distributed app.
Deployment questions are less about memorizing facts and more about recognizing which method matches the context. The question bank shows you enough scenarios that the decision tree becomes automatic. Check your weak areas by filtering to this topic and working through every item in one session.
The scenario below asks you to recommend the correct sandbox type and deployment method given a set of business and technical constraints.
Ready to Start Practicing?
Access all questions and start your exam preparation journey
Upgrade to Full Plat-Admn-202 Exam Questions π