Free ADM-201 Practice Exam – 2025 Updated

B. Field-history tracking is automatically restored with the field; it does not remain deleted.

C. Custom fields are undeleted from an object’s Deleted Fields list, not from the Recycle Bin (which stores records, not metadata).

D. Page-layout references are automatically re-established; the field doesn’t have to be manually re-added to layouts.

1. Salesforce Help: “Delete and Erase Custom Fields → Undelete Custom Fields,” Summer ’24, para. 2 (“Page-layout references are restored; you must manually add the field to reports, list views, and search layouts as needed”).

2. Salesforce Help: “Considerations for Deleting Custom Fields,” Summer ’24, bullet “Field history tracking is restored when you undelete a field.”

3. Salesforce Help: “Recycle Bin Overview,” Summer ’24, para. 1-2 (Recycle Bin stores records, not setup metadata such as custom fields).

A. Roll-up summary: This is a field that aggregates data from child records to a parent record; it is not a type of relationship itself but a feature of a Master-Detail relationship.

C. Cross Object formula: This is a formula field that pulls data from a related object to display on another. It does not create the relationship or control record access.

D. Lookup field: This creates a loosely coupled one-to-many relationship where the parent and child records have independent owners and separate sharing settings, which is contrary to the requirement.

1. Salesforce Help Documentation, "Overview of Relationships": "In a master-detail relationship, the detail record inherits the sharing and security settings of its master record. If a user has access to the master record, they also have access to the detail records." This directly confirms that access to the child is limited by the parent.

2. Salesforce Help Documentation, "Relationship Considerations": Under the Master-Detail section, it states, "Detail and subdetail records inherit the sharing settings from the master record." Conversely, for Lookup relationships, it notes, "The two objects in a lookup relationship have their own sharing settings."

3. Trailhead, Salesforce Platform Basics Module, "Data Modeling" Unit: "In a master-detail relationship, the security settings of the detail record are inherited from the master record. It’s a tight bond between two objects." This official courseware explicitly links the Master-Detail relationship type to inherited, and thus limited, security.

B. Contact Hierarchy is limited to only 3,000 contacts at one time.

This is factually incorrect. The documented limit for the number of contacts displayed in the hierarchy is 2,000.

C. Customizing hierarchy columns changes the recently viewed Contacts list view.

These are two distinct and independent user interface components. Customizing the columns for the Contact Hierarchy page does not alter the standard "Recently Viewed Contacts" list view.

D. Sharing setting are ignored by contacts displayed in the Contact Hierarchy.

This is incorrect and contradicts a core principle of Salesforce data security. The Contact Hierarchy respects and enforces the sharing settings established for the user.

1. Salesforce Help, View the Contact Hierarchy: "The hierarchy shows contacts that you have at least read access to. If you can’t see a contact in the hierarchy, you don’t have permission to view that contact." This directly supports the correctness of option A and the incorrectness of option D.

2. Salesforce Help, Guidelines for Using the Contact Hierarchy: "The contact hierarchy shows a maximum of 2,000 contacts." This reference confirms that the limit stated in option B is incorrect.

3. Salesforce Help, Customize the Contact Hierarchy Columns: This document details the process of modifying the hierarchy columns by editing the ContactHierarchyColumns field set on the Contact object. The documentation makes no mention of this action impacting any other list views, thereby invalidating option C.

B. The user’s profile is missing view access.

This option is too general. While missing access to the report's folder is a valid cause, options A and D represent more specific and primary failure points directly related to the creation of a new custom report and report type.

C. The org has reached its limit of custom report types.

Organizational limits on custom report types would prevent the administrator from creating a new report type. It would not affect users' ability to access an already existing report.

---

1. Official Salesforce Documentation on Custom Report Type Status:

Source: Salesforce Help, "Set Custom Report Type Status"

Reference: The documentation states, "While a custom report type is in development, only administrators and users with the 'Manage Custom Report Types' permission can create and run reports from it. When the report type is deployed, all users with access to the objects in the report type can use it." This directly supports option A.

2. Official Salesforce Documentation on Report Folder Sharing:

Source: Salesforce Help, "Share a Report or Dashboard Folder in Lightning Experience"

Reference: This guide explains that reports and dashboards are shared via folders. It details that items in private folders are not accessible to other users. The section "Considerations for Sharing Folders" implicitly supports option D by describing private folders as being inaccessible to others unless explicitly shared.

3. Official Salesforce Documentation on Report and Dashboard Folders:

Source: Salesforce Help, "Reports and Dashboards"

Reference: Under the "Organize Reports and Dashboards in Folders" section, it is clarified: "Your personal folders are private. To share reports or dashboards in a personal folder, save them to a shared folder." This confirms that saving a report in a private folder (Option D) makes it inaccessible to others.

A. Einstein Lead Scoring: This feature scores leads, not opportunities. It helps prioritize which leads to convert into accounts, contacts, and opportunities, which is an earlier stage in the sales process.

B. Einstein Search Personalization: This feature tailors search results to individual users. While it improves efficiency in finding records, it does not provide any predictive analysis to help prioritize deals.

C. Einstein Activity Capture: This feature automates the logging of emails and events to related Salesforce records. It provides a more complete view of customer interactions but does not score or rank opportunities for prioritization.

1. Salesforce Help, Einstein Opportunity Scoring: "Give your sales team an easy way to prioritize opportunities so they can focus on the deals that are most likely to close... Each opportunity is given a score, from 1 to 99, which is available on opportunity records..."

2. Salesforce Help, How Einstein Opportunity Scoring Works: "Einstein Opportunity Scoring uses data science and machine learning to score your opportunities... Einstein builds a scoring model by analyzing your past opportunities, including custom fields and activity data."

3. Salesforce Help, Einstein Lead Scoring: "Einstein Lead Scoring helps your sales team prioritize leads so they can focus on the ones that are most likely to convert." (This confirms it applies to leads, not opportunities/deals).

4. Salesforce Help, Einstein Activity Capture: "Einstein Activity Capture helps keep data between Salesforce and your email and calendar applications up to date... Einstein logs the email and event activity to the activity timeline of related Salesforce records." (This confirms its purpose is data synchronization, not scoring).

A. Review the Security token.

A security token is only required for API access or when logging in from an IP address outside the organization's trusted IP ranges. It is not a general diagnostic tool.

B. Review the password history.

The password history tracks when a user's password was changed. It does not provide any information about login attempts or the reasons for login failures.

C. Review the Password policies.

Password policies are org-wide settings that define password requirements (e.g., length, complexity, expiration). Reviewing them does not explain a specific user's login failure.

1. Salesforce Help Documentation, "Monitor Login History." This document details the fields available on the Login History page. It explicitly states, "The Status column shows whether the user successfully logged in. If the login failed, the status shows the reason, for example, Invalid Password or Login-As Not Enabled for Admin." This directly supports using Login History as the diagnostic tool.

2. Salesforce Help Documentation, "Troubleshoot Login Issues." In the section for administrators, the first recommended step is to "Check the user's login history." This establishes it as the primary troubleshooting method. The guide states, "From Setup, in the Quick Find box, enter Login History, then select Login History... to see a list of login attempts."

3. Salesforce Security Guide, "Password Policies." This guide describes password policies as preventative security controls that "determine the requirements for user passwords." This confirms that policies are general settings, not logs for troubleshooting individual login events. (See section: "Set Password Policies").

4. Salesforce Help Documentation, "Reset Your Security Token." This document explains the purpose of a security token: "Salesforce requires a security token to log in to Salesforce from an external application or via the API." This clarifies that it is not relevant to all login scenarios.

A. Making the field required for all users would prevent sales managers from saving the record without an amount, which contradicts the requirement.

B. A formula field calculates a read-only value based on other fields; it cannot be used to enforce data entry on a different field.

C. Assigning the administrator profile to managers is a significant security risk and violates the principle of least privilege for a minor requirement.

1. Salesforce Help Documentation, "Validation Rules": "Validation rules verify that the data a user enters in a record meets the standards you specify before the user can save the record... For example, you can have a validation rule that requires a user to enter a justification if they change an opportunity's amount by more than 10%." This establishes the purpose of validation rules for conditional requirements.

2. Salesforce Help Documentation, "Validation Rule Fields": This document lists the available functions and global variables. The $Profile global variable can be used to check the current user's profile. The formula would look similar to: AND(ISPICKVAL(StageName, "Negotiation"), ISBLANK(Amount), $Profile.Name = "Sales User"). This shows how to combine record criteria with user criteria.

3. Trailhead, "Formulas and Validations" Module, "Create Validation Rules" Unit: "A validation rule can contain a formula or expression that evaluates the data in one or more fields and returns a value of 'True' or 'False'. Validation rules display an error message to the user when the formula returns a value of 'True'." This confirms the mechanism for enforcing the business logic described in the question.

A. Set up Web-to-Lead form the interns use.

Web-to-Lead is designed to capture leads from an external website, not for internal users performing manual data entry within Salesforce.

C. Create a separate Lead Lightning App.

A Lightning App controls the user interface and navigation (e.g., which tabs are visible) but does not inherently categorize or tag the records created within it.

D. Update the active Leas Assignment Rules.

Lead Assignment Rules are used to automatically assign ownership of new leads to specific users or queues based on criteria, not to identify the source or type of the record.

1. Salesforce Help - Create Record Types: "Record types let you offer different business processes, picklist values, and page layouts to different users. You might create record types to differentiate your regular sales deals from your professional services engagements, offering different picklist values for each." This directly supports using record types to differentiate records for different user groups.

2. Salesforce Help - Assign Record Types to Profiles: "After you create record types, you can make them available to users by adding them to user profiles... When users create a record, they can choose a record type." By assigning only the "Intern Lead" record type to the interns' profile, it becomes their default, meeting the requirement.

3. Salesforce Help - Set Up Web-to-Lead: "Set up Web-to-Lead to capture registration information or product interest on your company’s website and generate up to 500 new leads a day." This confirms Web-to-Lead is for external website capture.

A. Activities: While the 'Today's Tasks' and 'Today's Events' components are useful for productivity, they are more of a to-do list than a source of sales-specific insights like the Assistant or Performance Chart.

B. Path: Path is a component used on a record page (e.g., an Opportunity or Lead) to guide a user through the stages of a business process. It cannot be placed on the homepage.

1. Salesforce Help Documentation - Standard Lightning Page Components:

Assistant: "The Assistant shows users important things they need to address, including new leads and opportunities that need attention." (Found under "Standard Component: Assistant").

Key Deals: "Help your sales reps keep their most important opportunities top of mind with the Key Deals component." (Found under "Standard Component: Key Deals").

Performance: "The Performance component shows sales performance against a goal for a specific period... Add it to a home page..." (Found under "Standard Component: Performance").

Path: "Use the Path component on object record pages..." This confirms Path is for record pages, not the homepage. (Found under "Standard Component: Path").

C. Specify initial submission actions within the approval process.

Initial submission actions (e.g., locking a record) occur when a record is submitted, but they do not directly facilitate the approver's ability to respond.

E. Create a flow to automatically approve all records.

This eliminates the need for an approver to respond, which contradicts the goal of making it easier for them to respond.

1. Salesforce Help, Let Users Respond to Approval Requests from Chatter: This document states, "Enable approvals in Chatter so that users can see approval requests in their Chatter feeds and respond to them without leaving the feed." This directly supports option A.

2. Salesforce Help, Set Up Email Approval Response: This guide explains, "Enable email approval response so that users can approve or reject approval requests by email, without having to log in to Salesforce." This directly supports option B.

3. Salesforce Help, Standard Lightning Page Components: Under the "Items to Approve" component description, it states, "Shows a list of items waiting for the user’s approval. Users can approve or reject items from their home page in Lightning Experience." This directly supports option D.

4. Salesforce Help, Configure an Approval Process: This document details the components of an approval process, clarifying that "Initial Submission Actions" are automated behaviors that occur when a record is submitted, not actions that simplify the approver's response interface. This supports the exclusion of option C.

A. Create formula field: A formula field computes a value based on other fields. It cannot, by itself, assign a record to a user or queue.

C. Assign with an escalation rule: Escalation rules are exclusively for the Case object. They are used to reassign a case if it is not resolved within a specified time.

D. Configure a validation rule: A validation rule is used to enforce data integrity. It prevents a record from being saved if it does not meet certain criteria, but it does not perform assignments.

1. Salesforce Help, "Set Up Lead Assignment Rules": "Assignment rules automate your organization’s lead generation and support processes. Use lead assignment rules to automatically assign leads... For example, you can create a lead assignment rule that assigns leads with a specific country to a specific sales team." (Salesforce Documentation, Accessed 2023).

2. Salesforce Trailhead, "Automate Lead Management" module, "Set Up Lead Assignment Rules" unit: This unit provides a step-by-step guide on how to "Create lead assignment rules to make sure that leads are assigned to the appropriate sales reps." It uses examples based on geography (State/Province).

3. Salesforce Help, "Validation Rules": "Validation rules verify that the data a user enters in a record meets the standards you specify before the user can save the record." This confirms its purpose is data integrity, not routing. (Salesforce Documentation, Accessed 2023).

4. Salesforce Help, "Set Up Escalation Rules": "Escalation rules automatically escalate cases when the case meets the criteria defined in the rule entry." This document explicitly states the feature is for the Case object. (Salesforce Documentation, Accessed 2023).

A. Knowledge Management is used to create and manage a repository of articles and information, not for routing work based on agent capacity or skills.

C. Escalation Rules automatically re-route cases that have not been resolved within a certain time frame, not for initial assignment based on agent skills.

D. Territory Management is primarily a sales feature used to structure and assign accounts to sales teams based on criteria like geography, not service agent skills.

1. Salesforce Help, Omni-Channel for Administrators: "Omni-Channel is a comprehensive customer service solution that lets you route any type of incoming work item—including cases, chats, and leads—to the most qualified, available agents in your organization... You can also manage your agents’ capacity to take on work items so that they’re not over-assigned." (Found in the "What Is Omni-Channel?" section).

2. Salesforce Help, Set Up Skills-Based Routing: "Skills-based routing looks at the skills required to complete a work item and matches these to the skills that are assigned to an agent. Omni-Channel routes the work to the first agent who has the required skills and is available." (Found in the "Skills-Based Routing" overview section).

3. Salesforce Help, How Agent Capacity Works in Omni-Channel: "Capacity models determine how much work agents can take on... When you use a status-based capacity model, you specify the agent capacity for each agent presence status." (Found in the "Agent Capacity" section).

C: The correct context for filtering by device type is 'Form Factor', not 'View'. The available values are 'Desktop' and 'Phone'.

D: While filtering by Role is a valid mechanism, Profile is the standard method for controlling a user's functional access and what they can see in the user interface.

1. Salesforce Help Documentation: Dynamic Lightning Pages. This document outlines how to set component visibility filters. It explicitly states, "You can also base a filter on the viewing user’s details, such as their profile or role... Use [Device context] to set a component to display exclusively when the page is viewed in a specific experience, such as a phone or a desktop." This supports using both Profile and Form Factor as filter criteria.

2. Trailhead by Salesforce: Lightning App Builder Module, Make a Record Page Dynamic Unit. This official training module provides a direct example of setting component visibility. It demonstrates using the filter User > Profile > Name to show a component only for a "Sales User" profile and a separate example using Device > Form Factor to show a component only on a "Phone". This confirms that options A and B are the correct methods.

B. Approval Process: This tool is designed for formal record submission and approval sequences, not for automating data synchronization between related records upon a field change.

C. Prebuilt Macro: Macros are user-initiated sets of instructions to automate repetitive tasks within the user interface. The requirement is for an automatic, backend process.

D. Formula field: A formula field can display a value from a parent record on a child record, but it cannot be used to actively update a separate, editable field.

1. Salesforce Help, "Flow Builder": This document introduces Flow Builder as the primary tool for building declarative automations. It states, "Flow Builder can be used to build code-like logic without using a programming language... Automate a guided visual experience... Add more automation to your pages and apps... Start a process when a record is created or updated." This directly supports using Flow for the described record-update trigger.

2. Salesforce Help, "Record-Triggered Flow": This resource details the specific flow type needed. It explains, "A record-triggered flow starts when a record is created or updated... Record-triggered flows can update any record in the database." This confirms its capability to update the related Opportunity Products when the Opportunity is updated.

3. Salesforce Help, "Considerations for Updating Records in Flows": Under the section for record-triggered flows, the documentation implicitly supports this use case by explaining how to update related records. For example, "To update records that are related to the record that triggered the flow, add an Update Records element." This is the exact action required.

4. Salesforce Help, "Formulas": This documentation clarifies the function of formula fields, stating they "calculate their values from other fields, expressions, or values," confirming they are for calculation and display, not for executing an update on another field.

A. Create a workflow role to update the Event Date Field.

"Workflow role" is not a standard Salesforce feature. A workflow rule automates actions but does not provide a user interface for submitting a request.

B. Create an approval process on the Campaign object.

An approval process is for formally approving a submitted record. While useful, it is a secondary step; the primary need is a mechanism for the initial submission, which is creating the Campaign record itself.

C. Create a sharing rule so that other agents can view events.

A sharing rule controls record visibility. While this helps agents see existing events to avoid conflicts, it does not create the submission process for requesting a new event.

1. Salesforce Help Documentation - Campaigns:

Source: Salesforce Help, "Campaigns"

Reference: The documentation states, "Manage all of your marketing initiatives, such as advertisements, direct mail, or conferences, with campaigns." This establishes the Campaign object as the standard and appropriate tool for managing events like open houses.

2. Salesforce Help Documentation - Approval Processes:

Source: Salesforce Help, "Set Up an Approval Process"

Reference: "An approval process automates how records are approved in Salesforce." This confirms that an approval process is a subsequent action taken on an existing record (like a Campaign), not the initial method for creating or submitting the request.

3. Salesforce Trailhead - Campaign Basics:

Source: Trailhead, "Campaign Basics" module, "Get Started with Campaigns" unit.

Reference: This module explains that Campaigns are used to "organize and track marketing efforts" and can represent a "specific marketing effort, such as an advertisement, direct mail, or conference." This directly supports using Campaigns for open house events.

A. Metadata Backups are limited a sandbox refresh intervals.

This is incorrect. Metadata backup processes are independent of sandbox refresh schedules and are performed using different tools (e.g., Ant Migration Tool, Salesforce CLI).

C. Data export service should be run from a sandbox.

This is incorrect. The Data Export Service is intended to back up an organization's live production data. Running it in a sandbox would only back up test data.

1. Salesforce Help, Article 000322136, "Export Backup Data from Salesforce": This document explicitly states the scheduling options. Under the "Schedule an Export" section, it details the process and notes, "You can schedule backup files to generate automatically at weekly or monthly intervals." This directly supports the correctness of option B.

2. Salesforce Help, Article 000323461, "Back Up and Restore Your Salesforce Data and Metadata": This article clarifies the distinction between data and metadata backups. It states, "The weekly data export service...does not include your org's metadata." It then recommends using other tools for metadata, such as the "Ant Migration Tool," which confirms that metadata backup is a separate process (supporting option D).

3. Salesforce Metadata API Developer Guide, "Introduction": This guide describes the tools and processes for retrieving and deploying metadata. It outlines methods like the Ant Migration Tool and Salesforce CLI, which are entirely separate from the data-centric Export Service, reinforcing that metadata requires a different process.

A. Auto-Response Rules: These send automated email responses to customers when a case is created; they do not change record ownership or act on time-based triggers.

B. Validation Rule: These prevent a record from being saved if criteria are not met. They are used for data integrity, not for automating actions on existing records.

D. Assignment Rule: These automatically assign ownership of newly created cases to users or queues. They do not act on existing cases based on their age.

1. Salesforce Help, Set Up Escalation Rules: "Escalation rules automatically escalate cases when the case meets the criteria defined in the rule entry. You can create rule entries, which define criteria for escalating a case, and escalation actions, which define what happens when a case escalates." This document details how to set time-based criteria (e.g., Case age over X hours) to trigger actions like reassigning ownership.

2. Salesforce Help, Assignment Rules: "Assignment rules automate your organization’s lead generation and support processes. Use lead assignment rules to automatically assign leads. Use case assignment rules to automatically assign cases." The documentation specifies these rules run when a record is created.

3. Salesforce Help, Auto-Response Rules: "Auto-response rules let you automatically send email responses to lead or case submissions based on the record’s attributes." This confirms their purpose is for communication, not record updates.

4. Salesforce Help, Validation Rules: "Validation rules verify that the data a user enters in a record meets the standards you specify before the user can save the record." This highlights their function in data validation, not process automation over time.

A. Approval process: This tool is designed for submitting records for formal approval, not for automating a field update based on a simple field change.

B. Formula Field: A formula field calculates its value dynamically each time it is viewed and cannot be used to stamp a static date based on a one-time event.

D. Validation Rule: This tool is used to enforce data integrity by preventing a record from being saved if certain conditions are not met; it cannot perform actions like updating fields.

---

1. Salesforce Help, "Flow Builder": "Flow Builder is the declarative interface used to build individual flows. You can use Flow Builder to build code-like logic without using a programming language." This establishes Flow as the primary tool for declarative logic and actions.

2. Salesforce Help, "Record-Triggered Flow": "A record-triggered flow runs when a record is created or updated... In a record-triggered flow, you can update any record, but it’s most efficient to update the triggering record." This directly supports using a record-triggered flow to update the account record that initiated the process.

3. Salesforce Help, "Which Automation Tool Do I Use?": This guide compares automation tools and states, "We recommend building all new automation in Flow Builder." It positions Flow as the successor to Workflow Rules and Process Builder for tasks like this field update.

4. Salesforce Help, "Considerations for Formula Fields": "A formula field calculates its value from an expression that you define. The formula field is read-only." This confirms that a formula field cannot be used to permanently set a value at a specific point in time.

A scheduled report is a reactive tool that can identify invalid data after it has been saved, but it cannot prevent its initial entry.

Making a field required ensures it is not left blank but does not validate the actual value entered against specific numerical constraints.

There is no standard declarative feature in Salesforce Setup called "Account Revenue limits" for setting minimum and maximum values on fields; this is the function of a validation rule.

---

1. Salesforce Help Documentation: Validation Rules.

Reference: "Validation rules verify that the data a user enters in a record meets the standards you specify before the user can save the record." This confirms that validation rules are the correct tool to prevent saving invalid data.

Location: Salesforce Help > Salesforce Administrator > Data Management > Validation Rules.

2. Salesforce Trailhead: Formulas and Validations Module, Create Validation Rules Unit.

Reference: "Validation rules help you improve data quality by preventing users from entering incorrect data." The unit provides a step-by-step guide on creating a rule with a formula and error message.

Location: Trailhead > Admin Beginner > Data Modeling > Formulas and Validations > Create Validation Rules.

3. Salesforce Help Documentation: Validation Rule Examples.

Reference: The document provides numerous examples, including one for a number range: OR(NumberOfEmployees 40000). This logic is directly analogous to the requirement in the question.

Location: Salesforce Help > Salesforce Administrator > Data Management > Validation Rules > Validation Rule Examples.

A. Lightning Data: This AppExchange product is used to enrich existing Salesforce records with third-party data; it does not provide business process templates or user-facing calculators.

B. Lightning Community: This is a Salesforce platform (now Experience Cloud) for building digital experiences, not a specific, installable AppExchange template for a single business process.

D. Bolt Solutions: These are comprehensive, pre-built templates for entire communities (Experience Cloud sites), which is a much broader scope and likely more complex than the requested process.

1. Salesforce Help Documentation, "Find Solutions on AppExchange": This document outlines the different types of solutions available. It defines Flow Solutions as "Installable flow templates that automate complex business processes." This directly supports the choice of Flow Solutions for a "templated process."

2. Salesforce Trailhead, "AppExchange Basics" Module, "Get to Know AppExchange Listings" Unit: This module explains that "Flow Solutions are partner-built integrations for Flow Builder. They make it easy to connect Salesforce to other systems and automate complex processes." This confirms their purpose as pre-built automation templates.

3. Salesforce Help Documentation, "Salesforce Bolt Solutions": This source defines a Bolt as a "pre-built solution that you can use to get a head start on your community." This highlights that Bolts are for entire communities, not just a single process, making them less specific to the request than a Flow Solution.

4. Salesforce Help Documentation, "Find and Use Lightning Data": This document states, "Lightning Data lets you compare your records with data from third-party providers and update them." This confirms its function is data enrichment, not process automation.

B. Bucket column: This is a feature used within a report to group field values into categories, not a mechanism to filter an entire dashboard.

C. Dashboard component: This is a visual representation of a report (e.g., a chart or table) on a dashboard, not the tool used for filtering the dashboard's data.

D. Combination Chart: This is a specific type of dashboard component for visualizing data; it does not provide filtering capabilities for the entire dashboard.

1. Salesforce Help Documentation: Filter Dashboard Data. This document states, "Add filters to let readers focus on data that's most important to them. For example, you can add a filter on Opportunity Owner to let your sales managers see data for each of their reps." This directly aligns with the scenario of filtering by 'Owner'.

2. Trailhead Module: Reports & Dashboards for Lightning Experience, Unit: Visualize Your Data with the Lightning Dashboard Builder. The section "Add Filters to Let Viewers Slice Data Their Way" explains, "Dashboard filters make it easy for viewers to apply different data perspectives to a single dashboard... You can add up to 3 filters per dashboard." This confirms that adding filters for the three requested fields (Origin, Status, Owner) is the correct and standard approach.

3. Salesforce Help Documentation: Categorize Your Data with Bucket Columns. This source clarifies the function of bucket columns: "Bucketing lets you quickly categorize report records without creating a formula or a custom field." This distinguishes it as a report-level feature, confirming why it is an incorrect choice for dashboard-level filtering.

A. Record setting and search index: Record access is controlled by the sharing model and object permissions, not a generic "record setting." The search index is built based on a user's permissions; it does not define them.

C. App permissions and search terms: App permissions control access to a collection of tabs and objects as an application, but not the underlying object permissions. Search terms are user-defined and not a security control.

D. Page layouts and field- level security: These settings control what a user sees on a record's page after they have already gained access to it. They do not prevent a user from finding or accessing the record itself.

---

1. Salesforce Help, Object Permissions: "Object permissions specify the base-level access users have to create, read, edit, and delete records for each object... For example, if you give users 'Read' permission on the accounts object, they can see account records, but they can’t edit them." This confirms that the ability to find records via search stems from the "Read" permission.

Source: Salesforce Help, Documentation, Security, Control Access to Objects, "Object Permissions".

2. Salesforce Help, View and Edit Tab Settings in Permission Sets and Profiles: "Tab Hidden - The tab isn’t available in the All Tabs page or visible in any apps. Users can’t view the tab. However, they can still view records for that object if they have the necessary permissions." This clarifies that hiding a tab is insufficient; the underlying object permission must be removed to fully restrict access.

Source: Salesforce Help, Documentation, User Management, "View and Edit Tab Settings in Permission Sets and Profiles".

3. Trailhead, Data Security Module, Control Access to Objects Unit: "The first level of data access you can control is for entire objects. You can prevent a user from seeing, creating, editing, or deleting any instance of a particular type of object, like a lead or an opportunity, by setting object permissions." This establishes object permissions as the foundational control for restricting access.

Source: Trailhead, Admin Beginner Trail, Data Security Module, "Control Access to Objects".

B: Changing the OWD to Public Read/Write would grant all users access to all opportunities, which is overly permissive and violates the principle of least privilege.

C: Enabling Territory Management is a complex solution for a simple sharing requirement. Furthermore, manual sharing is not scalable or automated for sharing all records that meet a criterion.

D: An owner-based sharing rule grants access to records based on who owns them, not on the attributes of the records themselves. This would not share all cross-sell opportunities.

1. Salesforce Security Guide, "Sharing Rules": This guide explains that "Criteria-based sharing rules determine with whom to share records based on field values other than ownership." This directly supports using a criteria-based rule for the 'cross-sell' opportunity type. (See section: "Types of Sharing Rules").

2. Salesforce Help, "Create a Criteria-Based Sharing Rule": This document outlines the process: "1. Define the rule... 2. Select which records to share... Specify the criteria that records must match to be included in the sharing rule. 3. Select the users to share with... select Public Groups...". This confirms that combining criteria with a public group is the standard procedure.

3. Salesforce Help, "Manage Public Groups": "Public groups are a way to group users... Use public groups to... set up sharing rules." This reference establishes the purpose of a public group as a collection of users for sharing purposes, fitting the "team of subject matter experts" scenario.

4. Trailhead, "Control Access to Records", Unit: "Configure Sharing Settings": This module states, "Use criteria-based sharing rules when you want to share records based on a field value rather than ownership." This educational resource reinforces the correct application of criteria-based sharing rules for this specific scenario.

A. Use a new version of the flow for each scenario.

This is inefficient and creates unnecessary maintenance overhead. A single flow should handle different scenarios using conditional logic, not separate versions.

B. Use a decision element and a new screen to show the proper question.

A decision element directs the flow's path between screens. The requirement is to conditionally show questions on the same screen, not navigate to different screens.

D. Use branching in the flow screen to show the proper scenario.

"Branching in the flow screen" is not a standard Salesforce feature. Flow branching is achieved with elements like 'Decision', which operates between, not within, screen elements.

1. Salesforce Help Documentation, "Set Component Visibility in Flow Screens": This document explicitly states, "You can declare that a component appears on a screen only when certain conditions are met... For example, on a screen, you can show a text box for a shipping address only if the user selects 'Ship' for a picklist." This directly supports using conditional visibility for the described scenario.

2. Salesforce Help Documentation, "Flow Element: Screen": In the section describing the properties of screen components, it details the "Set Component Visibility" section. It explains how to add conditions to control when a component is displayed, confirming this is the correct feature to use for showing or hiding elements on the same screen.

3. Trailhead, "Screen Flow Distribution," Unit: "Control Who Sees What in a Flow Screen": This module provides practical examples and states, "You can add logic to your screen components so that they appear only when they’re needed... When you configure a screen component, you can specify when to display it." This aligns perfectly with the question's requirement.

A. Related List: This component displays a list of records that are related to the current record (e.g., Case Comments on a Case), not fields from a single parent record like the Account.

C. Record Details: This component displays the fields of the current record (the Case) based on its assigned page layout. It cannot be used to display custom messages or fields from related records.

1. Salesforce Help, Lightning App Builder Standard Components:

Rich Text Component: "Add text and simple HTML markup to your Lightning page... You can also set visibility filters on this component." This supports its use for the conditional, bolded message.

Related Record Component: "Use the Related Record component to display the details of a related record, including the details of a parent record, on your Lightning page... Users can update the related record directly from the component without leaving the page." This directly addresses the need to update the parent Account's status.

Related List Component: "Use the Related List component to display a single related list for a record on your Lightning page." This clarifies its function is to show lists of child/related records, not edit a parent.

Record Detail Component: "The Record Detail component displays fields and sections from the page layout associated with the object." This confirms it is only for the record being viewed.

B. Themes apply to salesforce classic and to the salesforce mobile app.

Lightning Experience themes are exclusive to the Lightning Experience desktop UI and do not apply to Salesforce Classic or the Salesforce mobile app, which have separate branding controls.

C. Up to 150 custom themes can be created, modified, or cloned from the built-in themes.

This is incorrect. The official limit for the number of custom themes that can be created in a Salesforce org is 300, not 150.

1. Salesforce Help Documentation, "Considerations for Themes":

For Answer A: "You can have only one active theme at a time, and a theme applies to your entire org."

For Answer D: "Chatter External users see the built-in Lightning Blue or Lightning Lite theme."

For Incorrect Option B: "Themes don’t apply to Salesforce Classic or to the Salesforce mobile app."

2. Salesforce Help Documentation, "Create and Manage Themes":

For Incorrect Option C: "You can create up to 300 custom themes, and you can package themes." This document explicitly states the limit is 300.

A. Login Hours: This is incorrect because Login Hours are configured at the Profile level to control when specific users can access Salesforce, not in the org-wide Company Settings.

B. Password Policy: This is incorrect as Password Policies, which define password complexity and expiration, are also managed at the Profile level, not within the Company Settings section.

1. Salesforce Help, "View and Edit Your Company Information": This document explicitly lists Default Language, Default Locale, and Currency Locale as fields that can be configured on the Company Information page. It states, "The language in which all text and online help are displayed in your Salesforce org." and "The locale for currency, dates, and times."

2. Salesforce Help, "Supported Locales": This resource details the impact of the Locale setting, which includes the Currency Locale, confirming its importance for formatting data correctly for different regions, a key requirement for a global team.

3. Salesforce Help, "Password Policies": This documentation confirms that password policies are set for users through profiles. The section "Set Password Policies" begins with the instruction, "From Setup, in the Quick Find box, enter Profiles."

4. Salesforce Help, "Restrict Login Hours and IP Ranges on Profiles": This guide details the process for setting login hours, specifying that these restrictions are applied directly to a user's profile, not as an org-wide setting under Company Information.

A. Email-to-Case: This feature is used to automatically create cases from inbound emails. It is a case creation channel, not a tool for routing cases from all sources.

C. Auto-Response Rules: These rules send automated email responses to the person who submitted the case. They do not determine case ownership or routing.

D. Web-to-Case: This feature generates a web form to capture customer support requests and create cases. It is a source for case creation, not a routing mechanism.

1. Salesforce Help Documentation, "Set Up Assignment Rules": "Use case assignment rules to automatically assign cases to users or queues based on criteria you define. Typically, your organization has one rule for routing cases..." This document explicitly states that case assignment rules are used for automatic assignment to queues based on criteria.

2. Salesforce Help Documentation, "Case Assignment Rules": "A case assignment rule is a set of conditions that determines how a case is assigned to a user or a queue... When a case is created manually or automatically through Web-to-Case, Email-to-Case, or On-Demand Email-to-Case, the assignment rule is triggered." This confirms the rules work regardless of the case creation method.

3. Trailhead, "Automate Case Management" module, "Set Up Assignment Rules" unit: "Case assignment rules are a great way to automate your support process. They let you automatically assign incoming cases to specific agents or queues, so you don’t have to do it manually." This reinforces that assignment rules are the primary tool for automating case ownership.

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.

A. Map the lead custom field to the product's product category field.

Lead fields are mapped to fields on the Account, Contact, and Opportunity objects during conversion, not directly to fields on the Product object.

B. Create a workflow to update Opportunity fields based on the lead.

While automation could be used post-conversion, the standard, declarative method for this specific requirement is the built-in Lead Conversion Field Mapping feature.

D. Configure the product categories picklist field on the product.

Configuring fields on the Product object is unrelated to the process of mapping and transferring data from a Lead to an Opportunity during conversion.

1. Salesforce Help Documentation: Map Custom Lead Fields for Lead Conversion.

Reference: The documentation explicitly states the required steps. Under the "Salesforce Classic" and "Lightning Experience" sections, the first step is: "Create a custom field on the account, contact, or opportunity object that you want to map the custom lead field to." This directly supports the necessity of creating a custom field on the Opportunity first.

2. Trailhead by Salesforce: Set Up Lead Conversion.

Reference: In the unit "Customize the Lead Conversion Process," the section "Map Custom Lead Fields" states: "For your custom lead fields, create custom fields on the account, contact, or opportunity so your data is carried over when your sales reps convert leads." This confirms that creating a custom field on the target object is the prerequisite for mapping.