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

Create a Chatter stream. This is correct because a Chatter stream allows users to follow multiple records and people in one feed, and filter the feed by selecting a stream.

The two tools that an app builder could combine to display the number of open cases on the account page are Flow and Process Builder. Flow is a tool that allows the app builder to create a declarative automation that can query, manipulate, and display data from multiple objects. Process Builder is a tool that allows the app builder to create a trigger-based automation that can invoke a Flow when a record is created or updated. By using these two tools, the app builder can create a solution that can query the number of open cases for the account and parent account and display them on the account page using a screen element. Workflow is not a suitable tool, as it cannot query or display data from multiple objects. It can only perform actions such as field updates, email alerts, tasks, or outbound messages. Approval Process is not a suitable tool, as it is used to automate the approval of records based on certain criteria and predefined steps. It cannot query or display data from multiple objects.

For managers to respond to approval requests for opportunities above $50,000 in the Salesforce mobile app:

B. In-App Notification: Managers receive notifications within the Salesforce mobile app when there is an approval request, allowing them to approve or reject directly from the notification.

C. Record Detail: Managers can access the approval request directly from the Opportunity's detail page in the mobile app, where they can review and respond to the request.

Steps to configure approval process notifications:

Navigate to Setup → Approval Processes → select the relevant approval process.

Ensure the process is active and configured to send notifications to approvers.

Managers need to have the Salesforce mobile app configured to receive notifications.

For best practices on managing approvals in Salesforce, see Approvals in Salesforce.

 Sales rep B has implicit access to the Account because of the manual sharing of the Opportunity. Implicit sharing grants access to parent records when a user has access to a child record. Sales rep B was not added to the Account team, sharing set is not applicable for private sharing model, and Account was not manually shared.

 A custom button, a validation rule, and record types can be used to meet the requirement of hiding the convert button on leads until the lead status picklist is set to qualified. The custom button can replace the standard convert button and invoke a validation rule that checks the lead status. The record types can be used to assign different page layouts with different buttons for different lead statuses

The app builder should create a new roll-up summary field called First Order Date, using Type MIN on the Opportunity Close Date with a filter where IsWon = TRUE. A roll-up summary field is a type of field that calculates values from related records and displays them on the parent record. In this case, the app builder can create a roll-up summary field on the Account object that calculates the minimum (earliest) value of the Opportunity Close Date field from the related opportunities where IsWon = TRUE. This will show when customers made their first purchase. Option B, C, and D are not correct ways to use a roll-up summary field to meet the requirement.

Two reasons that can prevent an app builder from adding a custom component to the Lightning home page are if My Domain is not deployed, or if the component is tagged for record pages instead of home pages. My Domain must be deployed to add custom components to the page with the App Builder, as it enables Lightning components and other features. The component must be tagged for home pages in its configuration file, otherwise it will not show up in the App Builder for home pages

If an employee attempts to edit the description field after submitting an opportunity for approval, they will be presented with a ‘Record Lock’ notification. This means that the record is locked for editing while it is in the approval process and only users with the “Modify All” permission or users above them in the role hierarchy can edit it. [Source]

To make a custom component available for the utility bar in Salesforce, the component needs to be explicitly tagged for use in the utility bar. Salesforce components require specific configurations to be available in different parts of the application, such as the utility bar, record pages, or app pages.

Option C: For use on the utility bar: When a custom Lightning component is developed, it must include a specific target tag in its .js-meta.xml configuration file that marks it as usable in the utility bar. This is done by setting the target to "lightning__UtilityBar". Without this tag, the component will not appear as an option to add to the utility bar in the App Manager.

Example of how the component is tagged in the meta.xml file:

xml

Copy code

lightning__UtilityBar

Utility Bar Components Documentation

Option A: For use on record pages: This tag makes the component available only on record pages, but not the utility bar. The component would have a target for lightning__RecordPage in this case.

Option B: For use in Lightning App Builder: This option would allow the component to be used in the Lightning App Builder, but it wouldn't make the component available for the utility bar. App Builder placement is typically for page layouts.

Option D: For use in App Manager: This is incorrect, as App Manager is used for managing apps and not for tagging components for availability.

In summary, to make the component available for the utility bar, it needs to be specifically tagged for that purpose using the lightning__UtilityBar target in the component's metadata file.

Moving the reports from the Unfiled Public Reports folder and adding them to a new change set is what the app builder should do to deploy the reports to production. According to the Salesforce documentation, “Reports in the Unfiled Public Reports folder aren’t available for deployment.” Moving the reports to the Untried Public Reports folder, recreating the reports in production, and adding the reports to an unmanaged package are not necessary or recommended actions.

Update the organization-wide defaults and create a criteria based sharing rule are two actions that an app builder should complete to implement the change of moving to a more restrictive sharing model while allowing the Sales team to access all account records with the sales record type. Updating the organization-wide defaults can set the baseline level of access for accounts, and creating a criteria based sharing rule can grant additional access based on record type. Updating the Sales profile and creating an owner-based sharing rule are not necessary or sufficient actions for this change.

Record-triggered flow is the automation tool that the app builder should use to best address all these requests of sending an email to the finance manager and creating a task for the sales manager when a new client is won. According to the Salesforce documentation, “Record-triggered flows automate processes for you. They start when a record is created or updated, or when a platform event occurs.” A record-triggered flow can perform actions such as sending an email alert or creating a record based on criteria or conditions. Screen flow, Apex, and Approval process are not automation tools that can handle all these requests.

 A summary report on the opportunity object should be created to add to the account page layout. A summary report groups rows of data by common values and allows users to create charts based on aggregate values. A summary report on the opportunity object can group opportunities by stage and display a chart of all related opportunities on the account detail page.

The app builder should validate the inbound change set to ensure a smooth deployment to production. Validating an inbound change set allows the app builder to test whether the change set can be deployed without errors in the target org. Validating an inbound change set does not affect any data or metadata in the target org.

The app builder should verify that there is an Apex test that provides test coverage for the Flow. An Apex test is a unit test that verifies the functionality and quality of Apex code. Apex tests are required to deploy any change that contains Apex code or references Apex code, such as an auto launched flow3. The app builder should ensure that there is an Apex test that covers at least 75% of the Flow logic before deploying it to production in an active state4. Option B, C, and D are not things that the app builder should take into consideration when planning the deployment.

The Twitter component is a standard Lightning component that can be added to mobile view Lightning pages using the Lightning App Builder. It displays a contact’s Twitter profile and recent tweets

An AppExchange solution is a pre-built application or component that can be installed from the Salesforce AppExchange, which is an online marketplace for Salesforce products. AppExchange solutions can help you meet your business needs quickly and efficiently, without requiring much development effort or expertise. You can browse and search for AppExchange solutions by category, industry, rating, price, and more.

 The best way to configure Account sharing so that community users only see their own Account is to set the account external OWD to private. This will restrict the access to Account records for external users based on the sharing rules and criteria. Creating an account record type, defining an owner-based sharing rule, or defining a permission set will not prevent community users from seeing other accounts.

When Cloud Kicks needs to calculate summaries from child objects of a standard object declaratively, a few key considerations about master-detail relationships come into play. Master-detail relationships are critical in Salesforce when working with roll-up summary fields, which allow you to calculate values from child records.

Option B: An object can have up to two master-detail relationships.

Salesforce allows an object to have two master-detail relationships. This is important because if you want to aggregate child record data using roll-up summary fields, you need to have a master-detail relationship in place. Each master-detail relationship links a child object to a parent, and you can create roll-up summary fields on the parent object to summarize the child record data.