Salesforce CRT-403 Prepare for your Platform App Builder Certification Exam Practice Test

Answer : D

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.

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.

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.

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.

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.

Answer : B, D

For reporting snapshots, the source report must be capable of grouping data, which is necessary for summarizing information at specific intervals. The acceptable formats for a source report in reporting snapshots are:

Summary format (B). This format groups rows of data by one or more criteria and can perform calculations such as sum, average, etc., on another column at each group level.

Matrix format (D). Similar to the summary format but arranges data in a grid format, allowing summarization by both rows and columns.

Tabular (A) and joined (C) formats are not suitable for reporting snapshots. Tabular reports do not include grouped or summarized data, and joined reports involve combining multiple report types, which are not compatible with how reporting snapshots need to structure data.

Reference for more information on reporting snapshots and report formats:

Reporting Snapshots: https://help.salesforce.com/articleView?id=reports_snapshots.htm&type=5

Report Formats: https://help.salesforce.com/articleView?id=reports_understanding_formats.htm&type=5

Answer : B, C

To track the total number of trails associated with a park without writing code, the correct actions to take are:

Use a roll-up summary field on the Park record to show the total number of Trails (B). Roll-up summary fields calculate and display a value in a master record based on the values of fields in a detail record. They are used to count, sum, average, or get the minimum/maximum of values in related detail records.

Use a master-detail relationship between the Park and Trail objects (C). Master-detail relationships are necessary for roll-up summary fields as they allow the master object to control certain behaviors of the detail object and summarize data from those detail records.

A formula field (A) cannot dynamically count related records unless those records are linked via a master-detail relationship, and it cannot alone handle counts across related records without such a relationship. A lookup relationship (D) does not support roll-up summaries unless combined with additional tools like triggers or third-party apps, which involve coding or extra configuration outside standard object setup.

For more details, refer to the Salesforce Help documentation on master-detail relationships and roll-up summary fields:

Master-Detail Relationship: https://help.salesforce.com/articleView?id=relationships_considerations.htm&type=5

Roll-Up Summary Fields: https://help.salesforce.com/articleView?id=fields_about_roll_up_summary_fields.htm&type=5