The correct answer is C. Formula Field.

The Service Manager wants a visual color indicator based on the age of an open Case: green for new, yellow for one day old, and red for three days old. This can be implemented with a formula field using conditional logic and the Salesforce IMAGE() function to display different colored indicators based on Case age. Salesforce documentation confirms that the IMAGE function is available in formula fields and can display an image based on field values.

A formula field can evaluate the case age using fields such as CreatedDate , TODAY() , and IsClosed , then return the correct colored image.

A. Custom Button is incorrect because this is not a user action.

B. Quick Action is incorrect because the requirement is display-based, not action-based.

D. Lightning Web Component could do this with code, but a formula field is the simplest declarative Platform App Builder solution.

===========

The correct answer is C. Checkbox.

Universal Containers needs to track whether a contract was sent or not sent before an Opportunity is marked Closed Won. This is a simple Yes/No reporting requirement, so a Checkbox field is the best field type. Salesforce checkbox fields are represented as True/False values and can be used in reports and list view filters.

Picklist is unnecessary for a two-state value. Text and Text Area would create inconsistent reporting because users could type different values.

The correct answers are B. Use a roll-up summary field on the Park record and C. Use a master-detail relationship between the Park and Trail objects.

Northern Trail Outfitters wants the total number of Trails displayed on the Park record without code. In Salesforce, a standard roll-up summary field can count related child records, but it requires a master-detail relationship between the parent and child objects. Salesforce documentation confirms that roll-up summary fields calculate values from related records, and this is the correct declarative feature for this requirement.

A is incorrect because a formula field cannot count child records. D is incorrect because standard roll-up summary fields do not work on ordinary lookup relationships.

===========

The correct answer is C. A delegated approver is the recommended Salesforce feature when the assigned approver is unavailable, such as during vacation. Salesforce documentation confirms that users can identify a delegate in approval settings, and delegated approvers can approve or reject approval requests.

This ensures the closed-won Opportunity can still be reviewed before the leaderboard is updated, even though the owner’s manager is away.

Why others are incorrect:

A is not the best recommended setup because relying on an assistant to reassign requests is manual and reactive.

B is incorrect because forwarding approval requests is not the standard solution for planned approver absence.

D is incorrect because assignment rules do not assign delegated approvers for approval processes.

===========

In the Salesforce mobile app, navigation depends on the Lightning app the user is using. Salesforce documentation states that mobile navigation items depend on the active Lightning app, and when a Lightning app is enabled for desktop and phone, the desktop navigation tabs sync to the mobile navigation menu. Salesforce also notes that different menu configurations cannot simply be set directly for different user types. Therefore, the correct design is to create separate Sales and Marketing Lightning apps with different navigation items, then assign access to the appropriate profiles.

AW Computing wants to grant access to all users in the Service Manager role for Opportunities of type Service Agreement in a private sharing model.

Criteria-based sharing rules allow sharing records automatically based on field values (e.g., Type = Service Agreement) to roles, public groups, or users.

Salesforce documentation confirms that when the org-wide default is private, sharing rules are the declarative way to grant access to specific users based on criteria. (Salesforce Help)

Owner-based sharing rules share based on the record owner, not a field criterion.

Apex sharing rules are needed only if declarative sharing is insufficient.

Manual sharing requires user action and is not scalable.

===========

The correct answer is A. Roll-up summary field.

Cloud Kicks wants to count how many Subscription records are related to each Shoe record. Because a master-detail relationship already exists between Subscription and Shoe__c , the app builder should create a Roll-Up Summary field on the master object.

Salesforce documentation confirms that roll-up summary fields can count the number of detail records related to a master record. Trailhead also explains that roll-up summaries display values on the master record based on directly related detail records in a master-detail relationship.

B. Lookup field and C. Master-detail field define relationships, but the relationship already exists. D. Sum field is not a Salesforce field type.

===========