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

Q381. An administrator wants a custom Lightning app to open with Accounts, Contacts, Opportunities, and Reports in a specific navigation order. Where should the administrator configure this?

1. Role Hierarchy
   2. App Manager navigation items
   3. Organization-Wide Defaults
   4. Sharing Rules

Correct Answer: 2. App Manager navigation items

Explanation: Lightning apps can be configured through App Manager, including the navigation items that users see and the order in which those items appear. This lets administrators create focused applications for different departments and workflows. Adding an object to app navigation improves accessibility but does not grant object or record permissions. Role Hierarchy and Sharing Rules influence record-level access, while Organization-Wide Defaults establish the baseline sharing model. Administrators should therefore configure the application’s navigation separately from profiles, permission sets, field-level security, and sharing settings that determine what users are actually authorized to access.

Q382. A company wants sales users to access a calculator, recent items, and other productivity tools from a persistent panel at the bottom of a Lightning app. Which feature should the administrator configure?

1. Compact Layout
   2. Path
   3. Related List
   4. Utility Bar

Correct Answer: 4. Utility Bar

Explanation: The Utility Bar provides persistent access to selected productivity components at the bottom of a Lightning app. Administrators can configure supported utilities according to the needs of users working in that app, allowing quick access without navigating away from the current record. Compact Layouts control the important fields shown in record highlights, Path guides users through business stages, and Related Lists display associated records. The Utility Bar is part of the Lightning application experience, so its configuration is handled at the app level rather than through record-sharing or object-security settings.

Q383. A user has forgotten a Salesforce password but the account is still active. What is the MOST appropriate administrative action?

1. Reset the user’s password using the supported user-management function
   2. Delete and recreate the user
   3. Change Organization-Wide Defaults to Public
   4. Create a new role for the user

Correct Answer: 1. Reset the user’s password using the supported user-management function

Explanation: When an active user simply needs a new password, the administrator should use Salesforce’s supported password-reset functionality rather than creating a replacement user. Recreating users can disrupt ownership, audit history, activities, and licensing relationships. Organization-Wide Defaults control record access and have nothing to do with authentication credentials, while roles primarily influence record-level visibility. Administrators should also investigate repeated password problems or suspicious login behavior when appropriate and should consider related authentication settings such as MFA, login history, IP restrictions, and session security rather than treating every authentication issue as a data-access problem.

Q384. A company wants users to see changes to selected Account fields directly in the record’s Chatter feed. Which feature should the administrator consider?

1. Account Team
   2. Case Escalation
   3. Feed Tracking
   4. Opportunity Splits

Correct Answer: 3. Feed Tracking

Explanation: Feed Tracking can publish changes to selected record fields into the record’s feed, allowing users who work with or follow the record to see important updates in a collaborative context. This is different from Field History Tracking, which is primarily intended to retain an auditable history of selected field changes. Account Teams support collaboration by assigning internal users to Accounts, Case Escalation manages service deadlines, and Opportunity Splits allocate sales credit. Administrators should decide whether the requirement is collaboration visibility, historical audit information, or both, because Feed Tracking and Field History Tracking serve different purposes.

Q385. A company uses different currencies and wants historical Opportunity amounts to be converted using rates associated with specific date periods rather than only the current conversion rate. Which feature should the administrator evaluate?

1. Advanced Currency Management
   2. Territory Management
   3. Campaign Influence
   4. Account Teams

Correct Answer: 1. Advanced Currency Management

Explanation: Advanced Currency Management supports dated exchange rates for certain Salesforce sales scenarios, allowing historical Opportunity-related currency values to reflect exchange rates applicable to specific time periods instead of relying exclusively on one current conversion rate. This is useful for organizations whose exchange rates fluctuate materially over time. Territory Management organizes sales coverage, Campaign Influence supports marketing attribution, and Account Teams support collaboration. Administrators should understand the implications and supported objects before enabling advanced currency capabilities because currency configuration can affect reporting, forecasting, and financial interpretation across a global Salesforce organization.

Q386. A sales manager wants users to create Opportunities from converted Leads but does not want Opportunity creation to be mandatory for every conversion. What should the administrator understand about standard Lead conversion?

1. Salesforce always requires an Opportunity
   2. Salesforce can convert only into an Account
   3. Opportunity creation can be optional during conversion
   4. Lead conversion always creates a Case

Correct Answer: 4. Opportunity creation can be optional during conversion

Explanation: Standard Lead conversion can create or associate an Account and Contact while allowing Opportunity creation to be optional, depending on the user’s workflow and Salesforce configuration. This supports organizations where some qualified Leads should become customers or contacts without immediately generating a sales Opportunity. Conversion does not create Cases as its standard purpose, and it is not limited to Account creation alone. Administrators should also understand custom Lead field mapping, duplicate handling, record ownership, campaign relationships, and converted Lead reporting because these factors influence how prospect data moves into downstream Salesforce sales processes.

Q387. A company wants sales representatives to indicate that an Opportunity was lost because of pricing, competition, or timing. Management needs the reason available for reporting. What is the BEST design?

1. Ask users to put the reason only in Chatter
   2. Create a structured Closed-Lost Reason field and require it when appropriate
   3. Change the Opportunity Owner
   4. Create a Case for every lost Opportunity

Correct Answer: 2. Create a structured Closed-Lost Reason field and require it when appropriate

Explanation: When management needs consistent reporting, important business information should be stored in a structured field rather than free-form collaboration content. A Closed-Lost Reason picklist can provide standardized values, and a Validation Rule or appropriate automation can require the field when an Opportunity moves to a closed-lost stage. This supports reliable trend analysis of why deals are lost. Changing ownership does not explain the outcome, while creating Cases would misuse the service data model. Administrators should choose picklist values carefully so they provide meaningful categories without becoming overly granular or difficult for sales representatives to use.

Q388. A support organization wants agents to select standardized reasons for why Cases were closed so management can analyze recurring resolution patterns. Which approach is BEST?

1. Use only free-form Case comments
   2. Add a new Salesforce user for each reason
   3. Store standardized closure reasons in a structured Case field
   4. Use Opportunity Forecast Categories

Correct Answer: 3. Store standardized closure reasons in a structured Case field

Explanation: A structured field such as a controlled picklist provides consistent values that can be grouped, filtered, and analyzed in service reports and dashboards. Free-form comments may still be useful for detailed notes, but they are difficult to aggregate reliably for management reporting. Creating users has no relationship to Case closure classification, and Opportunity Forecast Categories belong to the sales pipeline. Administrators should determine whether closure reasons should be required for particular Case statuses and may use validation or automation to ensure the information is captured before a Case is considered fully resolved.

Q389. A manager wants a report showing the difference between this month’s revenue and the previous month’s revenue for each group. Which reporting capability should the administrator investigate?

1. A summary formula using supported grouped-value functions
   2. Login IP Ranges
   3. Case Queue
   4. Record Type

Correct Answer: 4. A summary formula using supported grouped-value functions

Explanation: Salesforce summary formulas can perform calculations using summarized report information, and supported grouped-value functions can enable comparisons between groupings such as current and previous periods. This can help a manager analyze changes rather than viewing each period’s total independently. The report must be grouped appropriately for the calculation to make sense. Login IP Ranges control authentication locations, Case Queues provide shared ownership, and Record Types affect business processes. Administrators should verify the formula’s grouping level and test its behavior carefully, particularly when reports contain subtotals, grand totals, or missing periods.

Q390. A company wants a report that shows all Accounts, including Accounts that have no related Contacts. What should the administrator ensure when selecting or creating the report type?

1. The report type’s object relationship includes Accounts whether or not related Contacts exist
   2. Every Account has at least one Contact
   3. The Account OWD is Public Read/Write
   4. Every user has Modify All Data

Correct Answer: 1. The report type’s object relationship includes Accounts whether or not related Contacts exist

Explanation: Custom Report Types define relationships between objects and can specify whether the primary object’s records should appear only when related records exist or whether primary records should appear with or without related records. If management needs all Accounts, the report type must preserve Accounts even when no Contact exists. Security settings still determine which Accounts each user can access, but making the organization Public or granting Modify All Data would be unnecessarily broad. Administrators should design report types around the actual analytical relationship required rather than attempting to compensate with security changes.

Q391. An administrator exports Account data before a mass update and notices that several records share the same business name but have different Salesforce record IDs. What should the administrator do before assuming the records are duplicates?

1. Delete every repeated name immediately
   2. Change all names to unique random values
   3. Evaluate matching business attributes and duplicate criteria before merging or deleting records
   4. Hard Delete all but the oldest record

Correct Answer: 3. Evaluate matching business attributes and duplicate criteria before merging or deleting records

Explanation: Identical business names do not necessarily mean records are duplicates. Different locations, subsidiaries, legal entities, or business units can legitimately share similar or identical names. Administrators should examine other attributes such as address, external identifiers, phone numbers, customer numbers, and established matching logic before merging or deleting records. Duplicate management requires careful analysis because incorrectly consolidating legitimate records can damage related Contacts, Opportunities, Cases, and integration mappings. A backup should also exist before significant cleanup. Salesforce Matching Rules and Duplicate Rules can help formalize the organization’s criteria for future duplicate detection.

Q392. A company wants to load a CSV file containing new records but does not need update, delete, or upsert operations. The file is within the supported limits of Salesforce’s browser-based importer. Which tool is appropriate?

1. Flow Trigger Explorer
   2. Data Import Wizard
   3. Lightning App Builder
   4. Schema Builder

Correct Answer: 2. Data Import Wizard

Explanation: Data Import Wizard is appropriate for many supported browser-based import scenarios where an administrator or authorized user needs to add or update records without the more advanced features of Data Loader. It provides mapping and duplicate-handling capabilities for supported objects. Data Loader is usually preferred for larger datasets or advanced operations such as delete, hard delete, export, and sophisticated upserts. Flow Trigger Explorer manages automation visibility, Lightning App Builder configures user interfaces, and Schema Builder visualizes the object model. Source data should still be cleaned and validated before any import.

Q393. A record-triggered Flow should run only when a Case changes from any nonclosed status to a closed status. What should the administrator use?

1. Current and prior record values to detect the status transition
   2. A dashboard filter
   3. A Campaign hierarchy
   4. A public calendar

Correct Answer: 1. Current and prior record values to detect the status transition

Explanation: Transition-based automation requires comparing the record’s current state with its previous state. The Flow can determine whether the prior Case Status was not closed and whether the current Status is considered closed. This prevents the automation from running repeatedly on every later edit to an already closed Case. Using only the current status may cause unwanted repeat actions. Dashboard Filters, Campaign Hierarchies, and Public Calendars are unrelated. Administrators should also configure selective entry criteria whenever practical so the Flow processes only records that could satisfy the transition requirement.

Q394. A Flow retrieves 1,000 records but only needs records where Status equals Active for later processing. Which design can improve clarity and processing efficiency?

1. Add 1,000 separate Decision elements
   2. Create one Flow for each record
   3. Display all records in a Screen element
   4. Filter records as early as practical, ideally in Get Records or an appropriate collection filter**

Correct Answer: 4. Filter records as early as practical, ideally in Get Records or an appropriate collection filter

Explanation: Automation is easier to understand and usually more efficient when it retrieves only the records actually required for the business process. If Status = Active is known in advance, the administrator should normally apply that criterion in Get Records. If a collection already exists for another reason, appropriate collection filtering can narrow it before later processing. Creating large numbers of Decisions or separate Flows would be inefficient and difficult to maintain. Administrators should minimize unnecessary records, loops, and database operations when designing automation expected to process significant data volumes.

Q395. An administrator needs a Flow to perform different processing for three customer tiers: Gold, Silver, and Bronze. Which Flow element should contain the branching logic?

1. Loop
   2. Decision
   3. Get Records only
   4. Screen only

Correct Answer: 2. Decision

Explanation: A Decision element evaluates conditions and routes the Flow into different outcome paths. The administrator can define outcomes for Gold, Silver, and Bronze customers and optionally provide a Default Outcome for records that do not match the expected values. Loops are intended to iterate through collections, while Get Records retrieves Salesforce data. Screen elements interact with users but are not required merely to branch logic. Clear outcome labels and mutually understandable conditions make Flow logic easier to maintain. Administrators should also consider whether tier values are controlled by a picklist or other structured source to avoid unexpected values.

Q396. A scheduled automation creates renewal Tasks every night. Users report that duplicate Tasks are being generated for the same Contract. What is the BEST correction?

1. Give the Flow more permissions
   2. Run the Flow twice each night
   3. Check for an existing qualifying Task before creating another one
   4. Delete all Tasks every morning

Correct Answer: 3. Check for an existing qualifying Task before creating another one

Explanation: Recurring automation should be designed to be idempotent where practical, meaning repeated executions should not create unintended duplicate outcomes. Before creating a renewal Task, the Flow can search for an existing open Task that meets the same Contract and purpose criteria. A Decision can then create the Task only if no matching record exists. Increasing permissions or running the automation more often would worsen the problem, while deleting all Tasks could remove legitimate user work. Administrators should consider duplicate prevention whenever scheduled automation repeatedly evaluates the same population of records.

Q397. An Agentforce agent needs to answer questions from an approved internal policy repository. Which administrative concern is MOST important when that repository changes frequently?

1. Maintaining current, accurate, authorized grounding content
   2. Giving the agent access to every Salesforce object
   3. Removing all human escalation paths
   4. Granting users Modify All Data

Correct Answer: 1. Maintaining current, accurate, authorized grounding content

Explanation: An AI agent grounded in enterprise information is only as reliable as the content made available to it. If policy information changes frequently, administrators need a governance process that keeps approved sources current and removes obsolete content. Access to those sources must also respect applicable authorization requirements. Giving the agent unrelated Salesforce permissions does not improve grounding quality, and removing escalation can worsen outcomes when the agent is uncertain. Administrators should test important questions after significant content changes to verify that responses reflect the current approved policy rather than superseded information.

Q398. During Agentforce testing, the agent correctly handles normal requests but performs poorly on ambiguous questions. What should the administrator do NEXT?

1. Immediately deploy to all customers
   2. Give the agent administrative access
   3. Ignore ambiguity because users will always ask clear questions
   4. Add representative ambiguous test cases and refine topics, instructions, and handoff behavior**

Correct Answer: 4. Add representative ambiguous test cases and refine topics, instructions, and handoff behavior

Explanation: Agent testing should include ambiguous, incomplete, unexpected, and out-of-scope requests, not just ideal examples. If the agent performs poorly when user intent is unclear, administrators should expand test coverage and refine topic definitions, instructions, clarifying behavior, or escalation paths. Granting broader permissions does not improve interpretation and may increase risk. Broad production deployment before addressing known failures would expose more users to the problem. Iterative testing helps administrators understand where an agent can act confidently and where it should ask for clarification or hand the request to a human.

Q399. An Agentforce agent should provide information about customer orders but must never cancel an order. Which configuration BEST supports this requirement?

1. Give the agent the cancellation action and rely on instructions not to use it
   2. Do not expose the cancellation action; provide only the read capabilities required for the approved use case
   3. Grant Modify All Data so failures are avoided
   4. Make all Orders publicly editable

Correct Answer: 2. Do not expose the cancellation action; provide only the read capabilities required for the approved use case

Explanation: The strongest design is to avoid granting capabilities that the agent does not need. If an Agentforce agent is intended only to provide Order information, it should receive appropriate read access and necessary retrieval actions but not a cancellation action. Behavioral instructions can help guide the agent, but they should not substitute for actual access control. Removing unnecessary write capability reduces the impact of unexpected prompts, misclassification, or configuration errors. This follows least-privilege principles and aligns AI functionality with Salesforce’s existing object, field, record, and action security model.

Q400. A business process is currently handled through several manual steps and spreadsheets. Before automating the process in Salesforce, what should the administrator do FIRST?

1. Build the largest possible Flow immediately
   2. Add every available Salesforce feature
   3. Understand the business objective, current process, users, data, exceptions, controls, and desired outcome
   4. Give all participants System Administrator permissions

Correct Answer: 3. Understand the business objective, current process, users, data, exceptions, controls, and desired outcome

Explanation: Effective Salesforce automation starts with understanding the business process rather than immediately choosing a technical feature. The administrator should identify the objective, participants, required data, decision points, exceptions, security constraints, volume, timing, and success criteria. Only then should the appropriate Salesforce solution be selected, whether that involves Flow, approval processes, validation, page configuration, or another capability. Automating a poorly understood process can reproduce inefficiency and create new risks. A clear process analysis also makes testing easier because expected outcomes and exception scenarios are defined before implementation begins.