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

The correct answers are C. Users, D. Public Groups, and E. Roles and Subordinates.

Manual sharing is used when the org-wide default is private and users need to share individual records on a case-by-case basis. Salesforce documentation confirms that manual sharing allows users to share individual records with other users, public groups, and roles.

A public group can include users, roles, and roles with subordinates, which makes it useful when sharing records with departments or groups of people.

A. Permission Set Groups is incorrect because permission set groups grant permissions, not manual record-level sharing.

B. Private Groups is not the standard manual-sharing option tested here.

===========

The correct answer is A.

When custom tabs are deployed through change sets without profile settings or permission sets, the deployed custom tabs are hidden by default for all users. Salesforce Help states that deployed custom tabs are hidden by default unless the change set also includes profiles that set the tab visibility.

Tab visibility is controlled through profile or permission set tab settings such as Default On, Default Off, and Tab Hidden.

Why others are incorrect:

B and C are incorrect because the tabs are not automatically default off or default on for all users.

D is incorrect because the custom tabs are deployed; they are just not visible until access is configured.

===========

AW Computing wants to grant access to all users in the Service Manager role for Opportunities of type Service Agreement in a private sharing model.

Criteria-based sharing rules allow sharing records automatically based on field values (e.g., Type = Service Agreement) to roles, public groups, or users.

Salesforce documentation confirms that when the org-wide default is private, sharing rules are the declarative way to grant access to specific users based on criteria. (Salesforce Help)

Owner-based sharing rules share based on the record owner, not a field criterion.

Apex sharing rules are needed only if declarative sharing is insufficient.

Manual sharing requires user action and is not scalable.

===========

The correct answers are B. External ID and C. Unique.

The legacy ID field should be marked as External ID because Salesforce can use an external ID field to match records during import, integration, and upsert operations. Salesforce documentation confirms that external IDs can be used to create or update records through upsert.

The field should also be marked Unique so Salesforce prevents duplicate legacy ID values. Salesforce custom field attribute documentation states that the Unique option prevents duplicate field values.

Why others are incorrect:

A is incorrect because encrypted text is not the right choice for a matching legacy ID used in upserts.

D is not the best answer because making the field required does not enable upsert matching or prevent duplicate external IDs.

===========

The correct answer is D. Create a new text field and import the formula field values in it.

The existing Specialty__c field is a formula field, so users cannot manually edit it. Formula fields calculate their value automatically from other fields. Since Cloud Kicks now wants Opportunity Specialty__c values to be different from the related Account value, the app builder should create a new editable field, such as a Text field, and then load the existing calculated formula values into that new field for existing Opportunity records.

This preserves historical Opportunity values while allowing sales reps to enter or update Specialty values going forward. Salesforce documentation explains that roll-up/formula-style calculated values are system-derived, while changing custom field types has limitations and requires care when data must be preserved.

A and B are incorrect because a formula field cannot simply become an editable text field while safely preserving all existing calculated values.

C is incomplete because creating a new text field without importing the existing formula values does not preserve the current values on existing Opportunities.

===========

The correct design is to create a master-detail relationship from Testimonial__c to Account and a lookup relationship from Testimonial__c to Contact.

The Account relationship must be master-detail because Salesforce deletes related detail records when the master record is deleted. That matches the requirement that if the Account is deleted, the related Testimonial__c records are also deleted. The Contact relationship must be lookup because the Testimonial__c record must remain when the Contact is deleted. Salesforce lookup relationships can keep the child record and clear the lookup value when the referenced record is deleted.

Why the other options are wrong:

A reverses the required behavior. B would delete the testimonial if either master side caused deletion behavior, which does not fit the Contact requirement. D uses lookup for Account, so it does not guarantee Account deletion will also delete Testimonial__c record

The correct answer is C. Formula Field.

The Service Manager wants a visual color indicator based on the age of an open Case: green for new, yellow for one day old, and red for three days old. This can be implemented with a formula field using conditional logic and the Salesforce IMAGE() function to display different colored indicators based on Case age. Salesforce documentation confirms that the IMAGE function is available in formula fields and can display an image based on field values.

A formula field can evaluate the case age using fields such as CreatedDate , TODAY() , and IsClosed , then return the correct colored image.

A. Custom Button is incorrect because this is not a user action.

B. Quick Action is incorrect because the requirement is display-based, not action-based.

D. Lightning Web Component could do this with code, but a formula field is the simplest declarative Platform App Builder solution.

===========

The correct answer is B. The deployed permission set will only contain changes related to the change set.

When permission sets are included in change sets, the deployment carries permission settings related to the components included in the change set. The existing permission set in production is not completely overwritten as a whole object, and field-level security changes can be included when the relevant fields are part of the deployment. Salesforce documents permission sets and profile settings as access settings that can be included with change sets.

A is incorrect because the whole permission set is not simply wiped and replaced.

C is incorrect because field-level security can be deployed when included properly.

D is close in plain language, but the more accurate exam answer is that the deployed permission set contains only changes related to the change set.

===========

The correct answer is C. Data Export Service.

Salesforce Data Export Service is the native tool used to export backup data from a Salesforce org. It allows admins to create export files of Salesforce data and schedule exports. Salesforce documentation describes Data Export as the feature for exporting backup data from Salesforce.

Important exam note: the question says “daily backup,” but standard Salesforce Data Export scheduling is commonly weekly or monthly depending on edition and settings. Among the listed options, Data Export Service is still the correct Platform App Builder answer.

A is incorrect because refreshing a Full Copy sandbox is not a backup strategy.

B is incorrect because packages move metadata, not org data backup.

D is incorrect because “Support expert” is not the Salesforce backup/export tool.

===========

The correct answers are B. Assign the page to a combination of apps and profiles, C. Make the page the default homepage for specific apps, and E. Make the page the org default.

When activating Lightning pages, Salesforce supports assigning a page as an org default, assigning it to specific Lightning apps, and assigning it to combinations such as app and profile. Salesforce Trailhead also confirms that Lightning record page activation supports org default, app default, and app/record type/profile assignments.

A is incorrect because Lightning page activation uses profiles, not permission sets, for this assignment model.

D is incorrect because Lightning pages are not activated by role as a standard activation option.

===========

The correct answer is C. Record Detail.

The Record Detail component on a Lightning Record Page displays the fields and sections from the object’s assigned page layout. After using Lightning Object Creator to create the object, fields, and data, the app builder must add the Record Detail component if users need to see the fields from the page layout on the Lightning Record Page. Salesforce documentation states that the Record Detail component displays fields and sections from the page layout associated with the object.

Why the other options are incorrect:

Highlights Panel shows key record actions and compact-layout information.

Recommendations displays recommendation records.

Path shows guided stage/status progression, not all page-layout fields.

===========

The correct answer is A. Sharing rules.

Because the Account OWD is Private, users can’t automatically see records owned by users in another branch of the role hierarchy. Salesforce sharing rules are used to extend record access beyond the organization-wide default and role hierarchy. Salesforce documentation states that sharing rules grant additional access to users in public groups, roles, or territories.

Why others are incorrect:

B. Public groups can be used inside a sharing rule, but the public group alone does not share records.

C. Aliases are user display shortcuts, not security controls.

D. Assignment rules assign records; they do not grant cross-team record visibility.

===========

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 correct answer is B. Use a private sharing model granting record access using hierarchy; manage field access with field-level security.

Cloud Kicks needs two different layers of access control:

First, only the sales rep, their manager, and executives above the manager should view the scorecard record. That is a record-level access requirement. A private sharing model with access opened through the role hierarchy supports this because users above a record owner in the hierarchy can access subordinate-owned records. Salesforce states that the role hierarchy opens access vertically to users higher in the hierarchy.

Second, reps must not see the executive comment fields. That is a field-level access requirement, so it should be handled with field-level security. Salesforce separates record-level access from field-level permissions.

A and C are incorrect because custom settings are not used to grant record access. D includes record types, but record types do not secure individual fields; field-level security is required.

===========

The correct answers are C. Custom object, D. Apex class, and E. Custom field.

Change sets are used to move metadata between related Salesforce environments, such as sandbox and production. Salesforce documentation confirms that change sets can migrate components such as custom objects, custom fields, and Apex classes. Salesforce also notes that custom fields can be migrated individually in a change set.

A. Web-to-lead is not one of the common metadata components normally selected as an item in this exam context. B. Standard fields are standard Salesforce metadata and are not moved like custom fields in change sets.

===========

The correct answer is A. Schema Builder.

Schema Builder lets an app builder quickly create and view custom objects, fields, and relationships from one visual interface. Salesforce Trailhead states that Schema Builder is used to visualize and edit the data model, including objects, fields, and relationships.

Lightning Object Creator is mainly used to create objects and fields from a spreadsheet. Manage Field Permissions controls access, not object creation. Developer Console is not the recommended point-and-click tool for this requirement.

===========

The correct answer is D. Create an Apex Trigger on the Account object.

The requirement is conditional: allow Account deletion generally, but block deletion when the Account has open Opportunities. A validation rule is not the correct tool because validation rules evaluate record data during save operations, while this requirement is specifically about preventing a delete operation.

An Apex before delete trigger can query related open Opportunities and call addError() on the Account record to stop the delete. Salesforce Apex documentation confirms that triggers can run before or after delete events, and trigger errors can prevent DML operations from completing.

A is incorrect because removing Delete permission blocks all Account deletion.

B is incorrect because removing the Delete button is not security and does not stop deletion through other channels.

C is incorrect because validation rules are not the right mechanism to block conditional deletes.

===========

The correct answer is B. Apex unit test failures.

When installing a package that contains Apex in a production org, Salesforce runs Apex tests as part of the installation/deployment validation. Salesforce documentation states that package installs or upgrades can fail when Apex test requirements are not met.

Even though the unmanaged package was tested in a Full Copy sandbox, production installation can still fail if Apex tests fail during production validation.

Why others are incorrect:

A, C, and D are not the best answer because the package already installed successfully in a Full Copy sandbox that matched production. The most certification-relevant reason for production failure is Apex unit test failure.

===========

The correct answer is A. Path.

Sales managers want reps to see recommendations, sales strategies, and key fields at each step of the Opportunity sales process. Salesforce Path is designed for exactly this. Path can highlight key fields and provide customized Guidance for Success for each stage of a process.

For Opportunities, Path can show reps which fields matter at each sales stage and provide stage-specific guidance such as qualification tips, sales strategy, or next-step recommendations.

C. Approval Process is for record approval routing.

D. Global Action is for creating or updating records quickly, not guiding users through sales stages.

B is not the correct Salesforce feature for this requirement.

===========