What the Salesforce Certified Platform App Builder exam covers
- Salesforce Fundamentals166 questions
- Data Modeling and Management164 questions
- Business Logic and Process Automation204 questions
- User Interface120 questions
- App Deployment79 questions
Free Salesforce Certified Platform App Builder practice test questions
A sample of 10 questions with answers and explanations. Sign up free to practice all 733.
-
A nonprofit admin is creating a custom object to track Grant Application records. When defining the object, which name determines how the tab and related lists are labeled when more than one record is referenced (e.g. '3 related Grant Applications')?
- APlural LabelCorrect
- BObject Name (API Name)
- CDescription
- DRecord Name field label
✓ Correct answer: ASalesforce stores two separate label properties on every custom object: a singular Label and a Plural Label, set when the object is created and editable afterward from Object Manager. The Plural Label is what renders in the tab name and in related list headers whenever more than one record is being referenced, so 'related Grant Applications' text pulls straight from that Plural Label value. This scenario is exactly that display case, not a naming or documentation concern. Remember: singular Label names one record, Plural Label names the group.
Why the other options are wrong- BObject Name (API Name) is the developer-facing unique identifier used in code and integrations (ends in __c); it never appears in user-facing tab or related list text.
- CDescription is free-text documentation shown only in Object Manager for admins, it has no bearing on what end users see on tabs or related lists.
- DThe Record Name field label just renames the standard Name field itself (e.g., 'Grant Application Number'), it does not control pluralized counts.
-
When marking a custom field as Unique in Salesforce, which TWO matching options can the admin choose between? (Choose TWO)
- ATreat numbers and letters as being equivalent characters
- BIgnore uniqueness on weekends
- CMatch only the first five characters
- DTreat A and a as different letters (case sensitive)Correct
- ETreat A and a as the same letter (case insensitive)Correct
✓ Correct answer: D, ED and E are correct because Salesforce's Unique attribute provides precisely two ways to compare values for duplicates: treating A and a as different letters, case sensitive, or treating A and a as the same letter, case insensitive, and the admin picks one at field-creation time. The key concept is that this choice only affects letter case in the comparison; it does not touch numbers, does not limit comparison to a subset of characters, and has nothing to do with dates or scheduling. This matters whenever two values differ only in capitalization, since the chosen mode decides whether Salesforce treats them as duplicates or as two valid, distinct entries. The wrong options invent matching behaviors Salesforce does not offer: there is no numbers-and-letters equivalence setting, no weekend exemption, and no partial-character matching limited to the first several characters. Remember the only real choice is case sensitive versus case insensitive, nothing else.
Why the other options are wrong- AThere is no Salesforce uniqueness option that treats numbers and letters as equivalent; the only real choice concerns letter case.
- BThere is no such thing as a day-of-week exemption for uniqueness enforcement; the constraint applies continuously, at all times.
- CThere is no partial-match uniqueness option limited to a set number of characters; the full field value is always compared.
-
A compliance officer at an insurance company wants a full backup of all Salesforce org data on a recurring basis, exported as CSV files, without writing any code. Which feature should be used?
- AData Loader's export operation, run manually every day
- BThe Data Export Service, scheduled automaticallyCorrect
- CSchema Builder's backup mode
- DThe Data Import Wizard's export tab
✓ Correct answer: BFound under Setup at Data Export, this feature is designed exactly for the compliance officer's need: it can be scheduled to run automatically on a recurring cadence and produces a zip file of CSV exports covering the org's data, all without writing any code. Manually running Data Loader's export operation every day would technically move similar data out, but it requires someone to remember and execute it each time, making it far less reliable than a scheduled service built for this purpose. Schema Builder has no backup functionality, and the Import Wizard cannot export at all. Takeaway: recurring, code-free backups point straight to the Data Export Service.
Why the other options are wrong- AManual daily exports through Data Loader require someone to remember and run them every time; they are not the turnkey, scheduled backup solution this scenario calls for.
- CThere is no backup mode within Schema Builder; it is strictly an object and field design tool.
- DThe Data Import Wizard has no export capability at all, only import.
-
An automotive dealership network wants a single vendor-maintained solution installed identically across dozens of dealership orgs, with future enhancements delivered centrally rather than rebuilt at each location. Which package type best supports this model?
- AUnmanaged package
- BManaged packageCorrect
- CAn outbound change set per dealership
- DA Developer Pro sandbox export
✓ Correct answer: BA managed package is the right model because each dealership org is a separate, unrelated org from the vendor's perspective, and a managed package distributed through AppExchange, with its namespace and versioning, lets the vendor push identical, controlled upgrades to every dealership centrally rather than rebuilding the solution at each location. This matches exactly what the network wants: one vendor-maintained solution installed consistently everywhere. An unmanaged package has no upgrade mechanism, requiring manual rework at every single dealership for future enhancements, change sets require a deployment connection between related orgs that unrelated dealership orgs would never share with the vendor, and a sandbox export is not a distribution mechanism for reaching separate customer orgs at all.
Why the other options are wrong- AUnmanaged packages have no upgrade mechanism at all, requiring manual rework at every single dealership for future enhancements.
- CChange sets require a deployment connection between related orgs, which unrelated dealership orgs would never share with the vendor.
- DA sandbox export is not a distribution mechanism for reaching separate, unrelated customer orgs across dozens of dealerships.
-
An analyst tries to add a chart directly to a tabular report but finds the option unavailable. Why?
- ATabular reports have no groupings, so charts are not supportedCorrect
- BCharts require the report to be in a public folder
- CCharts can only be added from a dashboard, never a report
- DTabular reports require Enterprise Edition to chart
✓ Correct answer: AThe correct answer is A because tabular reports list flat rows with no subtotal groupings at all, and a chart needs a summarized data series, grouped values with subtotals, to render bars, slices, or lines against. The key concept is that charting depends on the same grouping structure that summary, matrix, and joined formats provide but tabular does not. This scenario fits directly since the analyst is working in tabular format specifically. The remaining options misattribute the limitation to folders, placement, or edition, as the distractors explain. The takeaway is that charting always requires a grouped report format.
Why the other options are wrong- BFolder visibility and sharing settings have no bearing on whether a chart option is available on a given report.
- CReport charts can be added directly to summary, matrix, and joined reports, not only added indirectly through a dashboard.
- DReport charting availability is not gated by Salesforce edition in this way; the report format itself is the actual limiting factor.
-
OWD for Opportunities is Private. A Sales Rep reports to a Sales Manager in the role hierarchy. What access does the Sales Manager automatically have to the rep's Opportunities?
- ANo access; hierarchy needs open OWD
- BRead and Write accessCorrect
- CRead Only access, never Write
- DOnly with a sharing rule too
✓ Correct answer: BBecause the rep owns the Opportunity and can both view and edit it, role hierarchy extends that same Read and Write level up to the Sales Manager automatically, with no Sharing Rule or manual step required. This is the defining behavior of hierarchy-based access: it exists specifically to give upward visibility even when OWD is Private, which is exactly the situation described. The takeaway: hierarchy access mirrors the owner's access level, so if the owner can edit, so can everyone above them in the chain.
Why the other options are wrong- ARole hierarchy is designed to provide access precisely when OWD is restrictive, like Private; it does not require an open OWD to function.
- CHierarchy grants the same access level the subordinate has, which includes Write since the rep can edit their own record.
- DNo separate Sharing Rule is needed here; the hierarchy relationship alone is sufficient to grant this access.
-
An events company wants a roll-up summary on Event that only counts related Registration records, connected by master-detail, where Status equals Confirmed, excluding Cancelled ones. What roll-up summary feature enables this?
- AA cross-object formula field
- BFilter criteria on the roll-up summary fieldCorrect
- CA separate validation rule on Registration
- DA duplicate rule on Event
✓ Correct answer: BThe answer is B. Salesforce's roll-up summary configuration includes an optional filter criteria section, letting the admin specify a condition, here Status equals Confirmed, so that only Registration records meeting it count toward the total, effectively excluding Cancelled ones without any extra automation. This is a native, declarative feature built directly into the roll-up field's setup screen. A cross-object formula field (A) cannot aggregate across multiple child records at all, filtered or not, a validation rule (C) only blocks or allows a save and has no role in shaping which records feed an aggregation elsewhere, and a duplicate rule (D) manages detecting duplicate records, unrelated to this scenario. Takeaway: filter criteria on the roll-up itself is the native way to scope which child records get aggregated.
Why the other options are wrong- AA formula field cannot aggregate values across multiple child records at all, filtered or otherwise, so it cannot achieve this.
- CA validation rule only blocks or allows saves; it cannot filter which records are included in a roll-up summary's aggregation.
- DA duplicate rule manages detection of duplicate records and has no bearing on roll-up aggregation or its filter criteria.
-
A university's admissions office has an Apex trigger on Application that needs to hand off reusable, declarative logic (calculating a rank score and creating a follow-up Task) without showing any screen to a user. Which TWO characteristics correctly describe the Flow the developer should build and call from Apex? (Choose TWO)
- AIt should be an Autolaunched Flow with no screensCorrect
- BIt can be invoked directly from Apex codeCorrect
- CIt must include at least one Screen element
- DIt only runs on a time-based schedule
- EIt requires a Process Builder process to fire first
✓ Correct answer: A, BOptions A and B are correct because an Autolaunched Flow is the declarative flow type built with no Screen elements and designed to be invoked on demand from Apex code, a subflow, a REST call, or a Quick Action, running entirely in the background with nobody watching. The key concept is that this flow type is the bridge between imperative code and reusable declarative logic, letting the admissions office's Apex trigger hand off the rank-score calculation and Task creation to a maintainable flow instead of duplicating that logic in code. An Autolaunched Flow must not include a Screen element, since there is no user present when Apex calls it, so requiring a Screen element would be wrong. Only a Scheduled-Triggered Flow runs purely on a time-based schedule, this flow instead runs on demand whenever Apex invokes it. Process Builder is a legacy tool being retired and is not a prerequisite for calling an Autolaunched Flow from Apex. Takeaway: Apex-callable, screen-free background logic is always an Autolaunched Flow.
Why the other options are wrong- CAn Autolaunched Flow must not include a Screen element, since no user is present to view a UI when Apex invokes it in the background.
- DOnly a Scheduled-Triggered Flow runs purely on a time-based schedule; an Autolaunched Flow invoked from Apex instead runs on demand whenever the code calls it.
- EProcess Builder is a legacy tool being retired, and an Autolaunched Flow can be called directly from Apex without any Process Builder process involved at all.
-
An airline's flow needs to hold a list of multiple Baggage Claim records retrieved by a Get Records element so a later Loop element can process each one. What kind of variable should be created to hold that list?
- AA single Record Variable
- BA Formula resource
- CA Record Collection VariableCorrect
- DA Text Template
✓ Correct answer: CThe answer is C, a Record Collection Variable. Since Get Records may return more than one Baggage Claim, the results need a variable that can hold a list of records, which a Loop element then iterates over one at a time. A single Record Variable (A) can hold only one record's values, not a list. A Formula resource (B) performs a calculation and holds no records at all. A Text Template (D) composes merge-field message text; it is not built to hold records. Takeaway: whenever Get Records might return more than one record, the target variable must be a Record Collection Variable.
Why the other options are wrong- AA single Record Variable can only hold one record's field values, not a list of multiple Baggage Claim records.
- BA Formula resource performs a calculation and returns a single value; it does not hold a list of retrieved records.
- DA Text Template composes merge-field message text; it is not built to hold a list of records for a Loop to iterate.
-
On a Lightning record page using Dynamic Forms, can an admin mark an individual field component as Required or Read-Only for that page, similar to how page layouts allowed it?
- ANo, those properties only ever existed on page layouts
- BYes, each field component has its own such propertiesCorrect
- CYes, but only by writing a validation rule
- DNo, Dynamic Forms fields are always read-only
✓ Correct answer: BJust as a page layout let an admin mark a field Required or Read-Only for that layout, each Dynamic Forms field component has the equivalent properties available directly in its own settings, scoped to that specific field placement on the page rather than to a shared layout setting. This means moving to Dynamic Forms does not lose any of that familiar control, it simply relocates it onto the individual component. Claiming those properties only ever existed on page layouts is inaccurate since the field component carries its own equivalent; a validation rule is a different, save-time mechanism not needed just to mark a field required or read-only on the page; and fields are editable by default unless explicitly marked read-only, they are not always locked. Takeaway: Dynamic Forms fields keep the same Required and Read-Only controls, just moved to the field component itself.
Why the other options are wrong- AThis is inaccurate; Dynamic Forms field components carry their own equivalent Required and Read-Only properties, scoped to that field's placement on the page.
- CA validation rule is a different, save-time mechanism and is not needed just to mark a field required or read-only on the page itself.
- DFields are editable by default unless the admin explicitly marks them read-only; they are not automatically locked simply by using Dynamic Forms.
Who this Salesforce Certified Platform App Builder practice exam is for
This practice set is for anyone preparing for the Salesforce Certified Platform App Builder exam - from first-time candidates building a foundation to experienced Salesforce practitioners doing a final review before test day. If you learn best by working through realistic questions and reading why each answer is right or wrong, it is built for you.
How to use this Salesforce Certified Platform App Builder practice exam
- Start with the free sample questions above to gauge your current baseline.
- Read the full explanation on every question, including why each wrong option is wrong.
- Track your weak domains and focus your study where you are losing the most marks.
- Once you are scoring consistently well, take a timed, full-length mock exam.
- Use your readiness score to decide when you are ready to book the real Salesforce Certified Platform App Builder exam.
Related Salesforce resources
- Salesforce Certified Platform App Builder study guideKey concepts
- Salesforce practice examsAll Salesforce
- Certification pathWhere this fits
- Certification exam guides & tipsBlog
- Plans & pricingFree & paid
- How these questions are written and reviewedMethodology
- Report a problem with a questionCorrections
- Salesforce Certified Platform Developer I practice examRelated
- Salesforce Certified Agentforce Sales Consultant practice examRelated
- Salesforce Certified Agentforce Specialist practice examRelated
Salesforce Certified Platform App Builder practice exam FAQ
How many questions are in the Salesforce Certified Platform App Builder practice exam on CertGrid?
CertGrid has 733 practice questions for Salesforce Certified Platform App Builder, covering 5 exam domains. The real Salesforce Certified Platform App Builder exam is 60 qs in 105 min. CertGrid's timed mock is a fixed 60 questions.
What is the passing score for Salesforce Certified Platform App Builder?
Salesforce publishes a 73% passing score for this exam. CertGrid scores this mock on its own 0-1000 scale, on which 730 is the same threshold; the 0-1000 figure is ours, not Salesforce's. You have about 105 min to complete it. CertGrid tracks your readiness against the exam objectives so you know where to focus.
Are these official Salesforce Certified Platform App Builder exam questions?
No. CertGrid is an independent practice platform. We do not provide real or leaked exam questions. Our questions are original and designed to help you practice the concepts, scenarios, and difficulty style of the Salesforce Certified Platform App Builder exam.
Is there a free Salesforce Certified Platform App Builder practice test?
Yes. You can take a free Salesforce Certified Platform App Builder practice test straight away: a fixed set of 20 practice questions for this exam, retryable as often as you like, with no credit card required. You get readiness scoring and a weak-domain breakdown on those questions. Paid plans unlock the full 733-question bank, timed mock exams and full-bank domain analytics.
What CertGrid is (and is not)
CertGrid is an independent IT certification practice platform for Azure, AWS, Google, Cisco, Security, Linux, Kubernetes, Terraform, and other certification tracks. It provides objective-mapped practice questions, readiness scoring, weak-domain drills, and explanations to help learners understand what to study next.
Independent & original. CertGrid is an independent practice platform and is not affiliated with or endorsed by Salesforce. Questions are original practice items designed to mirror certification concepts and exam style. CertGrid does not provide official exam questions or braindumps.