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

The primary object of a custom report type is a fundamental design choice and cannot be changed after the report type is saved. Salesforce explicitly states in both the Enhanced and Legacy Custom Report Type Builder documentation that after saving a custom report type, the selected primary object cannot be changed. The primary object determines the base set of records represented by the report type and controls how additional related objects can subsequently be included. Consequently, the app builder must choose the Job Application object deliberately before saving the report type. Deployment does not permanently prevent a custom report type from being deleted, and the other options do not describe the core configuration limitation being tested. Therefore, B is the documented Platform App Builder consideration.

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

The correct answers are A. Use a master-detail relationship between the Park and Trail objects and C. Use a roll-up summary field on the Park record to show the total number of trails .

To show the total number of child Trail records on the parent Park record without code, the app builder should use a roll-up summary field . Salesforce documentation states that roll-up summary fields display values on a master record based on related detail records.

That means Park should be the master object and Trail should be the detail object. Then a roll-up summary field on Park can count the related Trail records.

B is incorrect because standard lookup relationships do not support roll-up summary fields.

D is incorrect because a formula field cannot count multiple child records.

===========

The correct answer is A. Account Object .

Roll-up summary fields are created on the parent object , because the summary value is displayed on the parent record. Here, the KPI values need to appear for each Account , and they summarize related Opportunity records. Therefore, the app builder should go to the Account object in Object Manager and create roll-up summary fields there.

For this requirement, the app builder would create separate roll-up summary fields on Account, such as:

Count of open Opportunities

Count of won Opportunities

Salesforce documentation describes roll-up summary fields as fields that calculate values from related records, such as records in a related list.

C. Opportunity Object is incorrect because Opportunity is the child/related record being counted.

D. Lightning App Builder is incorrect because Lightning App Builder controls page layout/components, not the creation of roll-up fields.

B. Lightning Object Creator is used to create objects from spreadsheets, not build rollups.

===========

The correct answer is B. Add the standard Chatter feed component.

In Lightning App Builder, Salesforce provides a standard Chatter component. Salesforce documentation states that the Feed component was renamed Chatter in Lightning App Builder and is used to place the publisher and feed on a record page.

A is incorrect because a custom Chatter feed component is not needed.

C is incorrect because this does not come from the AppExchange/App College.

D is incorrect because Chatter feed is not added by using the standard related list component.

===========

An indirect lookup relationship is used when an external object must relate to a standard or custom Salesforce object and the external data does not contain Salesforce record IDs. Salesforce requires the parent Salesforce object to contain a custom field marked External ID and Unique . Values from the external object ' s indirect lookup field are matched against this external ID field to establish the relationship. Salesforce specifically states that indirect lookups link a child external object to a parent standard or custom object using a custom unique External ID field. TEXT(Id) does not create such a relationship key, and CASESAFEID() merely converts Salesforce IDs to their 18-character representation. A normal Salesforce Record ID is used for standard lookup relationships, not indirect lookups.

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

The correct tool is Data Loader.

Cloud Kicks needs to insert over 1 million net new Account records. Salesforce Data Loader is the correct tool for large-volume imports because it supports bulk insert, update, delete, and export operations. Salesforce’s Data Loader documentation describes it as a client application for bulk data import and export, including inserting Salesforce records. Salesforce also distinguishes it from the Data Import Wizard, which is limited to smaller imports.

Why the other options are wrong:

Data Import Wizard is not suitable for over 1 million records because it is intended for much smaller imports. Schema Builder is for viewing and creating data model components, not loading a million records. Lightning Object Creator creates objects from spreadsheets, not mass-inserting large Account datasets into an existing model.

The correct answer is B.

Universal Containers needs the 18-digit Salesforce record ID for Opportunity records when exporting to Excel. Salesforce’s CASESAFEID() formula function converts a 15-character Salesforce ID into the 18-character, case-insensitive ID format that works better with external tools such as Excel. Salesforce documentation specifically describes CASESAFEID as the function used to convert IDs to 18-character IDs for Excel compatibility.

Correct formula:

CASESAFEID(Id)

A. VALUE(14) is unrelated. C. TEXT(Id) does not convert the ID to the 18-character case-safe format. D. ISNUMBER(Id) only checks whether a value is numeric, which is not useful for Salesforce record IDs.

===========

Lightning Object Creator, represented in current Salesforce Setup as creating a custom object from a spreadsheet, is specifically designed for this scenario. Salesforce states that administrators can upload an XLSX, CSV, or Google Sheet and use the wizard to create a custom object, derive its fields from the spreadsheet columns, and populate the new object ' s records as part of the same process. This directly meets all three requirements: create the object, create the fields, and load the spreadsheet data. Schema Builder can create objects and fields but does not simultaneously import the spreadsheet ' s record data. Data Loader imports large volumes into existing objects but does not automatically construct an object and its schema. Data Import Wizard similarly assumes supported target objects already exist.

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

Use a Record-Triggered Flow optimized for Actions and Related Records.

Submitting a record for approval is an action in Flow. Salesforce provides a Submit for Approval action, and after-save record-triggered flows are used when the automation needs to perform actions or work with related records after Salesforce saves the triggering record.

Option A is wrong because Fast Field Updates is the before-save path, mainly for updating fields on the triggering record. It is not the right optimization for submitting an approval request. Option B still requires a custom button and manual user action. Option C is unrelated because this requirement is based on an Opportunity record change, not a platform event.

===========

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.

===========

In the Salesforce mobile app, navigation depends on the Lightning app the user is using. Salesforce documentation states that mobile navigation items depend on the active Lightning app, and when a Lightning app is enabled for desktop and phone, the desktop navigation tabs sync to the mobile navigation menu. Salesforce also notes that different menu configurations cannot simply be set directly for different user types. Therefore, the correct design is to create separate Sales and Marketing Lightning apps with different navigation items, then assign access to the appropriate profiles.

The correct answer is C. Create a master-detail relationship between the parent and child object with a roll-up summary field that filters on the status field.

A roll-up summary field is the recommended declarative solution when Salesforce needs to summarize child-record data on a parent record. Salesforce documentation states that roll-up summary fields calculate values from related records and are defined on the master side of a master-detail relationship.

In this scenario, Opportunity is the parent and Detailed_Sales__c is the child. The roll-up summary field can summarize sales metrics and use filter criteria so only child records where Status = Active are included.

Why others are incorrect:

A is incorrect because a third-party AppExchange app is unnecessary when native roll-up summary functionality meets the requirement.

B is incorrect because Apex is not recommended when a declarative feature can solve the requirement.

D is incorrect because lookup relationships do not support standard roll-up summary fields. Salesforce documentation states that lookup relationships are similar to master-detail relationships, except they do not support roll-up summary fields.

===========

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.

===========

Developer Pro satisfies both requirements. Salesforce ' s current sandbox reference states that a Developer Pro sandbox can be refreshed every one day and provides 1 GB of data storage by default, comfortably exceeding the required 250 MB. A standard Developer sandbox also has a one-day refresh interval, but its standard data-storage allocation is only 200 MB, so it does not satisfy the stated storage requirement without an additional storage upgrade. Partial Copy provides significantly more storage but can only be refreshed every five days. A Full sandbox mirrors production-scale data and storage but has a 29-day refresh interval. Therefore, Developer Pro is the only standard sandbox type among the choices that simultaneously supports at least 250 MB and daily refresh capability.

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

When deploying from sandbox to production using Change Sets, the following are critical considerations:

A. Transactions will revert if the deployment errors – Salesforce applies deployments as a single transaction; any failure rolls back the deployment to maintain org integrity.

D. Change sets do not include all components and may require manual configuration – Certain components, such as record data or some metadata, may need manual setup or additional deployment steps.

Salesforce documentation emphasizes that change sets cannot deploy everything and must be carefully reviewed before validation. (Salesforce Help)

B. Users being logged out is not required; deployments can occur while users are logged in.

C. Salesforce Connect does not automatically link environments; it is unrelated to change sets.

===========

The correct answer is B. Master-detail relationship.

Cloud Kicks needs two things: count Gift Card records on the Account and prevent Gift Cards from being moved to another Account after creation. A master-detail relationship supports both requirements.

First, master-detail enables a roll-up summary field on Account to count related Gift Card records. Salesforce documentation confirms that roll-up summaries work from detail records up to the master record.

Second, master-detail relationships prevent reparenting by default. Salesforce documentation states that records cannot be reparented in master-detail relationships by default, although admins can allow reparenting if they choose.

A is incorrect because a lookup relationship does not support standard roll-up summary fields and does not permanently lock the parent Account by default.

C is incorrect because roll-up summary is a field on the parent Account, not the relationship field type on Gift Card.

D is incorrect because a formula cannot count related child records or enforce parent locking.

Performing Data Manipulation Language operations such as Update Records inside a Loop is a classic Flow governor-limit anti-pattern. Each loop iteration can perform another database operation, rapidly consuming transaction limits when a large collection of Opportunities is processed. Salesforce ' s official Flow guidance explicitly says never to place DML operations inside loops. Instead, the app builder should iterate through the records, use Assignment elements to modify them and add them to a record collection, and perform one bulk Update Records operation after the loop. Fault paths improve error handling but do not prevent governor-limit consumption. Schedule-triggered flows can update standard objects, so D is incorrect. The scalability problem described is therefore directly caused by performing Update Records repeatedly inside the Loop element.

The correct answers are B. AppExchange and D. Lightning Components.

Salesforce Trailhead states that custom Lightning components can be created with Lightning Web Components or Aura, and existing Lightning components can also be installed from the AppExchange. Custom components configured for Lightning App Builder appear in the Lightning Components pane and can be added to Lightning pages.

Why others are incorrect:

A. Import Wizard is a data import tool, not a source of UI components.

C. Apex Code provides server-side logic, but Apex itself is not a Lightning page component resource.

===========

Record type availability determines which record types a user can select when creating records. Salesforce allows record types to be assigned through profiles, permission sets, and permission set groups. Therefore, if the support team ' s profile currently provides access to Bronze, removing Bronze from that profile prevents users from selecting that record type, assuming it is not granted through another permission set. Organization-wide defaults and sharing rules regulate access to records after they exist; they do not control which record types a user can select during creation. A permission set group containing Platinum and Diamond could grant additional access but does not inherently revoke Bronze access already provided by the profile. The direct solution described by the options is therefore to remove the Bronze record type assignment from the support team ' s profile.

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