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

The correct solution is to add a Rich Text component to the Case Lightning record page and then use component visibility so it only appears when the related Account’s support level is Platinum.

Salesforce Lightning App Builder supports visibility rules that show or hide components based on field criteria. Salesforce documentation confirms that visibility filters on record pages rely on field data associated with the page’s object, and related lookup fields can be used in visibility-rule considerations.

This is the best declarative solution because the requirement is only to display a text notification. A custom Lightning Web Component or cloned Lightning page is unnecessary.

Why others are incorrect:

A is incorrect because assigning a Case page to “platinum accounts” is not the correct assignment model.

C and D are incorrect because custom Lightning Web Components add unnecessary development effort for a simple text notification.

===========

The correct design is to create a master-detail relationship from Testimonial__c to Account and a lookup relationship from Testimonial__c to Contact.

The Account relationship must be master-detail because Salesforce deletes related detail records when the master record is deleted. That matches the requirement that if the Account is deleted, the related Testimonial__c records are also deleted. The Contact relationship must be lookup because the Testimonial__c record must remain when the Contact is deleted. Salesforce lookup relationships can keep the child record and clear the lookup value when the referenced record is deleted.

Why the other options are wrong:

A reverses the required behavior. B would delete the testimonial if either master side caused deletion behavior, which does not fit the Contact requirement. D uses lookup for Account, so it does not guarantee Account deletion will also delete Testimonial__c record

The correct answer is A. A hyperlink to the parent Account of the parent Opportunity.

A formula field can use cross-object references to parent records, and Salesforce states that cross-object formulas can reference fields from objects up to 10 relationships away. Since Opportunity Product relates to Opportunity, and Opportunity relates to Account, a formula on Opportunity Product can reference the parent Opportunity’s Account.

Salesforce also supports the HYPERLINK() formula function, which creates a clickable link from specified link text to a specified URL. So a formula field can be configured to create a hyperlink to the Account record related to the parent Opportunity.

B is incorrect because formula field data types do not include Rich Text Area as a formula return type.

C is incorrect because Salesforce restricts formulas from using long text area, encrypted, or Description fields.

D is not the best verified answer because large cross-object concatenations can run into formula relationship, size, or complexity limits, while the clearly supported Platform App Builder use case here is the cross-object HYPERLINK formula.

===========

The correct answer is A. Lookup field.

Cloud Kicks wants to assign a Customer Service Manager user to an Account in addition to the standard Account Owner. The best field type is a Lookup field to the User object. A lookup field stores a relationship to another record and supports reporting, filtering, and record-level navigation. Salesforce describes lookup relationships as a way to relate two records while keeping the records otherwise independent.

A Text field would not create a real user relationship and could cause inconsistent names. A Picklist or Multi-select picklist would require manual maintenance of user names and would not behave like an assigned user reference.

===========