To meet the requirements, the administrator must first create a data structure to hold the shoe design information. Since Salesforce has no standard object for this purpose, creating a new custom object is the necessary first step.

Next, a relationship must be established between the new Shoe Design object and the standard Product object. The requirement that "Shoe designs should be unable to be deleted" is critical. A Master-Detail relationship enforces a cascade-delete behavior, meaning if a Product record is deleted, all its related Shoe Design records are also automatically deleted. This violates the requirement. A Lookup relationship, however, is loosely coupled and does not cascade-delete child records, making it the correct choice to ensure shoe designs can persist independently of the product.

A. A master-detail relationship's cascade-delete feature would delete shoe designs if the parent product is deleted, directly violating the core requirement.

C. Salesforce does not include a standard object named "Designs." Therefore, a custom object must be created to track this type of information.

1. Create Custom Objects: Salesforce Help

Article ID 000328449

"Create a Custom Object." This document outlines the process and purpose of creating custom objects to "store information that’s unique to your organization." This supports the selection of option B.

2. Object Relationships Overview: Salesforce Help

Article ID 000321637

"Object Relationships Overview." This official guide details the behavior of different relationship types.

For Master-Detail relationships

it states: "Deleting a master record deletes all detail records." This confirms why option A is incorrect.

For Lookup relationships

it states: "Deleting a record that’s on the parent side of a lookup relationship doesn’t affect the child record." This confirms why option D is the correct choice to prevent automatic deletion.

3. Trailhead - Data Modeling Module

Create Object Relationships Unit: This educational module explicitly contrasts the two relationship types. It states

"In a master-detail relationship

the detail record can’t exist without the master. If a master record is deleted

all of its detail records are deleted along with it." This reinforces the reasoning for rejecting the master-detail relationship in this scenario.

Campaign Member Status values are configured on a per-campaign basis, allowing each campaign to have a unique set of statuses. To modify these values, an administrator must first ensure the "Campaign Member Statuses" related list is visible on the Campaign page layout. Once visible, the administrator or an authorized user can directly add, edit, or remove the status picklist values from that related list on the specific campaign record. This provides the flexibility to tailor member statuses to the context of each individual marketing initiative.

B. Edit the picklist values for the Campaign Status in object Manager.

This is incorrect because it confuses "Campaign Status" (e.g., Planned, Completed) with "Campaign Member Status" (e.g., Sent, Responded). Also, member statuses are edited on the campaign record, not globally in Object Manager.

C. Mass modify the Campaign Member Statuses related list.

This is not a standard Salesforce function. While you can mass-update campaign member records, you cannot "mass modify" the available picklist values for the status field itself.

1. Salesforce Help

"Customize Campaign Member Statuses": This document outlines the procedure for changing these values. It states

"You can create custom Campaign Member Status values for each campaign... From a campaign record

you can add

edit

and delete status values. Open the campaign you want to customize... Click Edit on the Campaign Member Statuses related list." This directly supports option D.

2. Salesforce Help

"Customize Page Layouts with the Enhanced Page Layout Editor": This guide explains how to manage page layouts. To make the functionality described in the first reference available

an administrator must "drag related lists... onto the page layout." This supports option A as a necessary prerequisite if the related list is not already present.

The standard Salesforce lead conversion process is the correct method for this scenario. When a lead is converted, Salesforce creates an Account, a Contact, and optionally an Opportunity. Crucially, this process automatically transfers the lead's campaign history to the new contact record. This ensures that the link between the new contact and the original "open house" campaign is preserved, fulfilling the requirement to keep the associated campaign member history. Initiating this action from the campaign member detail page is a direct and valid way to start the conversion.

A. Deleting the lead permanently removes its record and all associated history, including the campaign membership, which is the opposite of the desired outcome.

B. Cloning creates an unnecessary duplicate lead record. Converting the clone would not associate the original lead's campaign history with the new contact.

D. This action would create a new, separate contact but fails to convert the existing lead, resulting in duplicate records and an incomplete lead lifecycle.

1. Salesforce Help Documentation: Convert Qualified Leads. Under the "What Happens When You Convert Leads?" section

the documentation states: "Campaign History: The Campaign History related list of the lead is moved to the contact record." This confirms that the standard conversion process preserves the campaign association.

2. Trailhead Module: Leads & Opportunities for Lightning Experience. In the unit "Qualify and Convert Leads

" it is explained: "When you convert a lead

the campaign member information is transferred to the contact record." This directly supports that conversion is the correct procedure to maintain campaign history.

3. Salesforce Help Documentation: Considerations for Converting Leads. This document details the effects of lead conversion

noting: "The campaign member record is moved to the new contact." This explicitly verifies that the campaign member status is transferred

not lost.

When a field is marked as "Required" in the Object Manager, it becomes universally required at the data model level. This means a value must be provided for this field whenever a record is created or updated, regardless of the user's profile or the method used (e.g., user interface, API, Data Loader). To ensure users can always populate the field, Salesforce automatically adds it to the bottom of the first section on all page layouts for that object where it is not already present.

A. The field is not required to save records via the API on that object.

This is incorrect. A universally required field enforces the requirement at the database level, meaning it is mandatory for all data entry points, including the API.

D. The field is optional when saving records via web-to-lead and web-to-case.

This is incorrect. Web-to-lead and web-to-case are methods of record creation. If a universally required field is not populated by the web form, the record creation will fail.

1. Salesforce Help Documentation

"Custom Field Attributes":

Under the "Required" attribute description

it states: "Requires that users enter a value for the custom field when they create or edit a record... Making a field required at the field level (universally required) means that... The field is required for all users

regardless of their profile... The field is automatically added to all page layouts." This directly supports answers B and C.

2. Salesforce Help Documentation

"Set Field-Level Security

Page Layouts

and Required Fields":

This document clarifies the difference between page layout requirements and universal requirements. It notes that a universally required field "must have a value to save a record in the user interface

the Force.com API

and so on." This confirms that the requirement applies via the API

invalidating option A.

3. Trailhead

Salesforce Platform Basics

"Data Modeling" Module

"Understand Custom & Standard Objects" Unit:

This module explains object and field customization. In the section on field properties

it details that the "Required" checkbox on the field definition makes it "universally required

" which is enforced across all interfaces

including API calls and automated processes like Web-to-Lead

which contradicts option D.

Data Loader is a client application that uses the Salesforce API to access data. When a user attempts to log in to Salesforce from an external application or from an IP address that is not included in the organization's trusted IP ranges, an additional security verification is required. This verification is a security token, which is a unique, system-generated alphanumeric code. To successfully authenticate, the user must append this security token directly to the end of their password in the password field.

A. Add a permission set that allows them to import data.

An administrator profile includes the "API Enabled" and object permissions required to import data by default, so an additional permission set is not necessary.

C. Use the Data Import Tool to mass import custom object records.

The question specifically asks about using the Data Loader. The Data Import Tool (or Wizard) is a separate, web-based tool with different capabilities and limitations.

D. Reset their password and their security token.

Resetting the password or token is only required if the user has forgotten them or if the password has expired. It is not a mandatory step for every login.

1. Salesforce Help Documentation

"Log In to Data Loader": "In the Password text box

enter your Salesforce password

with your security token appended to the end. For example

if your password is mypassword and your security token is XXXXXXXXXX

enter mypasswordXXXXXXXXXX." This directly supports the requirement to append the token.

2. Salesforce Help Documentation

"Reset Your Security Token": "If you can’t find your security token

you can reset it... When you change your Salesforce password... Salesforce also sends you a new security token". This clarifies that resetting is a conditional action

not a standard login procedure.

3. Salesforce Help Documentation

"Control Login Access Policies": This document explains how trusted IP ranges work. "Users who try to log in from an IP address outside the defined range are challenged to verify their identity... For API access

they must append a security token to their password." This establishes the context for when a token is needed.

4. Salesforce Help Documentation

"Standard Profiles": The System Administrator profile description confirms that it includes the "API Enabled" permission

making option A unnecessary for the user in the scenario.

To provide the sales manager with appropriate report access, three components must be configured. First, the report must be placed in a shared folder, and the manager must be granted Folder Access (B) to view it. Second, the manager's profile or permission set requires the correct Field-Level Security (D) to see the data in the report's columns. Third, a Custom Report Type (A) may be necessary to define the specific objects and fields available for the report if a standard type is insufficient. These steps control access to the report definition, its structure, and its data columns. The underlying record-level access for the manager to see their team's records is handled by the role hierarchy, which is a foundational prerequisite in this scenario.

C. Report subscription: This feature is used to schedule and email report results to users who already have access. It does not grant access to the report or its underlying data.

References:

1. Folder Access (B):

Source: Salesforce Help Documentation

Reference: Article "Share a Report or Dashboard Folder". It states, "To share a report or dashboard folder, you need Viewer, Editor, or Manager access to it... Your access level to a folder determines what you can do with the folder and its contents." This confirms that folder access is required to view the report.

2. Field-Level Security (D):

Source: Salesforce Help Documentation

Reference: Article "Set Field-Level Security for a Field on a Profile". It details, "Field-level security settings let you restrict what fields users can view and edit... If a user doesn't have 'Read' access to a field, that field's column is not visible in any reports." This directly links FLS to report column visibility.

3. Custom Report Type (A):

Source: Salesforce Help Documentation

Reference: Article "Create a Custom Report Type". It explains, "Report types act as a template... You choose which objects and fields are available to users who are creating reports from the custom report type." This establishes the CRT as a necessary configuration for defining the report's structure and available data.

4. Role Hierarchy (Implicit Prerequisite):

Source: Salesforce Help Documentation

Reference: Article "Control Access to Records". It clarifies, "The first step in controlling data access is to set your organization-wide sharing defaults... To open up access to records, you can use... a role hierarchy." With a private OWD, the role hierarchy is the standard mechanism that grants managers access to their team's records, which then appear in the report.

When a user manually creates a case, the case edit page includes a checkbox labeled "Assign using active assignment rules." This checkbox can be set to be selected by default on the page layout. If it is checked, the active assignment rule is triggered. Since the rule is designed for web or email cases, the manually created case will not meet the rule's criteria. Consequently, Salesforce assigns the case to the Default Case Owner specified in the Support Settings, which in this scenario is the administrator, instead of the creating user.

A. An escalation rule is changing the case owner on case creation: Escalation rules are time-based and trigger after a case has been open for a specified period, not immediately upon creation.

C. Another assignment rule is giving ownership to the administrator: Salesforce allows only one active case assignment rule at a time, so it is not possible for "another" rule to be firing.

D. The Owner field is missing on the webform and email template: This is irrelevant as the problem described is with manually created cases, not cases submitted via web or email.

1. Salesforce Help Documentation

"Set Up Assignment Rules": This document explains the function of assignment rules. It states

"When a case is created

it’s automatically assigned to a user or queue based on criteria you define... If no assignment rule entry criteria are met

the case is assigned to the Default Case Owner." This supports the logic that a non-matching case goes to the default owner.

2. Salesforce Help Documentation

"Configure Support Settings": This page details the "Default Case Owner" setting. It specifies that this user or queue becomes the owner of cases that do not match any assignment rule criteria. This confirms why the administrator would become the owner if they are set as the default.

3. Salesforce Help Documentation

"Case Page Layouts": The properties for the case page layout include the option to set the "Assign using active assignment rules" checkbox to be selected by default. This is the direct mechanism that causes the assignment rule to run on manually created cases

leading to the described issue.

To ensure consistent picklist values across the Account and Case objects, a Global Picklist (also known as a Picklist Value Set) is the ideal feature. It allows an administrator to define a single, master list of values that can be shared by multiple custom picklist fields.

To implement this, a Custom Picklist field must be created on both the Account and Case objects. During the creation of these custom fields, the administrator would select the option to use the predefined Global Picklist value set. Subsequently, the available values for each field can be tailored for different record types as required.

A. Dependent Picklist: This feature filters a picklist's values based on a selection in a different (controlling) field, which is not the scenario described.

C. Multi-Select Picklist: This is a field type that allows users to select multiple values. It does not address the core requirement of value consistency across objects.

1. Salesforce Help

"Create a Global Picklist Value Set": This document states

"A global picklist is a restricted picklist by nature. Only a Salesforce admin can add or modify its values. Users can’t add unapproved values... Use a global value set to share the values with other picklist fields." This directly supports the use of a Global Picklist for consistency.

2. Salesforce Help

"Create a Custom Picklist Field": In the setup steps for creating a custom picklist

Step 5 explicitly details the option to use a global value set: "To use a global picklist value set

select it from the list." This confirms that a Custom Picklist field is the mechanism to implement the global set.

3. Salesforce Help

"Assign Picklist Values to Record Types": This guide explains the process for customizing which values from a picklist are available for specific record types. It states

"After you create a record type

you can specify which picklist values are associated with it." This addresses the second part of the requirement.

The two most critical components for testing a new flow are using the dedicated testing tool and the appropriate, safe environment. The Debug feature in Flow Builder is the primary tool for unit testing. It allows an administrator to run the flow as a specific user, input test values, and see the detailed execution path and results without activating the flow. Best practice dictates that all development and testing, including for flows, must be conducted in a sandbox. This isolates the testing process from the live production environment, preventing accidental data changes and disruption to business operations.

A. Set Up a flow interview to test the flow.

A "flow interview" is simply a running instance of a flow. This is a generic term for what happens during debugging or a live run, not a specific testing component or method.

B. Run the flow using it to create contacts.

While this is the ultimate goal of the test, it is an action performed within the testing framework. The more fundamental components are the tool used (Debug) and the environment (Sandbox).

1. Salesforce Help

"Test Your Flow": This document explicitly describes the debugging process. It states

"The Debug button in Flow Builder lets you enter values for your flow’s input variables and display debug details while the flow runs... That way

you can verify that the flow works as you expect it to for that user." This directly supports using the Debug tool (Option C).

2. Salesforce Help

"Sandboxes: Staging Environments for Customizing and Testing": This official documentation outlines the purpose of sandboxes. It states

"A sandbox is a copy of your organization in a separate environment that you can use for a variety of purposes

such as testing and training... Because a sandbox is isolated from your production organization

operations that you perform in your sandbox don’t affect your production organization." This confirms that testing should occur in a sandbox (Option D).

3. Trailhead

"Flow Builder" Module

"Debug a Flow" Unit: This educational unit details the step-by-step process of using the debug tool within Flow Builder to test the logic and outcome of a flow

reinforcing the importance of this specific feature for testing (Option C).

This solution requires two distinct capabilities: a guided user interface for submission and a structured system for routing and authorization.

Flow Builder is the ideal tool for creating a guided, screen-based process (Screen Flow) that walks users through the steps of submitting an expense report. This directly addresses the need for a "guided expense report process" and simplifies submissions.

An Approval Process is the standard Salesforce feature designed specifically for managing "routing and authorizations." It automates how records are approved, defining the chain of command, criteria for approval, and the actions to be taken upon approval or rejection. A flow can initiate an approval process once the user has completed the guided submission.

A. Validation Rule: A Validation Rule is used to enforce data integrity and quality by preventing users from saving invalid data. It does not guide users through a process or manage approvals.

D. Quick Action: A Quick Action provides a shortcut to perform a specific task, such as creating a record or launching a flow. While it could be used to start the process, it does not build the guided interface or the approval logic itself.

1. Flow Builder & Screen Flows:

Salesforce Help

Flow Builder: "With Flow Builder

you can build screen flows to guide your users through a business process." This directly supports using Flow Builder for the "guided expense report process."

Salesforce Help

Flow Core Action: Submit for Approval: This document explicitly details how a Flow can be used to "Submit one or more records for approval

" confirming the synergy between Flow Builder and Approval Processes.

2. Approval Process:

Salesforce Help

Set Up an Approval Process: "An approval process automates how records are approved in Salesforce. An approval process specifies each step of approval

including who to request approval from and what to do at each point of the process." This confirms its role in handling routing and authorizations.