Salesforce Updated Platform-App-Builder Exam Questions and Answers by dollie

The correct answer is B.

Universal Containers needs the 18-digit Salesforce record ID for Opportunity records when exporting to Excel. Salesforce’s CASESAFEID() formula function converts a 15-character Salesforce ID into the 18-character, case-insensitive ID format that works better with external tools such as Excel. Salesforce documentation specifically describes CASESAFEID as the function used to convert IDs to 18-character IDs for Excel compatibility.

Correct formula:

CASESAFEID(Id)

A. VALUE(14) is unrelated. C. TEXT(Id) does not convert the ID to the 18-character case-safe format. D. ISNUMBER(Id) only checks whether a value is numeric, which is not useful for Salesforce record IDs.

===========

The correct answers are C. The report is in the manager’s Private reports folder and D. The report does not have a chart.

The Report Chart component is used to display a chart from a report on a Lightning page. If the report has no chart, it cannot be used as a Report Chart component source. Salesforce documentation describes the Report Chart component as a way to include a chart from a report in a Lightning page.

The app builder also must have access to the report through report folder sharing. Reports saved in a user’s private report folder are not visible to other users unless moved/shared appropriately. Salesforce explains that reports are saved by default into private reports or dashboards folders unless a public/custom folder is selected.

A is incorrect because a report having no returned data does not stop the report from being selectable. B is incorrect because the app builder does not need to be the report creator; they need access to the report folder and the report must contain a chart.

===========

A utility bar gives users quick access to commonly used productivity tools and components from within a Lightning app or console app. Salesforce describes the utility bar as a fixed footer that provides fast access to tools such as Notes, History, softphone, flows, and custom utilities. Utilities open in docked panels, allowing users to keep working without leaving the current page. This exactly matches the requirement: components accessible from anywhere in the app without leaving the page.

This question is testing the classic Salesforce Process Builder automation best practice , not a generic Flow-only rule. Salesforce’s official process design guidance states that an org should have only one record-change process per object . The reason is simple: every time a record is created or updated, Salesforce evaluates the record-change processes for that object. If an object has multiple record-change processes, the automation becomes harder to predict, harder to troubleshoot, and more likely to hit governor limits. Salesforce specifically explains that consolidating automation into one record-change process gives admins a single view of all criteria and actions for that object, reduces duplicated automation overhead, and allows the app builder to control the order of criteria evaluation.

A is not the best exam answer here. In modern Flow architecture, “one Flow per object” is often discussed as a design pattern, but it is not the exact best-practice wording being tested by this Platform App Builder-style question. Salesforce Flow design is more nuanced today because record-triggered flows can vary by trigger timing and event. B is wrong because validation rules should be separated by validation requirement, not forced into one rule per object. C is wrong because invocable processes are reusable modular processes, not the main record-change automation container.