The correct answer is C.

A junction object is commonly created with two master-detail relationships. Salesforce documentation states that sharing access to a junction object record is determined by the user’s access to both associated master records and the sharing setting on the relationship fields.

Here, Account Interest is the junction object between Account and Interest. If users do not have read access to the Interest object, they cannot view the Interest records. Because access to the junction object depends on access to both master records, they also cannot view the associated Account Interest records.

Why not others:

A is wrong because lack of read access to Interest does not give read-only access automatically.

B is wrong because the user can still view the Account if they have Account access.

D is wrong because junction object access is not simply “show junction but hide Interest details.”

===========

Based on the exact options provided, the correct answer is A. Create a master-detail relationship field on Open Position to Application.

The requirement says one applicant must be able to apply for multiple open positions using a single application. In Salesforce, the relationship field is created on the detail/child object. Therefore, to allow one Application__c record to relate to multiple Open_Position__c records, the master-detail field would be created on Open_Position__c and point to Application__c . Salesforce Trailhead confirms that in a master-detail relationship, the relationship field is created on the detail object.

Salesforce also uses master-detail relationships and junction objects to model many-to-many relationships.

Important note: In a fully normalized recruiting data model, a separate junction object between Application and Open Position is usually cleaner. But from the provided answer choices, A is the only option that supports one Application being connected to multiple Open Positions.

===========

The correct answer is D. Rich text area.

The requirement says users need to write detailed descriptions that can include pictures and links. Salesforce Rich Text Area fields are designed for formatted text and support images and hyperlinks.

Long text area supports longer plain text but not rich formatting with images. URL stores a single web address. Multi-select picklist stores selected values, not detailed formatted descriptions.

===========

The correct answer is B.

When customer invitations are enabled for Chatter groups, invited customers get limited collaboration access. Salesforce documentation states that customers can see only the groups they’re invited to and can interact only with members of those groups.

A is incorrect because invited customers do not automatically get broad group-invitation rights. C is incorrect because Chatter customer access does not grant access to Account records. D is incorrect because customers are invited to specific groups; they do not receive general public-group request access.

===========

The correct answer is A because Salesforce provides the Establish upper bound on existing picklists option to protect picklist performance by limiting inactive picklist values. Salesforce documentation states that this setting runs a query to identify picklists with fewer than 4,000 inactive values and enforce the limit.

Why others are incorrect:

B is for reusing picklist values across fields, not reducing inactive picklist performance impact.

C would worsen the issue because it removes limits on inactive values.

D is too drastic and not the recommended Salesforce feature for this issue.

===========

The correct answer is D. Deselect auto add to custom report type.

When creating a new custom field, Salesforce provides an Auto Add option that can automatically add the new field to applicable existing custom report types. If the app builder does not want the new field to appear on pre-existing custom report types, they should deselect the Auto add to custom report type option during field creation. Salesforce release documentation confirms that Auto Add automatically adds custom fields to custom report types based on that object.

Why the other options are incorrect:

Removing the field from page layouts only affects record-page visibility, not report type availability.

Changing profile visibility or read-only access affects field security, not whether the field is added to the custom report type layout.

===========

The correct answer is A. Add the field to the custom report type field layout.

The report already exists: Position with or without Applicants Report. The issue is not that reporting is disabled for the object; the issue is that the new Applicant field is not available as a column in that custom report type. For custom report types, fields available to report builders are controlled by the custom report type field layout. Salesforce’s documentation for adding fields to a custom report type directs admins to open the report type and use Edit Layout to add the missing fields.

B is incorrect because field-level security can hide a field from a user, but the troubleshooting step for a field missing from a custom report type column list is to add it to the custom report type layout.

C is incorrect because the report type already exists and is being used.

D is incorrect because the field data type was already assigned when the field was created.

===========

The correct answer is A.

UC has three Lead sources: web, trade shows, and partners. Some Lead information is common to all, while other fields are unique to each source. The best configuration is to use Lead record types with separate page layouts so each type of Lead shows the fields relevant to that process. Salesforce documentation states that record types allow different business processes, picklist values, and page layouts for different users or record categories.

B is not ideal because it leaves irrelevant fields visible and relies on users to collapse sections. C unnecessarily creates a different Lead object for the partner community. D is incorrect because separate custom objects would fragment Lead management and prevent standard Lead functionality from being used consistently.

===========

The correct answers are C. Text field and D. Number field.

Salesforce allows custom Text, Number, Email, and Auto Number fields to be marked as External ID fields. Since the available choices include Text and Number, those are the two valid answers.

Why others are incorrect:

A. Phone field cannot be marked as an External ID.

B. URL field cannot be marked as an External ID.

===========

The correct answer is B. Edit a record page using Lightning App Builder > Drag the component onto the page.

A custom Lightning component installed from AppExchange is configured on a Lightning record page through Lightning App Builder. Salesforce documentation states that Lightning App Builder supports custom Lightning components, including Aura and Lightning web components, and record pages are edited as Lightning pages.

The Page Layout editor is used for fields, buttons, related lists, and layout behavior, not for placing Lightning components on a Lightning record page. App Manager manages apps and utility bars, but the page canvas configuration is done in Lightning App Builder.