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

 Groups is available in the Chatter section of the navigation menu, not in the selected list for the navigation menu. According to the Salesforce documentation, “Groups appear in Chatter, not in Navigation Menu.” Groups is not available in the recent section of the navigation menu, nor is it included in the Smart Search items but unavailable on the navigation menu. Groups is unavailable in the selected list for the navigation menu.

The selected objects in the sandbox template. This is correct because a partial sandbox only copies a subset of data from production, and the data to be copied is determined by the sandbox template. If the Shipping object was not selected in the template, then its data would not be copied to the sandbox

 Big objects and external objects can be used to archive historical data and reduce data storage in Salesforce, while still allowing users to access the archived data using reports, queries, and lookups. Big objects store data within Salesforce, while external objects store data outside Salesforce and integrate it with Salesforce using an external data source

The goal is to automatically delete rejected quotes, which requires an automation tool capable of performing record deletion actions.

Only Flow can perform this function declaratively.

Why D (Flow) is correct:Exact Extract:“Use Flow Builder to automate complex business processes by collecting data and performing actions such as creating, updating, or deleting records.” — Salesforce Help | Flow Builder OverviewA Record-Triggered Flow can be configured to delete a quote automatically when its status is updated to “Rejected.”

Why D (Flow) is correct:Exact Extract:“Use Flow Builder to automate complex business processes by collecting data and performing actions such as creating, updating, or deleting records.” — Salesforce Help | Flow Builder OverviewA Record-Triggered Flow can be configured to delete a quote automatically when its status is updated to “Rejected.”

Why not A (Validation Rule):Validation rules prevent record saving; they don’t perform deletions.

Why not B (Einstein Next Best Action):NBA recommends actions but does not execute deletions automatically.

Why not C (Approval Process):Approval processes manage approvals but don’t delete records after rejection.

Lightning Object Creator is a tool that allows app builders to create an object with fields and import data from a spreadsheet simultaneously. Import Wizard and Data Loader are tools for importing data into existing objects, not creating new objects. Schema Builder is a tool for creating and modifying objects and fields, but not importing data.

 The app builder should use the Path component to meet the requirement of tracking different fields at each stage of the Opportunity sales process. The Path component is a Lightning component that displays the key fields and guidance for each stage of a standard or custom picklist field, such as the Opportunity Stage field. The app builder can configure the Path component to show the fields that need to be filled out and provide recommendations and sales strategies for each stage3. Option A, B, and C are not configuration steps that can meet this requirement.

Upon adding a lookup field to Account from a custom object, Box:

D. Accounts with Boxes. Salesforce automatically creates a new report type that reflects the relationship from the perspective of the parent object, in this case, Accounts, showing related Box records.

This new report type enables users to create reports that list Accounts along with their associated Boxes, if any.

For further understanding of report types and relationships, Salesforce's guide on Report Types provides comprehensive information on how these are structured following modifications to object relationships.

The best way to implement this request is to create a Lightning Web Component that can fetch the real-time stock price from an external API and display it on the Account record page. Installing a solution from the AppExchange may not be feasible as it may not match the exact requirements or may have additional costs. Building a Flow that uses API calls may not be efficient as it may consume API limits and may not be able to update the stock price in real-time. Using a scheduled Apex job may not be suitable as it may not be able to run frequently enough to reflect the real-time stock price

When creating a new field, if an app builder does not want the field to be automatically added to pre-existing custom report types, the step to take is:

Deselect 'Add Field to Custom Report Types' (D). This option is available when creating or editing a custom field and ensures that the field is not automatically included in report types where 'Automatically add new custom fields to report type layouts' is enabled.

Removing the field from page layouts (A) affects the visibility on record pages but not reports. Adjusting visibility (B) or setting read-only access (C) for report profiles affects user permissions to see the field in reports, but does not remove the field from report types if it was previously added.

Reference for managing fields in custom report types:

Custom Report Types and Fields: https://help.salesforce.com/articleView?id=reports_report_type_layouts.htm &type=5

When activating a Lightning page from the Lightning App Builder, three options are available:

Assign the page to a combination of apps and profiles. This option allows users to specify which apps and profiles will see the custom Lightning page instead of the default page.

Make the page the org default. This option makes the custom Lightning page the default for all users in the org regardless of their app or profile.

Make the page the default homepage for specific apps. This option allows users to set different homepages for different apps in Lightning Experience. [Source]

The common items that can be moved using a change set are custom object, Apex class, and custom field. These are metadata components that can be deployed from one environment to another using change sets. Web-to-lead and standard fields are not metadata components that can be moved using change sets.

To connect Testimonial__c records with both the submitter’s Contact record and Account record, an app builder should create a master-detail relationship from Testimonial__c to Account and a lookup relationship from Testimonial__c to Contact. A master-detail relationship creates a parent-child relationship between two objects and allows for roll-up summary fields, sharing settings, and cascading actions. A lookup relationship creates a loose association between two objects and allows users to relate records from one object to another. Source

 The recommended solution to grant the customer service agent access to the field is creating a permission set that allows read-only access to the field via Field Level Security and assigning it to the agent. A permission set is a collection of settings and permissions that give users access to various tools and functions. Field Level Security (FLS) is a setting that controls the access level of fields for different profiles or permission sets. The app builder can create a permission set that grants read-only access to the custom field on the account object via FLS and assign it to the agent. Option B is incorrect because creating a new profile to allow for read-only access to the field via FLS and assigning it to the agent is not recommended, as profiles are used to define the baseline permissions and settings for a group of users, and creating multiple profiles for individual users can be hard to maintain. Option C is incorrect because updating the Customer Service Profile already assigned to the agent to allow for read-only access to the field via FLS is not recommended, as this will affect all users who have the same profile, which may violate the security policy. Option D is incorrect because updating the custom field’s FLS in setup to allow the agent read-only access to the field is not possible, as FLS can only be set at the profile or permission set level, not at the user level.