Pass the Salesforce App Builder Platform-App-Builder Questions and answers with CertsForce

All data should be backed up before converting a text field to a picklist, as some data may be lost or truncated during the conversion. Changing a field type will remove existing field history, as the history tracking values are not converted

Updating the account search layouts search results columns displayed and updating the account search filter fields can improve an end user’s search experience by showing more relevant information and allowing more refined filtering. The view filter settings and the accounts tab columns displayed are not related to the search functionality

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

To display a weather map component on a Lightning record page conditionally:

A. Component visibility should be used. This feature in the Lightning App Builder allows components on a Lightning page to be displayed based on specific criteria, such as field values or user attributes. In this case, the app builder can set the visibility of the weather map component to only appear when a house is scheduled for a showing based on the relevant field values.

For more details on setting up conditional component visibility, review the guide on Dynamic Lightning Pages.

The Account record includes Invoice roll-up summary fields. This is correct because roll-up summary fields are only available on the master object in a master-detail relationship, and changing the field type to lookup would delete the roll-up summary fields

The app builder should use Data Loader to quickly insert a list of over 60,000 net new Accounts. Data Loader is a tool that allows users to insert, update, delete, or export large amounts of data from Salesforce using CSV files or database connections. Data Loader can handle up to 5 million records at a time and supports features such as bulk API, batch operations, mapping files, etc. Data Loader is ideal for loading large data sets into Salesforce quickly and efficiently. Lightning Object Creator is not a valid tool, as it cannot insert data into existing objects. Lightning Object Creator is a tool that allows users to create custom objects from spreadsheet data by uploading a file and mapping columns to fields. It cannot load data into existing objects or handle more than 500 records at a time. Import Wizard is not a valid tool, as it cannot handle more than 50,000 records at a time. Import Wizard is a tool that allows users to insert, update, or delete data from Salesforce using CSV files or Excel files. Import Wizard supports standard objects and some custom objects and provides features such as field mapping, duplicate detection, data validation, etc. Import Wizard is ideal for loading small data sets into Salesforce with more control and accuracy.

For a formula to evaluate to true when the stage is set to "Negotiation/Review" and the close date is less than one week away, the correct formula is:

Option B. This formula uses the ISPICKVAL function to check the text value of a picklist and compares the CloseDate to a week from today:

AND( I AND(

ISPICKVAL(StageName, "Negotiation/Review"),

CloseDate - 7 < TODAY()

)SPICKVAL(StageName, "Negotiation/Review"), CloseDate - 7 < TODAY() )

This formula checks that both conditions are met: it confirms the stage name is "Negotiation/Review" and that the CloseDate is within the next 7 days from the current date.

Option A lacks the ISPICKVAL function necessary for evaluating picklist fields. Option C uses DAY(7) which is not a valid Salesforce formula expression. Option D also uses DAY(7) incorrectly and fails to use the ISPICKVAL function.

Reference for creating formula fields in Salesforce:

Formula Field Reference: https://help.salesforce.com/articleView?id=sf.customize_functions.htm &type=5

A template for a new Lightning record page determines how the page is divided into regions. The template is responsive and will automatically adapt to the device being used to view the record page. The template can be changed after the initial save, and users do not need “View All Data” permissions for the object

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