Salesforce Platform App Builder Salesforce Certified Platform App Builder Exam Practice Test

Page: 1 / 14
Total 291 questions
Question 1

A sales manager has noticed that reps continue to input contacts directly in

their phone instead of adding them to Salesforce.

What should an app builder recommend to ensure the data makes it into Salesforce?



Answer : C

To ensure sales reps input contacts into Salesforce rather than their personal devices:

C . Enable offline create, edit, and delete in Salesforce for Android and iOS. This feature allows sales reps to enter contact information directly into the Salesforce Mobile App even when they are offline, which syncs back to Salesforce once connectivity is restored.

Steps to enable offline capabilities:

Navigate to Setup Mobile Administration Salesforce Mobile App Offline Settings.

Configure offline settings to allow for creating, editing, and deleting records.

Ensure that the Contact object is available for offline access.

This functionality encourages reps to use Salesforce directly by mitigating connectivity constraints.

For implementation details, refer to Salesforce Mobile App Offline.


Question 2

Universal Containers (UC) requires that all users specify a contract is sent on each Opportunity prior to marking it as "Closed Won". UC wants to be able to report on how many Opportunities have sent Contracts compared to how many have a missing contract when the Opportunities closed.

Which field type should an app builder configure to fulfill this requirement?



Answer : D

For tracking whether contracts have been sent for Opportunities:

D . Checkbox. This field type allows users to clearly indicate (Yes/No) whether a contract has been sent. This binary nature of checkboxes makes it simple to filter and report on Opportunities based on whether a contract was sent.

Steps to configure this field:

Navigate to Setup Object Manager Opportunity.

Click Fields & Relationships New Checkbox.

Define the field with a label (e.g., Contract Sent).

Set the default value to false (unchecked).

Add the field to the relevant page layouts.

This setup facilitates accurate reporting and ensures that opportunities cannot be marked as 'Closed Won' without indicating whether a contract was sent.

For guidance on creating fields, see Salesforce's documentation on Custom Field Creation.


Question 3

Where can an app builder edit an existing app to add components to the utility bar?



Answer : C

To add components to the utility bar of an existing app:

C . App Manager. This is where Salesforce apps are configured, including the utility bar which can house components like a chat tool, recent items list, or custom Lightning components.

Steps to edit an app's utility bar:

Navigate to Setup App Manager.

Locate the desired app and click on the dropdown next to it select Edit.

In the App Builder, navigate to the Utility Items tab.

Click 'Add' to include new components to the utility bar.

Configure the properties of the utility item as needed.

Save the app configuration.

For step-by-step instructions on modifying apps, see Salesforce's guide on Managing Apps in Lightning Experience.


Question 4

Which two features can be used to allow users to access Flows?

Choose 2 answers



Answer : A, C

To allow users access to Flows, Salesforce offers multiple integration points:

A . Quick Action: Flows can be initiated from record pages, the app utility bar, or global actions using Quick Actions. This allows users to execute flows relevant to specific records or global processes.

C . Flow Launcher: A component available in Lightning App Builder that enables users to start flows directly from a Lightning page.

Steps to set up these features:

For Quick Actions, navigate to Setup Object Manager select object Buttons, Links, and Actions New Action Action Type (Flow).

For Flow Launcher, navigate to Lightning App Builder select the page drag the Flow component to the desired section of the page configure it to launch the specific flow.

For more information on integrating Flows, check the Salesforce documentation on Flow Distribution.


Question 5

Ursa Major Solar (UMS) uses Cases to track customer complaints, an Issue__c object to represent known problems with its solar panels, and a

Case_Issue__c junction object to relate known problems to customer complaints.

Periodically, UMS conducts audits which require the auditing users to view Case _Issue__c records.

Which access levels must be configured to allow UMS users to access Case _Issue_c records?



Answer : D

To ensure auditing users can access records in the Case_Issue__c junction object, the correct data permissions on related records must be established:

D . Read-Only access on Case and Issue__c. Users need read-only access to both Case and Issue__c objects to view associated Case_Issue__c junction object records properly. This is because access to junction object records in Salesforce is determined by the user's access levels to the parent records in a relationship.

Steps to configure access:

Navigate to Setup Profiles or Permission Sets.

Select the profile or permission set of the auditing users.

Under Object Settings, adjust the permissions for Case and Issue__c to at least 'Read-Only'.

Ensure that users have visibility to the Case_Issue__c object itself.

This configuration allows users to view the details of cases and issues as they audit the junction object records.


Question 6

A new field is being created on a custom object. However, the app builder does not want the field to show up on pre-existing custom report

types.

What should the app builder do on the custom field setup to fulfill this requirement?



Answer : D

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


Question 7

After utilizing the Lightning Object Creator to create a new object, its fields, and to insert all of the data, an app builder now needs to set up the

Lightning Record Page.

Which component should the app builder have on their Lightning Record Page to see all of the fields from the page layout?



Answer : C

For an app builder who needs to ensure all fields from the page layout are visible on a Lightning Record Page after using the Lightning Object Creator, the correct component to use is:

Record Detail (C). The Record Detail component automatically displays all fields that are included on the assigned page layout for the object. It is designed to reflect the layout configuration and is the simplest way to ensure all fields are presented as configured in the layout editor.

Highlights Panel (A) is used primarily to display key fields at the top of the record page, providing a summary view rather than full field visibility. Recommendations (B) is used for displaying prompts or suggestions and does not display record fields. Path (D) is useful for displaying stages in a process (like sales stages or service processes) and does not show field data directly.

Reference for setting up Lightning Record Pages and using components effectively:

Lightning Record Pages: https://help.salesforce.com/articleView?id=sf.lightning_page_components.htm&type=5


Page:    1 / 14   
Total 291 questions