Q147. Nickname__c is a custom text field on a contact record that is Utilized to override the contact name appearing on an email template. This Field is not required and is not always filled in. Which formula should an app builder use to select the contact ‘ s preferred Name for email communications?
This scenario should be solved with standard metadata. Use C. IF (NOT (ISBLANK (Nickname__c)), Nickname__c, FirstName). The decision turns on data validation. Validation rules prevent bad data from being saved. They are appropriate when the requirement is to enforce a condition at save time rather than merely warn, display, or report on the problem later.
This is how the same requirement would be handled in a well-governed Salesforce org: identify the controlling object, relationship, field, page, automation, or environment first, and then configure the native capability for that control point. The selected answer satisfies the requirement without requiring users to perform extra interpretation or administrators to maintain an unnecessary custom workaround.
The alternatives are plausible only if the requirement is read too narrowly. A (IF (NOT (BLANKVALUE (Nickname__c)), Nickname_c, FirstName)) should be rejected because it works at the wrong scope for the object, field, page, automation, or deployment condition in the stem. B (IF(ISNULL(Nickname__c), Nickname _ C, FirstName)) would be fragile here because it could produce an inconsistent result once different users, records, or apps are tested. D (IF (TEXT (Nickname_c), Nickname_c, FirstName)) is only a partial match because That field type either stores the wrong kind of value or fails to support the required behavior as cleanly as the selected option. A complete implementation should also check page assignment, field access, record ownership, and mobile behavior where those factors apply.
—
Q151. Ursa Major Solar has received complaints about inconsistent customer service experiences and wants to provide its agents with a checklist of items that must be accomplished when servicing a case. What should an app builder use to implement this?
The platform gives a native tool for this situation. Use B. Actions & Recommendations component. The selected option is not chosen because it sounds familiar; it is chosen because it gives Salesforce the right instruction at runtime. Lightning App Builder controls page composition, component visibility, activation, assignments, and specialized surfaces such as record pages, home pages, and utility bars.
The scenario describes a business outcome, not merely an administrative preference. If the feature is configured correctly, users get the intended result without depending on memory, spreadsheets, or manual policing. That is the professional standard for Platform App Builder work: place the rule in metadata, test it under the correct permissions, and keep the design supportable.
The other choices would leave a gap in the implementation. A (Business component) misses the mark because A Lightning component changes the interface; it does not automatically solve security, relationship, or data- quality requirements. C (Activity Timeline component) handles a different concern; A Lightning component changes the interface; it does not automatically solve security, relationship, or data-quality requirements. D (Highlights Panel component) is less defensible because A Lightning component changes the interface; it does not automatically solve security, relationship, or data-quality requirements. In a real org, the builder should include negative testing as well, proving that the rule does not fire or display outside the intended conditions.
—