View Full Salesforce ADM-201 Exam Dumps and Practice Test Dumps.

Q301. A Salesforce user is experiencing an issue that the administrator cannot reproduce. The user wants to allow the administrator to access Salesforce as that user temporarily for troubleshooting. Which capability is MOST relevant?

1. Manual Sharing
   2. Account Team
   3. Grant Login Access
   4. Campaign Influence

Correct Answer: 3. Grant Login Access

Explanation: Grant Login Access allows a user to authorize an administrator or approved support personnel to log in as that user for troubleshooting, subject to Salesforce configuration and permissions. This can help the administrator reproduce issues involving page layouts, permissions, application behavior, or user-specific configuration without asking for the user’s credentials. Manual Sharing grants record access, Account Teams support collaboration on Accounts, and Campaign Influence tracks marketing contribution to sales. Administrators should use impersonation-style troubleshooting carefully, respect organizational privacy policies, and limit access to the period necessary to investigate the reported problem.

Q302. A user can access Accounts but cannot create records for a newly introduced record type that colleagues can use. What should the administrator verify FIRST?

1. Whether the record type is assigned to the user’s profile or appropriate access configuration
   2. Whether the Account organization-wide default is Public
   3. Whether the user owns a Campaign
   4. Whether a Case Queue exists

Correct Answer: 1. Whether the record type is assigned to the user’s profile or appropriate access configuration

Explanation: Record types must be made available to users through their access configuration before they can select them when creating records. A user can have full object access to Account yet still lack access to a specific Account record type. The administrator should therefore review the user’s profile and related record-type availability and default settings. Organization-wide defaults govern record visibility rather than record-type selection. Campaign ownership and Case Queues are unrelated. Record-type access should also be checked alongside page-layout assignments and picklist values because these configuration elements work together to produce the user’s record-creation experience.

Q303. A company wants the same standardized list of industry classifications reused in picklist fields on Account, Lead, and a custom Vendor object. Which configuration should the administrator use?

1. Three unrelated text fields
   2. Three separate role hierarchies
   3. A sharing rule
   4. A global value set used by the picklist fields

Correct Answer: 4. A global value set used by the picklist fields

Explanation: A global value set allows administrators to maintain one centralized collection of picklist values and reuse it across multiple custom picklist fields. This improves consistency because updates to the approved value set can be managed centrally rather than maintaining several independent lists. Text fields would allow inconsistent free-form entries, while role hierarchies and sharing rules deal with record access rather than field values. Global value sets are especially useful for enterprise classifications such as regions, product categories, industries, or standardized reasons that must remain consistent across several objects.

Q304. An administrator wants a custom field to display a clickable website address constructed from another field on the record. Users should not manually enter the displayed link. Which solution is BEST?

1. Auto Number field
   2. Formula field using an appropriate hyperlink function
   3. Roll-Up Summary field
   4. External ID field

Correct Answer: 2. Formula field using an appropriate hyperlink function

Explanation: Formula fields can generate calculated text and links dynamically from other record values. By using an appropriate hyperlink function and URL construction, the administrator can create a clickable link without requiring users to maintain the value manually. Because the formula recalculates when referenced data changes, it stays aligned with the source field. Auto Number fields generate identifiers, Roll-Up Summary fields aggregate detail records, and External IDs support matching with external systems. Formula fields are useful whenever the displayed information should be derived automatically rather than stored as separate manually maintained data.

Q305. A company has a multi-select picklist named Services Interested In. The administrator wants users to choose several services for one Lead. What should the administrator remember about multi-select picklists?

1. They can store more than one selected value and may require special handling in formulas, reporting, and integrations
   2. They can contain only one value per record
   3. They automatically create related Service records
   4. They provide record-level security

Correct Answer: 1. They can store more than one selected value and may require special handling in formulas, reporting, and integrations

Explanation: Multi-select picklists allow users to select several values in one field, which can be convenient for certain classification requirements. However, they behave differently from ordinary picklists in formulas, reporting, data imports, integrations, and automation. Administrators should evaluate these limitations before selecting this field type, especially when values need sophisticated analytics or downstream processing. Multi-select picklists do not automatically create related records and have no security function. In some data models, a related child object may be more flexible when selections require attributes, detailed reporting, or frequent integration processing.

Q306. A custom object is used as a junction object between Consultant and Project. The business wants each junction record to depend on both related records. Which data model is commonly used?

1. Two text fields
   2. One Auto Number and one formula
   3. Two master-detail relationships on the junction object
   4. One Chatter group for each project

Correct Answer: 3. Two master-detail relationships on the junction object

Explanation: A many-to-many relationship in Salesforce is commonly created using a junction object with two master-detail relationships, one to each parent object. Each junction record represents one association, such as one Consultant assigned to one Project. This structure allows many Consultants to relate to many Projects while preserving structured relational data. The master-detail configuration also affects sharing, ownership, cascade deletion, and roll-up capabilities, so administrators should ensure those behaviors fit the business requirement. Text fields and Chatter groups do not create relational data relationships between Salesforce records.

Q307. A salesperson regularly works with the same sales engineer and regional manager on Opportunities. The salesperson wants to add those colleagues quickly to new Opportunities. Which feature should the administrator consider?

1. Campaign Member Status
   2. Default Opportunity Team
   3. Case Queue
   4. Knowledge Data Category

Correct Answer: 2. Default Opportunity Team

Explanation: Default Opportunity Teams allow a salesperson to define users who frequently collaborate on the salesperson’s Opportunities and add them efficiently to Opportunity records. Team members can have specified Opportunity Team roles and appropriate access according to configuration. This reduces repetitive manual selection for sales teams that work together consistently. Campaign Member Status tracks marketing engagement, Case Queues provide shared ownership for service work, and Knowledge Data Categories organize Knowledge articles. Opportunity Teams are intended for internal sales collaboration while leaving one user as the primary Opportunity owner.

Q308. An administrator is troubleshooting why a custom button that worked in Salesforce Classic does not provide the desired experience in Lightning Experience. What should the administrator evaluate?

1. Only organization-wide defaults
   2. Whether the user has a Campaign
   3. Whether the button is compatible with Lightning and whether a Lightning action or Flow is more appropriate
   4. Whether the Recycle Bin contains records

Correct Answer: 4. Whether the button is compatible with Lightning and whether a Lightning action or Flow is more appropriate

Explanation: Some custom button implementations designed for Salesforce Classic do not translate directly to Lightning Experience, especially approaches relying on unsupported URL techniques or JavaScript buttons. The administrator should evaluate the intended business outcome and determine whether a supported Lightning action, Flow, component, or other current mechanism is a better solution. Organization-wide defaults govern record access rather than button compatibility. Campaigns and the Recycle Bin are unrelated. Administrators should modernize legacy user-interface customizations where practical instead of assuming every Classic implementation will behave identically in Lightning Experience.

Q309. A support team wants the Case page to provide a feed-oriented workspace showing customer communications and record activity in a service-friendly interface. Which Salesforce capability should the administrator evaluate?

1. Case Feed
   2. Opportunity Forecasting
   3. Campaign Influence
   4. Territory Management

Correct Answer: 3. Case Feed

Explanation: Case Feed provides a feed-based interface for working with customer-service Cases and can bring relevant communications and Case activity into a service-oriented workspace. It is designed to help agents follow interactions and handle support work efficiently. The precise service experience depends on the organization’s Salesforce configuration and current Service features. Opportunity Forecasting and Territory Management apply to sales processes, while Campaign Influence applies to marketing attribution. Administrators should design the Case user experience around the information and actions agents need most frequently while continuing to enforce appropriate object, field, and record access.

Q310. A sales manager needs to know the number of different Accounts represented in an Opportunity report, not merely the total number of Opportunity rows. Which report feature should be considered?

1. Unique Count on the appropriate field
   2. Case Assignment Rule
   3. Login Hours
   4. Page Layout Assignment

Correct Answer: 1. Unique Count on the appropriate field

Explanation: Unique Count can show how many distinct values appear for a supported field in a report. If an Opportunity report contains multiple Opportunities for the same Account, counting rows would overstate the number of different customer Accounts represented. Applying Unique Count to the relevant Account field provides a more meaningful distinct count where supported. Case Assignment Rules, Login Hours, and Page Layout Assignments do not affect report calculations. Administrators should choose report summaries that answer the actual business question rather than assuming ordinary record counts always provide the correct metric.

Q311. An administrator wants to export records that include items currently in the Recycle Bin for a data-recovery investigation. Which Data Loader operation should be evaluated?

1. Insert
   2. Export All
   3. Upsert
   4. Hard Delete

Correct Answer: 4. Export All

Explanation: Data Loader’s Export All operation can include records that have been soft deleted and remain relevant to recovery or auditing scenarios, unlike a standard export that focuses on active records. This can help an administrator investigate data that was recently deleted. Insert creates new records, Upsert updates or inserts according to matching identifiers, and Hard Delete permanently removes records. Administrators should understand the difference between ordinary deletion, Recycle Bin retention, hard deletion, standard export, and Export All when designing data-management and recovery procedures.

Q312. A company is importing Contacts and wants to associate each Contact with the correct Account using an external identifier maintained on Account rather than Salesforce Account IDs. What should the administrator leverage where the import tool supports it?

1. Case Status
   2. Relationship mapping using an Account External ID
   3. Opportunity Forecast Category
   4. Chatter group membership

Correct Answer: 2. Relationship mapping using an Account External ID

Explanation: External IDs can help integrations and data-loading tools match Salesforce records to identifiers from outside systems. Where supported, relationship mapping can use the parent object’s External ID so imported child records such as Contacts can be associated with the correct Account without first translating every external identifier into a Salesforce record ID. This simplifies repeatable integrations and migrations. Case Status, Forecast Categories, and Chatter membership are unrelated. Administrators should ensure the external identifier is reliable and ideally unique so one source-system value corresponds to the intended Salesforce record.

Q313. A dashboard should always show the five highest-revenue Opportunities rather than every Opportunity in the source report. Which report capability should the administrator evaluate for the dashboard source?

1. A row limit combined with appropriate sorting
   2. A public group
   3. A record type
   4. A validation rule

Correct Answer: 1. A row limit combined with appropriate sorting

Explanation: A report can use sorting together with a row limit in supported configurations to restrict results to the highest or lowest records according to a chosen measure. For example, sorting Opportunity Amount from highest to lowest and limiting results can produce a focused source for a top-deals dashboard component. Public Groups affect access administration, Record Types control processes and layouts, and Validation Rules enforce data quality. Administrators should confirm that the report format and dashboard component support the desired behavior and that the sort order accurately reflects the metric management wants to analyze.

Q314. A manager wants a matrix-style report with Sales Region across columns and Product Family down rows so revenue can be compared across both dimensions. Which report format should be used?

1. Tabular
   2. Summary
   3. Joined
   4. Matrix

Correct Answer: 4. Matrix

Explanation: Matrix reports group data by both rows and columns, making them appropriate when users need to compare summarized values across two dimensions. In this case, Product Family can be grouped by rows while Sales Region appears across columns, with Opportunity revenue summarized at the intersections. Tabular reports primarily provide lists, while Summary reports group mainly by rows. Joined reports combine separate report blocks rather than simply providing two-dimensional grouping. Matrix reports are especially useful for management analyses where comparisons across categories need to be visible in one structured table.

Q315. A Flow must send an approval-related notification only when a record’s Discount Percentage changes from 20% or less to above 20%. Which logic should the administrator use?

1. Send the notification whenever any field changes
   2. Evaluate only the current value
   3. Compare the current value with the prior value and detect the threshold crossing
   4. Create a new user for every approval

Correct Answer: 3. Compare the current value with the prior value and detect the threshold crossing

Explanation: The automation needs to identify a transition across a threshold, not merely whether the current discount is above 20%. Comparing current and prior values lets the Flow detect that the previous value was at or below 20% and the new value is greater than 20%. This prevents duplicate notifications on later edits while the discount remains above the threshold. Current-value-only logic could execute repeatedly. Administrators should use prior-record information, selective entry criteria, and clear Decision logic to ensure transition-based automations run only when the meaningful business change occurs.

Q316. A Screen Flow displays a long form to several audiences. The administrator wants certain components to have different visual styling without creating separate flows for each audience. Which current capability should the administrator evaluate?

1. Component-level styling overrides for Screen Flows
   2. Organization-wide defaults
   3. Lead Assignment Rules
   4. Account Hierarchy

Correct Answer: 2. Component-level styling overrides for Screen Flows

Explanation: Salesforce’s Spring ’26 Platform Administrator maintenance material highlights component-level styling overrides for Screen Flows, allowing administrators to tailor the appearance of supported screen components for different audiences without relying on separate flow implementations for every visual variation. This can improve usability and maintainability when the underlying process remains the same. Organization-wide defaults manage record visibility, Lead Assignment Rules route Leads, and Account Hierarchy shows relationships among Accounts. Administrators should still keep accessibility, consistency, and maintainability in mind when applying visual customization to business-critical guided processes.

Q317. A company wants selected non-administrator users to be able to delete Salesforce Files as part of a governed records-management process. Which current Spring ’26 capability should the administrator evaluate?

1. Delete Salesforce Files permission
   2. Opportunity Splits
   3. Campaign Hierarchy
   4. Case Team

Correct Answer: 4. Delete Salesforce Files permission

Explanation: Salesforce’s Spring ’26 Platform Administrator maintenance content highlights the Delete Salesforce Files permission, which expands file-management capabilities for appropriate non-administrator users. This can support delegated records-management responsibilities without requiring users to become full System Administrators. Because file deletion can have significant consequences, the permission should be granted only to users with a legitimate business need and should be governed according to retention and compliance requirements. Opportunity Splits, Campaign Hierarchies, and Case Teams address unrelated sales, marketing, and service collaboration needs.

Q318. An Agentforce agent has an action that retrieves customer information. Testing shows the action fails only for users with restricted Account access. What should the administrator investigate FIRST?

1. Whether the users have more dashboard subscriptions
   2. The Salesforce permissions and record access required by the action
   3. Whether the Campaign Type is correct
   4. Whether the users have Public Calendars

Correct Answer: 1. The Salesforce permissions and record access required by the action

Explanation: Agentforce actions still depend on appropriate Salesforce security and access. If an action succeeds for users with broad access but fails for users with restricted Account visibility, the administrator should investigate object permissions, field-level security, sharing, and the specific records the action needs. Broadening access indiscriminately is not the right first response; the action should function only within the user’s authorized scope. Dashboard subscriptions, Campaign Type, and Public Calendars do not govern Account access. Agent testing should include multiple realistic permission profiles so security-dependent behavior is discovered before broad deployment.

Q319. An Agentforce agent repeatedly selects the wrong action when two actions have similar purposes. Which configuration improvement is MOST appropriate?

1. Give both actions unrestricted access to every object
   2. Remove Salesforce security checks
   3. Refine action descriptions, instructions, scope, and testing so the intended use of each action is clear
   4. Add unrelated actions to increase choice

Correct Answer: 2. Refine action descriptions, instructions, scope, and testing so the intended use of each action is clear

Explanation: When an agent has difficulty choosing between similar actions, administrators should clarify the semantic distinction between them through well-defined action descriptions, topic instructions, scope, and representative testing. Each action should have an understandable purpose and only the permissions necessary for that purpose. Adding more unrelated actions increases ambiguity, while removing security controls creates risk without addressing action selection. Administrators should test prompts that could plausibly match either action and refine configuration until the agent consistently chooses the appropriate capability or escalates when the correct action is uncertain.

Q320. An administrator is assessing whether a new declarative automation should be implemented with Flow. What should be considered BEFORE building it?

1. Only whether Flow Builder has an attractive interface
   2. Whether every user has System Administrator access
   3. The business trigger, required data, actions, timing, scale, error handling, and existing automation
   4. Only the number of fields on the object

Correct Answer: 3. The business trigger, required data, actions, timing, scale, error handling, and existing automation

Explanation: Good automation design begins with understanding the business requirement rather than immediately adding Flow elements. Administrators should identify what triggers the process, which records and fields are required, what actions must occur, whether execution should happen before save, after save, asynchronously, or on a schedule, and how errors should be handled. Existing automation should also be reviewed to prevent duplicate or conflicting logic. Scale matters because inefficient queries or repeated database operations can create performance issues. A clear design produces automation that is easier to test, troubleshoot, document, and maintain.