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 answer is D. Custom Report Type.
A custom report type defines which records and fields are available in a report based on relationships between a primary object and related objects. Salesforce also references custom WITH or WITHOUT report types for reporting on related records.
Because DreamHouse Realty needs "with" or "without" reports involving a custom object and related lookup data, the app builder must create a Custom Report Type and define the object relationships.
Why others are incorrect:
A . Report Filters filter report results but do not define the reportable object relationship.
B . Row-Level Formula calculates values per row; it does not create with/without relationship reporting.
C . Report Bucket Field groups report values; it does not define related-object report structure.

The correct answer is A. Path.
Sales managers want reps to see recommendations, sales strategies, and key fields at each step of the Opportunity sales process. Salesforce Path is designed for exactly this. Path can highlight key fields and provide customized Guidance for Success for each stage of a process.
For Opportunities, Path can show reps which fields matter at each sales stage and provide stage-specific guidance such as qualification tips, sales strategy, or next-step recommendations.
C . Approval Process is for record approval routing.
D . Global Action is for creating or updating records quickly, not guiding users through sales stages.
B is not the correct Salesforce feature for this requirement.

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 D. Create an Apex Trigger on the Account object.
The requirement is conditional: allow Account deletion generally, but block deletion when the Account has open Opportunities. A validation rule is not the correct tool because validation rules evaluate record data during save operations, while this requirement is specifically about preventing a delete operation.
An Apex before delete trigger can query related open Opportunities and call addError() on the Account record to stop the delete. Salesforce Apex documentation confirms that triggers can run before or after delete events, and trigger errors can prevent DML operations from completing.
A is incorrect because removing Delete permission blocks all Account deletion.
B is incorrect because removing the Delete button is not security and does not stop deletion through other channels.
C is incorrect because validation rules are not the right mechanism to block conditional deletes.