The app builder should create a sharing rule that grants the users Read/Write access to the Application records. A sharing rule is a type of rule that can extend record access to groups of users based on certain criteria. In this case, the app builder can create a sharing rule that grants Read/Write access to the Application object to the recruiters based on their role, public group, or queue. This will allow them to edit the Application records related to any Internship record, regardless of the ownership. Option A, B, and C are not ways to configure the proper access.

To count child records (Trails) on a parent record (Park) without code, a Roll-up Summary field is required. However, Roll-up Summary fields only work when a Master-Detail relationship exists.
Why A (Roll-up Summary) is correct:Exact Extract:"A roll-up summary field calculates values from related records, such as those in a related list, on a master record. You can count the number of related records or summarize fields." - Salesforce Help | Roll-Up Summary Fields Why D (Master-Detail Relationship) is correct:Exact Extract:"Roll-up summary fields are available only for master-detail relationships." - Salesforce Help | Relationships OverviewTherefore, the Trail object must be the detail and the Park object the master to enable the roll-up count.
Why D (Master-Detail Relationship) is correct:Exact Extract:"Roll-up summary fields are available only for master-detail relationships." - Salesforce Help | Relationships OverviewTherefore, the Trail object must be the detail and the Park object the master to enable the roll-up count.
Why not B:Formula fields can't count related records.
Why not C:Lookup relationships don't support roll-up summaries natively.
Reference:
Salesforce Help | Roll-Up Summary Fields
Salesforce Help | Relationships Overview
Salesforce Platform App Builder Exam Guide | Data Modeling and Management

To restrict visibility of the Jupiter field on the Solar System object specifically to users with the Outer Planets profile:
C . Field-level security (FLS). This allows the app builder to control access to fields based on user profiles.
Steps to set up field-level security:
Navigate to Setup → Object Manager → Solar System.
Select Fields & Relationships → Jupiter field.
Click Field-Level Security.
For all profiles except Outer Planets, set the Visible option to unchecked, ensuring these users cannot see the field.
For the Outer Planets profile, check Visible to grant access.
This configuration ensures that only users with the Outer Planets profile can view the Jupiter field.
For more information on field-level security, check Salesforce's guide on Field-Level Security.

When multiple objects require the same picklist values, the correct approach is to create a Global Picklist Value Set (also called a Global Value Set). This allows an organization to maintain one centralized list of picklist values that can be reused across multiple picklist fields on different objects.
Why C is correct:Exact Extract:"Global value sets let you share the same picklist values with more than one picklist field. A global value set is a set of shared values that you define once and use in multiple custom picklist fields." - Salesforce Help | Global Value SetsThis ensures consistent data values, simplifies maintenance, and makes changes automatically available wherever the global picklist is used.
Why C is correct:Exact Extract:"Global value sets let you share the same picklist values with more than one picklist field. A global value set is a set of shared values that you define once and use in multiple custom picklist fields." - Salesforce Help | Global Value SetsThis ensures consistent data values, simplifies maintenance, and makes changes automatically available wherever the global picklist is used.
Why not A (Related Picklist):"Related Picklist" is not a valid Salesforce feature.
Why not B (Shared Custom Field):Salesforce does not provide a "Shared Custom Field" functionality. Each field belongs to a specific object.
Why not D (Dependent Picklist):Dependent picklists control available values based on another field's value. They do not allow reuse of a single value list across multiple objects.
Reference (Salesforce Platform App Builder documentation / Study Guide topics):
Salesforce Help | Global Value Sets
Salesforce Help | Picklist Fields
Salesforce Platform App Builder Exam Guide | Data Modeling and Management

To create "with" or "without" reports on the new custom object, a custom report type is needed. A custom report type defines the relationship between one or more standard or custom objects for reporting purposes. It allows users to select which fields they want to display in their reports and filter by related objects.