Salesforce Platform-App-Builder Questions Answers

The correct answer is C. Custom object with Master-detail field to Opportunity.

AW Computing needs many help requests related to one Opportunity, so the help request should be a custom child object under Opportunity. Because the Opportunity page must show the most recent request date, the app builder needs a Roll-Up Summary field on Opportunity using MAX on the request date field.

Salesforce roll-up summary fields work on the master side of a master-detail relationship, and MAX can be used for date/date-time fields.

A is backward because the master-detail field belongs on the child object, not Opportunity.

B and D use lookup relationships, which do not support standard roll-up summary fields.

===========

An input value from something outside the flow must be received through a Flow variable configured as Available for Input . Salesforce defines an input variable as a variable marked Available for Input that receives values from outside the flow. The app builder therefore creates a Variable resource, selects the required data type, and enables Available for Input under Availability Outside the Flow. The invoking Lightning component can then pass a value into that resource when the flow starts. $Record is a Flow global variable used in specific record contexts and does not replace a configurable external input parameter. Constants cannot receive changing runtime values because their values are fixed. Public component properties describe the LWC side but do not by themselves create a receiving Flow variable. Salesforce

================

The correct answers are B. Assign the page to a combination of apps and profiles, C. Make the page the default homepage for specific apps, and E. Make the page the org default.

When activating Lightning pages, Salesforce supports assigning a page as an org default, assigning it to specific Lightning apps, and assigning it to combinations such as app and profile. Salesforce Trailhead also confirms that Lightning record page activation supports org default, app default, and app/record type/profile assignments.

A is incorrect because Lightning page activation uses profiles, not permission sets, for this assignment model.

D is incorrect because Lightning pages are not activated by role as a standard activation option.

===========

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

Here, “custom-based” is most likely referring to a criteria-based sharing rule. UC wants to move from public sharing to a more restrictive model, so the app builder must first update the Organization-Wide Defaults for Accounts. Salesforce OWDs define the default access users have to records they do not own.

Then, to continue giving the Sales team access to all Account records with the Sales record type, the app builder should create a criteria-based sharing rule based on record criteria, such as Record Type. Salesforce criteria-based sharing rules share records based on field values.

C is incorrect because profiles control object permissions, not record-level sharing by record type.

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

===========