Platform-App-Builder Salesforce Certified Platform App Builder (Plat-Admn-202) Free Practice Exam Questions (2026 Updated)

The correct next steps are A. Add the fields to the page layout on the object and C. Create a permission set for access to the object and fields .

This is a two-part access problem in Salesforce: users need both security access and user-interface exposure . Creating a custom object and fields in Schema Builder only creates the metadata. It does not automatically guarantee that end users can see, create, edit, or use those records and fields.

C is required because object permissions define the base-level access users have to records for an object, such as create, read, edit, and delete. Salesforce also uses field permissions / field-level security to control whether users can view or edit individual fields. Permission sets are the correct modern mechanism to grant object and field permissions to selected users without changing their base profile.

A is also required because page layouts control the organization of fields on record detail and edit pages. Even if a user has field-level access, the field must be placed on the relevant page layout for normal record-page visibility and editing in the UI. Salesforce specifically separates field-level security as the access-control layer and page layouts as the UI organization layer.

B is incorrect because “Allow Reports” only makes the object available for report creation; it does not grant users object CRUD access or field-level visibility. D is incorrect because data types are assigned during field creation, not after, and choosing a data type does not grant user access.

The correct answer is C. A delegated approver is the recommended Salesforce feature when the assigned approver is unavailable, such as during vacation. Salesforce documentation confirms that users can identify a delegate in approval settings, and delegated approvers can approve or reject approval requests.

This ensures the closed-won Opportunity can still be reviewed before the leaderboard is updated, even though the owner’s manager is away.

Why others are incorrect:

A is not the best recommended setup because relying on an assistant to reassign requests is manual and reactive.

B is incorrect because forwarding approval requests is not the standard solution for planned approver absence.

D is incorrect because assignment rules do not assign delegated approvers for approval processes.

===========

The required metric is the total monetary value of won Opportunities for each Account. Salesforce supports roll-up summary fields on Account that aggregate Opportunity Amount and apply filtering criteria so that only qualifying child records are included. The appropriate configuration therefore uses SUM on Opportunity Amount with a filter restricting the calculation to Opportunities whose Stage represents Closed Won. Option C would incorrectly include open and lost Opportunities. COUNT-based options calculate the number of records rather than total sales value, and the roll-up belongs on the Account because that is where the summarized result must appear. Salesforce ' s current documentation specifically gives the example of an Account roll-up displaying total Opportunity amount and filtering the aggregation to only won Opportunities.

================

The correct answers are A. Set up new public Chatter groups and D. Use post action on the Account object.

Public Chatter groups support open collaboration where company users can share information in a group feed. Salesforce Chatter groups are designed for teams to share information, files, and discussions.

Post action on the Account object allows users to discuss customer accounts directly from the Account record feed. Salesforce Chatter feeds appear on record pages and allow users to follow records and see updates about them.

Why others are incorrect:

Private Chatter groups are not suitable because CK wants all company employees to see the conversations.

Chatter actions to create tasks help assign work, but they do not primarily solve open company-wide collaboration around accounts.

===========

With Account organization-wide defaults set to Private, users cannot automatically see records owned by peers at the same role-hierarchy level. Salesforce sharing rules provide an exception to restrictive organization-wide defaults and can grant additional record access to selected users, roles, or public groups. If User A belongs to a public group targeted by an Account sharing rule, User A can receive access to User C ' s Account while User B does not. Being at the same role level as User C does not provide upward hierarchy access. “View All Fields” concerns field visibility and does not grant access to otherwise inaccessible records. Login access policies concern when or where users can authenticate, not access to one particular Account. Therefore, membership in a public group used by a sharing rule explains the different record visibility.

================

The correct answer is A. TODAY().

The formula needs to calculate how many whole days have elapsed since a marketing communication was sent. The TODAY() function returns the current date as a Date value, which is appropriate for whole-day calculations. Salesforce documentation also shows that TODAY() can be used with addition and subtraction operators for date calculations.

NOW() returns a Date/Time value and can introduce fractional day/time calculations. DATEVALUE() converts a Date/Time or text value into a Date, but the question asks which function should return today’s date for calculating elapsed days. DATETIMEVALUE() returns a Date/Time value, not the desired whole-date calculation.

===========

The correct place to verify whether a change set can be deployed is Inbound Change Sets in the target org, normally Production.

Salesforce guidance says that after uploading a change set from the source sandbox, the app builder goes to Setup → Inbound Change Sets, opens the change set awaiting deployment, and clicks Validate. Validation checks whether the deployment succeeds or fails before committing the changes.

A. Deployment Settings is mainly used to authorize deployment connections and allow inbound changes from another org. C. Deployment Status is used to monitor deployment progress/results, not to initiate validation of an inbound change set.

The correct action is to validate the inbound change set in Production before the deployment window. Salesforce states that an inbound change set can be validated without deploying changes, and validation shows the same success or failure messages that would occur during an actual deployment.

This helps the app builder confirm whether Apex tests, dependencies, and deployment requirements will pass while the developer is away.

Why not others:

A is wrong because removing Apex classes would remove required code.

B is wrong because deployment validation is done from the inbound change set in the target org.

C is not the standard change-set validation process.

The correct answers are A. Enable Feed Tracking on Opportunities and D. Use a record-triggered flow on Opportunity and a Chatter post action.

Feed Tracking is the correct configuration to track field changes on the Opportunity record feed. Salesforce states that feed tracking detects changes to tracked record fields and posts updates to the feed for users who follow the record. Salesforce also allows admins to enable feed tracking for an object and select tracked fields.

A record-triggered flow with a Chatter post action handles the automatic notification requirement. The flow can detect when the Opportunity Close Date changes and post to Chatter, such as mentioning the sales manager or a manager group. Salesforce supports posting to a record’s Chatter feed through automation when feed tracking is enabled.

B is incorrect because an outbound message sends data to an external endpoint, not a manager notification on the Opportunity. C is incorrect because Historical Trending is mainly for reporting on changes over time, not automatic manager notification on the record.

The correct answer is C. A Galaxy__c with Star__c report type will be automatically created.

When a master-detail relationship is created between a parent custom object and a child custom object, Salesforce can automatically generate a standard report type for the parent object with the child object, such as Galaxy__c with Star__c, assuming reporting is enabled for the objects. Salesforce documentation confirms that standard report types are created in certain object relationship scenarios, including lookup and master-detail relationships.

Why the other options are incorrect:

A is incorrect because the report type is based on the parent with child, not the child object with the parent merely as a field.

B is incorrect because a custom report type is not required for this basic master-detail reporting scenario.

D is incorrect because the report type is not created as Star__c with lookup fields from Galaxy__c.

===========

A validation rule is the correct mechanism because the requirement is to prevent invalid ZIP-code formats from being saved. Salesforce supports the REGEX() function in validation rules specifically for enforcing structured input patterns. Salesforce ' s own validation examples include a five-digit American ZIP-code pattern using regular expressions, demonstrating this exact use case. The rule can evaluate the shipping postal-code field and return TRUE whenever the value does not consist of exactly five digits, causing Salesforce to block the save and display an error. Help text only advises users and cannot enforce the format. A Screen Flow would affect only records entered through that particular interface, while an approval process is excessive and does not provide immediate data-format validation. Therefore, B provides consistent enforcement at the record-validation layer.

================

The correct answer is B. Unable to reference the child records.

Formula fields can reference fields on related parent records through cross-object formulas. For example, a formula field on Contact can reference Account fields because Account is the parent of Contact. Salesforce Trailhead shows this pattern by inserting Contact | Account | Account Number in a formula on Contact.

However, the reverse direction is not supported in a normal formula field. An Account formula cannot directly reference values from multiple related Contact child records. Since Contacts are child records of Account, the Contact relationship does not appear in the Account formula editor.

A is incorrect because the issue described is about relationship direction, not the number of formula fields.

C is incorrect because Contact and Account do not need a master-detail relationship for this limitation to apply.

D is incorrect because Salesforce formula character limits are separate from this parent-to-child reference limitation. Salesforce documents formula character limits separately.

===========

The correct answers are C. Lightning App Builder and D. Lightning components in Setup.

In Lightning App Builder, custom Lightning components that are configured for use in Lightning App Builder appear in the Lightning Components pane.

In Setup → Lightning Components, Salesforce allows admins to view a list of Lightning Web Components and Aura components in the org.

Why others are incorrect:

A. Visualforce components in Setup lists Visualforce custom components, not Lightning components.

B. Salesforce Optimizer App analyzes org configuration and recommendations; it is not the place to list available custom Lightning components.

===========

The correct answers are B. Roles and Subordinates, C. Public Groups, and D. Users / Individual Users.

Salesforce manual sharing allows record owners or users with proper access to share individual records with users, public groups, and roles. Salesforce documentation specifically states that manual sharing is used to share individual records with other users, public groups, and roles.

For Lightning manual sharing, Salesforce also describes entering groups, users, roles, or territories in the sharing search box.

So, based on your option wording:

B appears to mean Roles and Subordinates.

C is Public Groups.

D appears to mean Users / Individual Users.

A. Permission Set Groups is incorrect because permission set groups grant object, field, app, and system permissions, not case-by-case record sharing.

E. Private Groups is not the standard answer for this Platform App Builder manual-sharing question.

===========

The correct answer is D. Roll-up summary field.

Cloud Kicks wants to display a count of related Opportunities on the Account record where the Opportunities are Closed Won and have a Close Date within the last year. A roll-up summary field is the correct declarative feature because it calculates values from related records, including counts, sums, minimums, and maximums. Salesforce documentation confirms that roll-up summary fields calculate values from related records and can display values on the parent record.

The app builder can create a roll-up summary field on Account with filter criteria such as:

Stage = Closed Won

Close Date = Last 365 Days / Last Year

Why others are incorrect:

Activity timeline displays activities, not Opportunity counts.

Formula field cannot count multiple child Opportunity records.

Validation rule blocks invalid saves; it does not calculate related record totals.

===========

A Screen Flow is specifically designed for interactive processes that display information, ask users questions, and capture user input across one or more screens. Salesforce states that Screen elements can collect text, choices, dates, lookup values, and other inputs, and multiple Screen elements can create a guided multi-page experience. Screen flows can also be embedded directly on Lightning record pages, which precisely matches the requirement to guide customer care agents from the Case page. A record-triggered flow runs automatically when record data changes and does not provide an interactive wizard. An autolaunched flow normally runs without screens, while a schedule-triggered flow executes at defined times for batches of records. Because agents must actively provide information at several stages of the return process, Screen Flow is the correct declarative solution.

The correct answer is C.

The app builder needs to display only the first five digits from the parent Account’s ZIP+4 custom text field. Salesforce’s LEFT() function returns a specified number of characters from the beginning of a text string, so the correct formula is:

LEFT(Account.Zip_Code__c, 5)

Salesforce formula documentation confirms that LEFT returns characters from the beginning of a text string.

BEGINS() checks whether text starts with specific characters. LPAD() pads text to a specified length. TEXT() converts certain data types to text, but it does not extract the first five characters.

===========

The verified exam answer is D. Add the Path component to the Lightning record page.

Salesforce Path is designed to guide users through stages of a business process. For each step, such as each Opportunity Stage, an app builder can highlight key fields and add guidance for success. Salesforce documentation states that when creating a Path, the app builder can select key fields for each step and enter success guidance.

This fits the requirement because users need to know which fields should be completed at each Opportunity stage.

Important nuance: Path guides users, but it does not hard-enforce stage-based required fields by itself. Salesforce notes that page layouts cannot require different fields in different Path steps; strict enforcement requires validation rules based on the stage/path step.

===========