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

Q361. A company wants new Salesforce users to start with the organization’s preferred language, locale, and time zone values, while still allowing administrators to change them for individual users. Where should the administrator review the organization defaults?

1. Sharing Settings
   2. Object Manager
   3. Role Hierarchy
   4. Company and organization settings

Correct Answer: 4. Company and organization settings

Explanation: Organization-level company settings define important defaults used when Salesforce users are created, including items such as language, locale, and time zone configuration. These defaults give administrators a consistent starting point while individual user settings can still be adjusted when employees work in different countries or regions. Sharing Settings controls record-level visibility, Object Manager manages object metadata, and Role Hierarchy affects access to records owned by other users. Administrators should understand the difference among language, locale, and time zone because each changes a different part of the Salesforce user experience.

Q362. An administrator wants to prevent users from creating more than one Contact with the same government-issued customer identifier. Which field configuration provides the strongest straightforward control?

1. Mark the custom identifier field as Unique
   2. Add the field to a Compact Layout
   3. Make the field a controlling picklist
   4. Add the field to a dashboard

Correct Answer: 1. Mark the custom identifier field as Unique

Explanation: Marking a custom field as Unique instructs Salesforce to prevent duplicate values in that field across records. This is appropriate when the business identifier itself must be unique, such as an externally assigned customer number. A Duplicate Rule could provide more sophisticated matching behavior, but a Unique field is a direct way to enforce uniqueness for one exact identifier. Compact Layouts affect highlighted information, controlling picklists affect dependent selections, and dashboards provide analytics. Administrators should verify whether case sensitivity and external integration behavior matter when defining a field that acts as a business key.

Q363. A custom child object is in a master-detail relationship with a parent object. The business wants administrators to be able to move an existing child record from one parent record to another. Which relationship option must be enabled?

1. Track Activities
   2. Allow Reports
   3. Allow Reparenting
   4. Grant Access Using Hierarchies

Correct Answer: 3. Allow Reparenting

Explanation: In a master-detail relationship, the master normally defines important ownership and lifecycle behavior for the detail record. If the business needs users to move a detail record from one master to another, the administrator must enable the Allow Reparenting option where supported. This should be considered carefully because changing the master can affect sharing, roll-up calculations, and the business meaning of the record. Track Activities and Allow Reports control different object capabilities, while Grant Access Using Hierarchies affects record visibility rather than whether the master relationship itself can be changed.

Q364. A company wants a custom record page to display a different Lightning page depending on the record’s app and the user’s profile. Which configuration is MOST appropriate?

1. Organization-Wide Defaults
   2. Lightning page activation and assignment
   3. Case Escalation Rule
   4. Campaign Member Status

Correct Answer: 2. Lightning page activation and assignment

Explanation: Lightning App Builder allows administrators to activate pages and assign them according to supported combinations such as app, record type, and profile. This makes it possible to tailor the Lightning experience to different user groups without changing the underlying object. Organization-Wide Defaults control baseline record access, Case Escalation Rules handle service escalation, and Campaign Member Status tracks marketing responses. Administrators should remember that Lightning page assignment affects the interface only; object permissions, field-level security, and record sharing still determine which data the user can actually access through the page.

Q365. A custom object contains an Amount field and a Discount Percentage field. Users need to see a calculated Net Amount that always reflects the latest values without manually maintaining it. Which solution should be used?

1. Formula field
   2. Auto Number field
   3. External ID field
   4. Queue

Correct Answer: 1. Formula field

Explanation: A Formula field calculates its value dynamically from other fields and functions. Net Amount can therefore be calculated from Amount and Discount Percentage without requiring users or automation to maintain a separate stored value. If either source field changes, the formula result automatically reflects the latest values. Auto Number fields generate sequential identifiers, External ID fields help match records with external systems, and Queues manage shared record ownership. Formula fields are especially useful for derived values that should always remain synchronized with their source data and do not require an independent historical stored value.

Q366. Marketing wants to identify Leads and Contacts who belong to a Campaign but have not yet responded. Which Salesforce data should the administrator ensure is used consistently?

1. Opportunity Forecast Category
   2. Account Team Role
   3. Case Priority
   4. Campaign Member Status

Correct Answer: 4. Campaign Member Status

Explanation: Campaign Member Status records how each Lead or Contact has interacted with a Campaign, allowing marketing users to distinguish members who were Sent an invitation, Responded, Registered, Attended, or reached another configured state. Consistent status values are critical for accurate campaign response reporting. Opportunity Forecast Categories classify sales pipeline, Account Team Roles identify internal Account collaborators, and Case Priority indicates support urgency. Administrators should configure useful statuses for each Campaign type and identify which statuses count as responses so marketers can accurately measure engagement and follow-up requirements.

Q367. A company wants to track a customer’s purchased equipment serial number and installation date so support agents can see what equipment the customer owns. Which standard Salesforce object should be considered?

1. Campaign
   2. Asset
   3. Lead
   4. Quote

Correct Answer: 2. Asset

Explanation: Assets represent products or equipment owned or used by a customer after purchase. They can store information such as serial numbers, installation dates, status, and relationships to Accounts or Contacts, making them useful for support, maintenance, warranties, and renewal scenarios. Campaigns represent marketing initiatives, Leads represent prospective customers, and Quotes represent proposed sales terms before purchase. Administrators should evaluate how Products, Orders, Assets, Contracts, and Cases work together when the business needs to support customers based on the specific products they have already acquired.

Q368. A support organization wants agents to know how much time remains before a Case response milestone is violated. Which combination of Salesforce service features is MOST relevant?

1. Opportunity Teams and Forecasts
   2. Campaigns and Campaign Members
   3. Entitlements, entitlement processes, and milestones
   4. Price Books and Products

Correct Answer: 3. Entitlements, entitlement processes, and milestones

Explanation: Entitlements define the support a customer is eligible to receive, while entitlement processes and milestones can represent time-based service commitments such as first response or resolution deadlines. These features allow service organizations to track whether support obligations are being met and how much time remains before a milestone is violated. Opportunity Teams and Forecasts belong to sales, Campaigns belong to marketing, and Price Books manage product pricing. Administrators implementing formal support-level commitments should also ensure Business Hours and Holidays accurately represent the operating schedule used in milestone calculations.

Q369. An administrator wants a report that shows only Contacts whose Account belongs to the Technology industry. The report type already exposes Account fields. What is the simplest solution?

1. Add an Account Industry filter to the report
   2. Create a new role hierarchy
   3. Create a duplicate Contact field for Industry
   4. Change the Account organization-wide default

Correct Answer: 1. Add an Account Industry filter to the report

Explanation: If the report type already exposes fields from the related Account, the report can simply filter on Account Industry without copying that value into Contact. This keeps the data model cleaner and avoids maintaining duplicate information. A new role hierarchy would affect record access, while changing organization-wide defaults would alter sharing across the organization. Creating a duplicate Contact field would introduce unnecessary synchronization requirements. Administrators should first use relationships and reporting capabilities already available before adding fields solely to support a report that can be produced from existing related data.

Q370. A sales report should display the average Opportunity Amount for each sales representative. Which report configuration is required?

1. Create a Queue for Opportunities
   2. Group by Opportunity Owner and summarize Amount using Average
   3. Enable Email-to-Case
   4. Add a Campaign Hierarchy

Correct Answer: 3. Group by Opportunity Owner and summarize Amount using Average

Explanation: Salesforce reports can group records by fields such as Opportunity Owner and summarize numeric values using functions such as Sum, Average, Minimum, and Maximum. Grouping by Owner and applying Average to Amount produces the requested metric without adding a new field to Opportunity. Queues, Email-to-Case, and Campaign Hierarchies solve unrelated ownership, support, and marketing requirements. Administrators should select summary functions according to the business question because a total, average, maximum, or record count can communicate very different information about the same underlying sales data.

Q371. A dashboard is designed for regional managers. Each manager should see data according to that manager’s own Salesforce access instead of data from one fixed executive user. Which feature should be used?

1. Public Calendar
   2. Static dashboard running as the CEO
   3. Joined Report only
   4. Dynamic Dashboard

Correct Answer: 4. Dynamic Dashboard

Explanation: A Dynamic Dashboard uses the logged-in user’s security context, allowing multiple managers to view the same dashboard while seeing records they are individually authorized to access. This reduces the need to create separate dashboards for each region. A standard dashboard with a fixed executive running user would show data according to that user’s access instead. Joined Reports combine report blocks but do not create dynamic security behavior, while Public Calendars are unrelated. Administrators should also manage dashboard folders and understand applicable limits for Dynamic Dashboards within the organization’s Salesforce edition.

Q372. A data migration contains a mixture of records that already exist in Salesforce and records that are new. An External ID is available for matching. Which Data Loader operation should the administrator use?

1. Export
   2. Upsert
   3. Hard Delete
   4. Merge

Correct Answer: 2. Upsert

Explanation: Upsert combines update and insert behavior. When Data Loader finds an existing Salesforce record that matches the supplied External ID, it updates that record; when no match exists, it can insert a new record. This makes Upsert particularly useful for synchronization and migrations where the input contains both existing and new business records. Export only extracts data, Hard Delete permanently removes records, and Merge consolidates supported duplicates rather than processing an entire mixed dataset. Administrators should verify External ID uniqueness, field mappings, validation rules, and automation effects before executing a large upsert.

Q373. An administrator wants a report to identify Accounts that have Contacts but do not have any Opportunities. Which reporting capability is MOST useful?

1. Dashboard Subscription
   2. Bucket Field
   3. Cross Filters
   4. Compact Layout

Correct Answer: 3. Cross Filters

Explanation: Cross Filters allow reports to include or exclude records based on whether related records exist. In this scenario, the administrator can use relationship-based filters to identify Accounts with Contacts and without Opportunities, subject to the available report type and filter capabilities. Bucket Fields classify existing values, Dashboard Subscriptions distribute analytics notifications, and Compact Layouts affect record-page highlights. Cross Filters are valuable for business questions framed as “with” or “without” related records because they avoid creating permanent checkbox fields solely to support relationship-based reporting.

Q374. A company wants users to see whether a record’s approval request is currently Pending, Approved, or Rejected directly from the record page. What should the administrator consider?

1. Exposing appropriate approval information or status through the page and approval configuration
   2. Changing Organization-Wide Defaults
   3. Creating a Case Queue
   4. Enabling Territory Management

Correct Answer: 1. Exposing appropriate approval information or status through the page and approval configuration

Explanation: Approval-related information should be surfaced using the organization’s approval configuration and appropriate Lightning page components or status fields. This gives users visibility into whether a record is pending review, approved, rejected, or otherwise progressing through the defined approval lifecycle. Organization-Wide Defaults manage record sharing, Case Queues manage service ownership, and Territory Management manages sales coverage. Administrators should design the approval user experience so record locking, approvers, approval history, and status indicators are understandable without weakening the controls that protect records while they are under review.

Q375. A Flow processes records from a collection and needs to update every record after changing one field. What is the most scalable design?

1. Perform Update Records inside the loop for every item
   2. Launch a separate Flow interview for each field
   3. Save records one at a time using screens
   4. Modify records in the loop, add them to a collection, and perform one bulk update afterward

Correct Answer: 4. Modify records in the loop, add them to a collection, and perform one bulk update afterward

Explanation: Salesforce Flow should avoid repeated database operations inside a loop when the work can be performed in bulk. A scalable pattern is to iterate through the collection, make changes to each record in memory, add the modified records to another collection if necessary, and then perform one Update Records operation after the loop. This reduces database operations and helps the Flow behave efficiently with larger record volumes. Separate interviews or user screens would add unnecessary complexity. Bulk-aware design is an important practice for maintainable Salesforce automation.

Q376. A Flow should create a Task three days after an Opportunity enters the Proposal stage. Which capability is MOST appropriate?

1. Formula field
   2. Sharing Rule
   3. Auto Number
   4. Scheduled path in a record-triggered Flow

Correct Answer: 4. Scheduled path in a record-triggered Flow

Explanation: A Scheduled Path can delay actions within an appropriate record-triggered Flow until a defined time relative to the triggering record or a date/time value. The administrator can trigger the Flow when the Opportunity enters Proposal and schedule Task creation for three days later. A Formula field can calculate values but cannot schedule an action. Sharing Rules control access, and Auto Number fields generate identifiers. Administrators should understand how scheduled paths handle records that later change and should define entry conditions carefully to prevent duplicate delayed actions when the same stage is revisited.

Q377. An administrator is reviewing failed Flow interviews and wants to understand why automation stopped. Which design practice makes troubleshooting MOST effective?

1. Clear element names, fault paths, and meaningful error handling
   2. Removing all Decision elements
   3. Giving users Modify All Data
   4. Converting every Flow into a Screen Flow

Correct Answer: 2. Clear element names, fault paths, and meaningful error handling

Explanation: Maintainable Flow design includes descriptive element names, logical structure, selective entry criteria, and explicit fault paths for operations that can fail. These practices help administrators understand where an interview stopped and what data or action caused the problem. Meaningful notifications or error records can further improve support. Removing decisions would eliminate needed business logic, while granting broader permissions may hide rather than solve errors. Converting background automation to Screen Flows is also inappropriate. Good Flow troubleshooting begins with a design that communicates its own intent and failure behavior clearly.

Q378. An Agentforce agent can search company Knowledge content. A user without permission to view a restricted article asks a question whose answer is contained in that article. What should happen in a properly secured design?

1. The agent should reveal the article because AI access is separate
   2. The agent should ignore Salesforce security for Knowledge
   3. The agent should respect the user’s authorized data access and not expose restricted content
   4. The agent should automatically grant Knowledge access

Correct Answer: 3. The agent should respect the user’s authorized data access and not expose restricted content

Explanation: Agentforce should operate within the organization’s Salesforce security model. Users should not gain access to restricted Knowledge content merely by asking an AI agent instead of navigating to the article directly. Administrators should verify article visibility, data categories, user permissions, grounding configuration, and other security controls during testing. Instructions can help guide behavior but are not a substitute for actual access restrictions. Testing should include users with different permission levels so administrators can confirm that the agent provides useful information without exposing data outside each user’s authorized scope.

Q379. An Agentforce agent frequently receives questions that require a sensitive financial action which should remain human-controlled. What is the BEST design?

1. Provide an escalation or human handoff rather than exposing the sensitive action unnecessarily
   2. Give the agent the financial action but tell it not to use it
   3. Give every user financial administrator permissions
   4. Disable all topic instructions

Correct Answer: 1. Provide an escalation or human handoff rather than exposing the sensitive action unnecessarily

Explanation: Not every user request should be automated. When a task is sensitive, high-impact, or intentionally reserved for human decision-making, the Agentforce experience should provide an appropriate escalation or handoff rather than giving the agent unnecessary authority. This follows least-privilege principles and limits the consequences of incorrect interpretation or unexpected prompts. Behavioral instructions alone are not a sufficient security control if the agent already has permission to perform a sensitive action. Administrators should design agent scope according to business risk, required approvals, and organizational governance.

Q380. An organization is evaluating a new Salesforce administration feature introduced in a seasonal release. Which approach BEST supports a controlled rollout?

1. Enable it for everyone immediately
   2. Replace existing production functionality before testing
   3. Evaluate official guidance, dependencies, access controls, testing results, and business impact before deployment
   4. Skip documentation because seasonal features are automatically safe

Correct Answer: 3. Evaluate official guidance, dependencies, access controls, testing results, and business impact before deployment

Explanation: Salesforce seasonal releases can provide useful new capabilities, but administrators should treat them like any meaningful platform change. They should review official Salesforce documentation and maintenance material, identify prerequisites and licensing, evaluate permissions and security implications, test representative scenarios, understand interactions with existing automation, and plan user communication before deployment. Salesforce’s current Spring ’26 administrator maintenance content highlights features such as Setup with Agentforce, the Request Approval component, Screen Flow styling, Flow Logs, and new file-management permissions, illustrating why administrators must stay current while still following disciplined change management.