Salesforce Administrator ADM-201 Exam Dumps 2025

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.