Certified Platform App Builder — Free Practice Questions
10 free sample questions from a bank of 463, with the correct answers and explanations. No signup required — start practising right now.
1Universal Containers manages internal projects by department using a custom object called Projects. Only employees in the project's respective department should have view access to all of the department's project records. If an employee changes job roles and moves to another department, the employee should no longer have access to the projects within their former department.
Which two options will meet these requirements assuming the organization-wide default for Projects is set to Private? (Choose two.)
Create a criteria-based sharing rule using the Project's department that grants access to users by profiles.
Create a criteria-based sharing rule using the Project's department that grants access to users by permission sets.
Create a criteria-based sharing rule using the Project's department that grants access to users by roles.
Create a criteria-based sharing rule using the Project's department that grants access to users by public groups.
Answer: C, D
The short version
CD — Criteria sharing to roles and public groups meets department-private Projects needs. OWD Private blocks broad view, and department staff change over time. The settled key is CD because role plus public-group targets move with the user while profiles and permission sets cannot be used there.
Key concepts in this question
OWD Private: baseline that hides Projects records unless sharing opens them by criteria.
Criteria-based sharing: rule that shares when record fields meet values, here department match.
Roles: hierarchy-based targets that follow job moves automatically when the user role changes.
Public groups: flexible collections that can mirror departments and update as people transfer.
Profiles and permission sets: object and field access controls, not valid targets for criteria sharing rules.
Why CD is correct
CD is correct because Salesforce allows criteria-based sharing rules to target roles and public groups, both of which re-evaluate when an employee changes department. A mover loses old department access and gains new access without manual resharing. Profiles and permission sets are not selectable as share-with targets for this rule type, so only C plus D satisfies the dynamic requirement.
Why the others are wrong
A. Profiles control object permissions and cannot be the share-with target of a criteria rule.
B. Permission sets grant functional access but likewise cannot receive a criteria-based share.
Certified-Platform-App-Builder exam tip
For criteria sharing remember roles plus public groups as share-with targets; profiles and permission sets never qualify.
2An app builder would like to streamline the user experience by reflecting summarized calculations of specific fields on various objects.
Which three field types could be used in roll-up summary fields to accomplish this? (Choose three.)
Checkbox
Date
Percent
Time
Currency
Answer: B, C, E
The short version
BCE — Date, percent and currency work in roll-up summaries for MIN and MAX. Roll-ups aggregate child values onto a parent, but only certain field types qualify. The settled key is BCE because those three are documented as allowed while checkbox and time are not.
Key concepts in this question
Roll-up summary: parent field that counts, sums, or takes MIN and MAX over child records.
Date support: allowed for MIN and MAX so parents can show earliest or latest child dates.
Percent and currency: numeric types allowed for MIN, MAX and SUM style aggregation.
Checkbox: boolean that lacks ordering for MIN and MAX in roll-up context.
Time: unsupported type for roll-up summaries in the documented matrix.
Why BCE is correct
BCE is correct because Salesforce help lists currency, percent, date and date-time as available when MIN or MAX is selected. Checkbox has no meaningful minimum and time is excluded from the type matrix. Choosing B plus C plus E therefore reflects summarized calculations that the platform actually permits on master-detail style roll-ups.
Why the others are wrong
A. Checkbox cannot be used for MIN or MAX roll-up math, so it is excluded from valid types.
D. Time is not in the supported roll-up type list, unlike date and date-time.
Certified-Platform-App-Builder exam tip
For roll-ups memorize date plus percent plus currency for MIN-MAX; checkbox and time are out.
3A customer service representative at a call center would like to be able to collect information from customers using a series of question prompts.
What could be used to accomplish this?
Workflow Rules
Salesforce Connect
Flow
Process Builder
Answer: C
The short version
C — Flow collects call-center information through guided question prompts. Reps need step-by-step screens that branch on answers. The settled key is C because Flow is the declarative interview engine for that pattern.
Key concepts in this question
Flow: declarative automation with screens, decisions and data actions for guided interviews.
Workflow Rules: record-triggered field updates and alerts without interactive screens.
Salesforce Connect: external-object integration for viewing outside data, not for prompting users.
Process Builder: record-triggered branching automation now superseded, still without screen interviews.
Question prompts: sequential data capture that maps directly to Flow screens and choices.
Why C is correct
C is correct because only Flow provides screen elements, choices and conditional paths that walk a rep through questions and store responses. Workflow and Process Builder run in the background on save and cannot interview the user. Salesforce Connect surfaces external rows rather than collecting new inputs, so Flow is the complete solution.
Why the others are wrong
A. Workflow Rules automate behind the scenes and offer no screen prompts for callers.
B. Salesforce Connect integrates external data and does not build guided question sequences.
D. Process Builder triggers on records without screens, so it cannot conduct a prompt series.
Certified-Platform-App-Builder exam tip
When the stem says series of question prompts choose Flow screens; background tools lack interviews.
4An app builder has been asked to provide users a way to identify a Contact's "Preferred Contact Method" directly on the Contact record. Users need to be able to identify whether a phone number or an e-mail is the Contact's preferred communication method.
What field type will allow the app builder to accomplish this with the fewest fields possible?
Picklist
E-mail
Checkboxes
Formula
Answer: A
The short version
A — Picklist captures preferred contact method in one field. Phone versus email needs a single choice, not two flags or extra objects. The settled key is A because picklist stores one value with fewest fields.
Key concepts in this question
Picklist: single field offering defined values such as phone or email for consistent choice.
Fewest fields: design goal that favors one field over multiple booleans.
Email field: stores an address but does not record which channel is preferred.
Checkboxes: each holds true or false, so two methods would need two fields plus validation.
Formula: derives display from other fields and cannot itself collect the preference.
Why A is correct
A is correct because a picklist lets users select the preferred method directly on Contact with one column and built-in reporting. Two checkboxes would double fields and allow invalid both-on states. Email and formula types solve addressing or display, not preference capture, so picklist minimizes schema while enforcing valid choices.
Why the others are wrong
B. Email stores an address but cannot indicate whether phone or email is preferred.
C. Checkboxes would require two fields and extra logic to prevent dual selection.
D. Formula displays calculated text and cannot serve as the data-entry point for preference.
Certified-Platform-App-Builder exam tip
For one-choice preference with fewest fields choose picklist; avoid dual checkboxes.
5Universal Containers uses a private sharing model for opportunities. This model cannot be changed due to a regional structure. A new sales operations team has been created. This team needs to perform analysis on Opportunity data, and should have read and write access to all Opportunities.
Which two are recommended solutions for the app builder to give the users appropriate access? (Choose two.)
Add a manual share for all opportunities with each user on the sales operations team.
Create a criteria-based sharing rule to share all opportunities with the sales operations private group.
Create a criteria-based sharing rule to share all opportunities with the sales operations public group.
Add a permission set with "View All" and "Modify All" opportunity permissions enabled.
Answer: C, D
The short version
CD — Public-group sharing plus View All and Modify All gives ops read-write on all Opportunities. OWD stays private for regions, yet the new team needs broad analysis access. The settled key is CD because sharing opens records while permission-set rights ensure object power.
Key concepts in this question
Private OWD: Opportunities hidden by default due to regional structure that cannot change.
Criteria sharing to public group: rule that shares every Opportunity with the sales-operations group.
View All plus Modify All: object permissions that grant full record access regardless of sharing.
Manual shares: one-by-one grants that cannot scale to all records and team churn.
Private group: not a valid sharing target; public groups are required for this pattern.
Why CD is correct
CD is correct because C shares all Opportunities to the operations public group under the unchanged private model, while D adds View All and Modify All for robust read-write including reports and transfers. Together they handle both record visibility and object capability. Manual sharing and private-group targeting fail on scale and validity, leaving C plus D as recommended.
Why the others are wrong
A. Manual shares for every Opportunity with each user cannot scale and break on new records.
B. Sharing to a private group is invalid; Salesforce requires a public group as the target.
Certified-Platform-App-Builder exam tip
For all-records access under Private OWD pair public-group sharing with View All plus Modify All.
6Universal Containers has a requirement that an Opportunity should have a field showing the value of its associated account's billing state. This value should not change after the Opportunity has been created.
What is the recommended solution to configure this automation behavior?
Formula field
Apex
Roll-up summary field
Workflow
Answer: D
The short version
D — Workflow stamps billing state at creation so it never changes later. The Opportunity needs a snapshot, not a live lookup. The settled key is D because workflow field update copies the value once.
Key concepts in this question
Snapshot need: preserve account billing state as it was when the Opportunity was created.
Formula field: live cross-object display that would change if the account state later changes.
Roll-up summary: aggregation from children, not a parent-to-child copy, and unsuitable here.
Apex: code that could copy values but is heavier than declarative automation for this task.
Workflow field update: rule that writes a static value on create and leaves it untouched.
Why D is correct
D is correct because only a workflow that fires on creation and updates a text or state field produces a frozen copy. A formula would recalculate on every view and defeat the do-not-change requirement. Apex and roll-ups miss the declarative snapshot pattern, so workflow is the recommended low-code solution.
Why the others are wrong
A. Formula stays live to the account and would change after creation, violating the freeze need.
B. Apex can work but is overkill when declarative workflow already snapshots simply.
C. Roll-up summarizes children onto parents and cannot copy account to Opportunity at create.
Certified-Platform-App-Builder exam tip
For snapshot-not-live from parent at create choose workflow field update, never formula.
7Universal Containers conducts evaluations of its sales reps using a custom object consisting of numerical scores and executive comments. The company wants to ensure that only the sales reps, their managers, and their manager's executives can view the rep's evaluation record, but the reps should not be able to view the executive comment fields on their review.
How can these requirements be met?
Use a private sharing model granting record access using hierarchy; manage field access with record types and field-level security.
Use a private sharing model granting record access using custom settings; manage field access with page layouts and field-level security.
Use a private sharing model granting record access using hierarchy; manage field access with field-level security.
Use a private sharing model granting record access using custom settings; manage field access with record types and page layouts.
Answer: C
The short version
C — Private sharing with hierarchy plus field-level security meets evaluation privacy. Record access must follow management chain while comments stay hidden from reps. The settled key is C because hierarchy handles records and field security handles columns.
Key concepts in this question
Private OWD: evaluations hidden except via hierarchy or sharing.
Role hierarchy: grants managers and executives above the rep automatic record view.
Field-level security: hides executive comment fields from reps while showing scores.
Custom settings: app config storage, not a record-sharing mechanism.
Page layouts plus record types: control arrangement, not true field security.
Why C is correct
C is correct because hierarchy sharing gives the rep, manager and executive chain record access without opening all evaluations. Field-level security then removes executive comments from rep profiles while keeping them for leaders. Other combos misuse custom settings for sharing or rely on layouts that can be bypassed, so only C enforces both dimensions.
Why the others are wrong
A. Record types plus layouts manage display, not secure hiding of sensitive fields.
B. Custom settings do not grant record access, so that sharing leg fails.
D. Custom settings plus layouts again misses true record sharing and field security.
Certified-Platform-App-Builder exam tip
Pair hierarchy for record chain access with field-level security for column hiding on reviews.
8Which two statements are true about field update actions from workflow rules and approval processes? (Choose two.)
Field updates are tracked in the History related list of a record regardless of whether or not history tracking is set for those fields.
Field updates to records based on workflow rules and approval processes do not trigger Validation Rules.
Field updates are not available on currency fields if the organization uses multi-currency.
Field updates with "Re-evaluate Workflow Rules" selected can cause a recursive loop if the update field is included in a workflow.
Answer: C, D
The short version
CD — Currency limits plus re-evaluation loops are the true field-update cautions. Workflow updates behave specially with multi-currency and recursion. The settled key is CD because both statements match documented considerations.
Key concepts in this question
Field update: workflow or approval action that writes a value without user edit.
Multi-currency: org where currency fields use record currency and face update limits.
Re-evaluate Workflow Rules: option that can retrigger rules and loop if the updated field is in criteria.
History tracking: requires explicit feed setup; updates are not auto-tracked without it.
Validation rules: generally bypassed by workflow field updates, which can invalidate prior data.
Why CD is correct
CD is correct because Salesforce notes field updates are unavailable on certain currency setups when multi-currency is active, and enabling re-evaluate can cause recursion when the updated field remeets rule criteria. Those two cautions are explicit in workflow considerations. History auto-tracking and validation triggering are the opposite of actual behavior, so C plus D stands.
Why the others are wrong
A. Updates are not auto-tracked in History without enabling history tracking for the field.
B. Workflow-driven updates do not trigger validation rules, so claiming they do is false here.
Certified-Platform-App-Builder exam tip
Remember workflow updates skip validation, need history setup, face currency limits and can loop on re-evaluate.
9Which two objects can be members of a Campaign? (Choose two.)
Opportunity
Account
Lead
Contact
Answer: C, D
The short version
CD — Leads and Contacts are the classic Campaign members. Campaigns track prospects and people engaged by marketing. The settled key is CD because those two objects are built as members.
Key concepts in this question
Campaign: marketing initiative object that groups outreach and responses.
Campaign Members: junction linking Leads and Contacts to a Campaign with status.
Leads: unconverted prospects who can be added as members for nurturing.
Contacts: existing people who join campaigns for events and journeys.
Accounts and Opportunities: related through other means, not classic member records in this bank key.
Why CD is correct
CD is correct because Salesforce models Campaign Members specifically around Lead and Contact IDs with member status. That supports prospect-to-customer journeys and reporting on influence. Accounts and Opportunities relate to campaigns differently and are not members under the settled key, so C plus D matches the data model.
Why the others are wrong
A. Opportunity links to campaigns via influence, not as a Campaign Member record here.
B. Account linkage is newer or indirect and is not a classic member under this key.
Certified-Platform-App-Builder exam tip
For Campaign members default to Leads plus Contacts; treat account influence as separate.
10At Universal Containers, the VP of Service has requested a visual indicator flag on each case, based on the case priority. High-priority case should be flagged red, medium-priority should be flagged yellow, and low-priority cases should be flagged green.
Which two formulas will accomplish this requirement? (Choose two.)
AD — Both flag formulas must wrap logic in IMAGE for display. Priority needs red, yellow and green icons. The settled key is AD because only A and D use IMAGE with CASE or nested IF correctly.
Key concepts in this question
IMAGE function: only way to render a flag graphic from a formula on the record.
CASE: compact mapping of picklist values to image paths for low, medium and high.
Nested IF plus ISPICKVAL: alternative that checks priority step by step and returns paths.
Bare path: returning a URL string without IMAGE shows text, not a visual flag.
Syntax completeness: each branch must resolve to a path and include alt text handling.
Why AD is correct
AD is correct because A uses IMAGE around CASE to map priorities to green, yellow and red flags, while D uses IMAGE around nested IF with ISPICKVAL to achieve the same visual result. B and C omit IMAGE and would display URLs as text rather than flags. Both A and D therefore meet the visual-indicator requirement with valid functions.
Why the others are wrong
B. IF without IMAGE returns text paths and never renders the flag image.
C. CASE without IMAGE likewise yields text instead of a graphical indicator.
Certified-Platform-App-Builder exam tip
For visual flags always require IMAGE; CASE and nested IF are both valid insides.