Path is designed to give users a visual representation of a record ' s progression through a process based on a picklist field such as Status or Stage. Salesforce describes Path as an at-a-glance indicator that shows where a record currently sits in a process and where it is progressing next. For delivery tracking, the app builder can configure delivery statuses as Path stages and place the Path component on the Lightning record page. Related Lists display associated records rather than process progression. Details displays record fields, while Related Record exposes information from another related record. Because the stated requirement is specifically for a visual representation of delivery status, Path is the native declarative component that directly satisfies the requirement.

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

The correct answer is C. Approval process.

The key requirement is that the manager’s sign-off on free parts must be processed. Salesforce approval processes are designed to automate record approval, define approval steps, assign approvers, and perform actions when records are approved or rejected. Salesforce Trailhead gives a similar discount-management example where discount percentage is tracked and manager approval is requested through an approval process.

Why others are incorrect:

A. High Velocity Sales is for sales engagement/cadences, not approval sign-off.

B. Quotes may help with pricing, but it does not by itself process manager approval.

D. Checkbox can store a value but cannot route approval.

===========

A validation rule is required because Cloud Kicks needs to prevent , rather than merely discourage, users from skipping required Opportunity stages. A validation formula can evaluate the new StageName together with the prior stage, required fields, or other process criteria and block the save when the transition violates the sales process. Salesforce validation rules are designed to prevent records from being saved when specified business conditions are violated. Path and Guidance for Success improve usability and tell representatives what they should do, but neither inherently stops a user from jumping directly to Contract Signed. An approval process would add unnecessary managerial routing and does not directly represent the requirement to enforce valid stage progression. Therefore, a validation rule is the most efficient declarative mechanism for enforcing the required pipeline sequence.

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

The correct answer is A. Make the Opportunity Type a required field on the initial Opportunity page layout and use automation to update the record type based on the Opportunity Type.

The requirement has two phases: first, show users only the fields needed to create the Opportunity; after save, show the full record page based on the Opportunity type. This can be handled by using a required Opportunity Type field first, then automation can update the Opportunity record type. Salesforce page layouts can be assigned by profile and record type, which allows different Opportunity types to show different layouts after the record type is set.

B is incomplete because it only mentions page layouts based on profile, not dynamically changing the layout based on Opportunity Type after creation. C is incorrect because sharing rules control record access, not field display. D relies on users manually expanding sections and does not meet the streamlined requirement.

The correct answer is B. Field-level security.

Only users with the Outer Planets profile need to see the Jupiter field. Salesforce field-level security, also called field permissions, controls whether users can view or edit individual fields on an object. This is the proper way to restrict a field by profile or permission set.

Sharing rules control record-level access, not field visibility. Filtered views affect list views, not field security. Classic encryption protects sensitive data but is not the correct feature for profile-based field visibility.

===========

The correct answers are A. The NOW() function in the formula field and D. A cross-object field referenced in the formula field.

Salesforce allows roll-up summary fields to summarize formula fields only when the formula does not contain unsupported dynamic or cross-object references. Salesforce documentation states that roll-up summaries can calculate formula fields only if the formula does not contain cross-object field references or functions that derive values dynamically, such as NOW() or TODAY().

A is correct because NOW() changes dynamically based on current date/time.

D is correct because cross-object field references prevent the formula from being used in the roll-up summary.

C is incorrect because CASE() itself is allowed.

B is incorrect because the issue is not simply a field update; the restriction is specifically cross-object references or dynamic formula functions inside the formula being summarized.

===========

Queues are represented through Salesforce Group records, and their stable programmatic identifier is the DeveloperName , or API name. A flow that determines a regional queue dynamically can first calculate the appropriate queue API name in a text or formula resource and then use Get Records against the Group object, filtering DeveloperName to that value and Type to Queue. Salesforce ' s current Flow guidance provides this exact architecture for dynamically resolving queues rather than hard-coding IDs. Hard-coded user or queue IDs are brittle across environments and conflict with the dynamic-routing requirement. An asynchronous path changes execution timing but does not resolve the assignee. A custom Task text field likewise does not establish an actual queue assignment. Therefore, the formula-resource plus Get Records pattern is the correct declarative solution.

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

The correct answer is A. The requirement is to combine four custom text fields into one formula field and display the result on two lines.

The formula works as follows:

Street__c displays the street on the first line.

BR() inserts a line break. Salesforce documents the BR formula function as inserting a line break in a text string.

City__c & " , " & Planet__c & " " & Galaxy__c displays the remaining location information on the second line. The & operator connects two or more strings in Salesforce formulas.

Why others are incorrect:

Options using field names without __c are not correct for custom fields. Options using __r are relationship references, not direct custom field references. Options without BR() do not satisfy the two-line requirement.

===========

The correct answer is B. The Allow reparenting checkbox, Child records can be reparented to other parent records after they are created, is unchecked.

A service plan must be associated with one Contact, and users cannot change the Contact after the service plan is created. Since field access and validation rules are not the issue, the likely cause is a master-detail relationship where Allow reparenting is not enabled.

Salesforce documentation states that in master-detail relationships on custom objects, administrators can allow child records to be reparented by selecting Allow reparenting. If that option is not selected, users cannot change the parent record after the child record is created.

A and C relate to master-detail sharing settings, not changing the parent record. D is the opposite of the problem; if Allow reparenting were checked, users could change the parent Contact.

===========

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.

===========