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

The correct answer is D. Component visibility filter.

In Lightning App Builder, component visibility rules can control whether a component appears based on context, including the device/form factor. Salesforce Trailhead specifically describes creating a visibility rule so a component appears only when the page is viewed on a phone, which matches restricting a Lightning component to mobile users.

A is incorrect because form factor settings are generally used for page/device availability or preview behavior, not the best feature for hiding or showing one specific component on a single Lightning record page.

B and C are incorrect because the Highlights Panel and Related List Quick Links are page components, not conditional visibility tools.

===========

The correct answers are A and B .

The requirement is to display a visual flag image based on Case Priority. Salesforce’s own sample image formula for Case Priority uses the IMAGE() function with CASE() to display green, yellow, or red flag images.

Both formulas are valid because:

A uses IMAGE() with nested IF() and ISPICKVAL() checks.

B uses IMAGE() with CASE() to return the correct image URL.

C and D are incorrect because they return only the image URL text, not the actual image. The formula must use IMAGE() to display a visual flag.

===========

The correct answer is D. Universal Containers wants the real-time value of the Account’s Support Level picklist to appear on related Case records. The best declarative solution is a cross-object formula field on Case that references the related Account field.

Because Support Level is a picklist, the formula should use the TEXT() function to return the picklist value as text. Salesforce documentation states that cross-object formulas can reference fields from related objects, and Salesforce’s TEXT function supports picklist values in formulas.

Example formula concept:

TEXT(Account.Support_Level__c)

Why others are incorrect:

A is incorrect because the formula must be on Case, not Account.

B is incorrect because Case already relates to Account; a new lookup alone does not display the value.

C is incorrect because roll-up summary fields summarize child records; they do not copy/display a parent picklist value on child Case records.

===========

The correct answers are A. There are already two master-detail relationships on the Invoice Line Item and C. Invoice Line Item records exist without having the Invoice lookup field populated.

Salesforce allows a lookup relationship to be converted to a master-detail relationship only when the lookup field has a value on all existing records. Therefore, if any Invoice_Line_Item__c records do not have the Invoice lookup populated, Salesforce prevents the conversion.

Salesforce also limits each custom object to up to two master-detail relationships. If Invoice Line Item already has two master-detail relationships, it cannot have another master-detail relationship added or converted.

B is incorrect because custom objects can be on the detail side of master-detail relationships. D is incorrect because a roll-up summary field on Invoice is not the reason this lookup-to-master-detail conversion would be blocked.

===========