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

The correct answer is B. The Allow reparenting checkbox, Child records can be reparented to other parent records after they are created, is unchecked.

A service plan must be associated with one Contact, and users cannot change the Contact after the service plan is created. Since field access and validation rules are not the issue, the likely cause is a master-detail relationship where Allow reparenting is not enabled.

Salesforce documentation states that in master-detail relationships on custom objects, administrators can allow child records to be reparented by selecting Allow reparenting. If that option is not selected, users cannot change the parent record after the child record is created.

A and C relate to master-detail sharing settings, not changing the parent record. D is the opposite of the problem; if Allow reparenting were checked, users could change the parent Contact.

===========

The correct answers are B. Create a criteria-based sharing rule and C. Update the organization-wide defaults.

To move from a public sharing model to a more restrictive model, the app builder must first update the Organization-Wide Defaults for Accounts. OWDs define the baseline record access for users. Then, because the Sales team must still access all Account records with the Sales record type, the app builder should create a criteria-based sharing rule using record criteria, such as Record Type. Salesforce sharing rules are used to extend access when the OWD is Private or Public Read Only.

A is incorrect because owner-based sharing rules share records based on owner, not record type.

D is incorrect because profiles control object permissions, not record-level access by record type.

The correct answer is D. Sum.

Cloud Kicks wants the total value of all won Opportunities displayed on the Account record. In a roll-up summary field, SUM totals the values in a selected numeric/currency field, such as Opportunity Amount. Salesforce documentation identifies SUM as the roll-up summary type used to total values in the selected field.

The app builder would create a roll-up summary field on Account, summarize Opportunities, use SUM on the Amount field, and apply filter criteria for won Opportunities, such as Stage equals Closed Won.

A. Count would only count the number of Opportunities.

B. Total is not the Salesforce roll-up summary type name.

C. Aggregate is not the specific roll-up summary option used here.

===========

The Automation Lightning App ' s Monitor tab is Salesforce ' s centralized interface for examining failed and paused flow interviews. Salesforce states that the Monitor tab displays failed interviews, their error information, and details needed to determine why execution failed. From the failed interview details, an administrator can open the run in debug mode and inspect the execution information without requiring the user to reproduce the issue. This directly satisfies the requirement to troubleshoot intermittent production failures from historical flow runs. Option A focuses primarily on paused interviews and is not the current comprehensive monitoring experience. Apex Replay Debugger is intended for Apex debugging rather than declarative Flow execution. Running the flow manually as another user creates a new test execution rather than analyzing the specific production failures that already occurred.