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

Q181. A Salesforce organization defines a range of trusted corporate IP addresses. What is the primary effect when a user logs in from an address inside that trusted range?

1. The user automatically receives Modify All Data
   2. Salesforce can treat the login as coming from a trusted network and may not require an additional identity verification challenge based solely on the IP
   3. The user can bypass profile login hours
   4. Organization-wide defaults become Public Read/Write

Correct Answer: 2. Salesforce can treat the login as coming from a trusted network and may not require an additional identity verification challenge based solely on the IP

Explanation: Trusted IP ranges identify networks that Salesforce recognizes as trusted for login purposes. A login from inside the trusted range can reduce certain identity-verification challenges that might otherwise occur when a user authenticates from an unfamiliar network. Trusted IP ranges do not grant data permissions, override profile login hours, or alter organization-wide defaults. Administrators should also distinguish organization-level trusted IP ranges from profile Login IP Ranges: profile ranges can restrict where users are permitted to log in, whereas trusted ranges primarily influence login verification behavior.

Q182. An administrator wants users to see a Related List for Contacts on the Account record page, but the list does not appear even though users can access Contact records. What should the administrator review FIRST?

1. Opportunity Forecast Categories
   2. Lead Assignment Rules
   3. Login History
   4. The Account page layout and Lightning record page configuration**

Correct Answer: 4. The Account page layout and Lightning record page configuration

Explanation: Related lists displayed on records are influenced by the assigned page layout and, in Lightning Experience, the components placed on the Lightning record page. If users already have access to Contacts but the related list is not visible, the administrator should verify that the Contacts related list is included on the relevant Account layout and that the Lightning page contains the appropriate related-list component. Forecast categories, Lead Assignment Rules, and Login History do not control related-list presentation. Administrators should separate user-interface configuration from permissions because a hidden component does not necessarily indicate missing record access.

Q183. A custom object needs a field containing an identifier from an external ERP system. The identifier must not be duplicated across records and will be used by integrations to locate records. Which configuration is BEST?

1. Create a custom field marked as External ID and Unique
   2. Create a Long Text Area field
   3. Use a Roll-Up Summary field
   4. Store the value in Chatter

Correct Answer: 1. Create a custom field marked as External ID and Unique

Explanation: An External ID field is designed to store identifiers originating outside Salesforce and can be used by integrations and data tools to match records during operations such as upsert. Marking the field Unique additionally prevents duplicate external identifiers from being saved. This combination is useful when the external system’s key should map to exactly one Salesforce record. Long Text Area fields are not designed for record matching, Roll-Up Summary fields aggregate related records, and Chatter is collaboration content rather than authoritative integration data. Administrators should select a field type compatible with the external identifier.

Q184. A company wants users to be unable to select a Close Date earlier than today when creating a new Opportunity, but existing historical Opportunities should remain unchanged. Which tool is MOST appropriate?

1. Sharing Rule
   2. Compact Layout
   3. Validation Rule that applies to new records
   4. Public Group

Correct Answer: 3. Validation Rule that applies to new records

Explanation: A Validation Rule can enforce conditions at save time and can include logic such as ISNEW() together with a comparison between Close Date and the current date. This allows the administrator to prevent invalid values on newly created Opportunities without forcing changes to historical records. Sharing Rules control record access, Compact Layouts control highlighted fields, and Public Groups are used for sharing and other access assignments. Validation Rules are especially useful when a business requirement must be enforced consistently whenever users or supported interfaces attempt to save a record.

Q185. A company wants a manager to be automatically added to the Account Team whenever a sales representative creates an Account. Which Salesforce feature should the administrator consider for a reusable team configuration?

1. Opportunity Contact Roles
   2. Case Queue
   3. Campaign Hierarchy
   4. Default Account Teams**

Correct Answer: 4. Default Account Teams

Explanation: Default Account Teams can help users establish a predefined group of collaborators who commonly work with their Accounts. When enabled and configured appropriately, users can add their default team to Accounts instead of selecting the same team members repeatedly. This is useful when a salesperson regularly works with the same manager, sales engineer, or service representative. Opportunity Contact Roles identify customer Contacts involved in Opportunities, Case Queues manage service ownership, and Campaign Hierarchies organize marketing programs. Account Teams concern internal Salesforce users collaborating around customer Account records.

Q186. An administrator wants Opportunity Stage to default to “Prospecting” when a new Opportunity is created for a particular process. Which configuration should the administrator review?

1. Dashboard Filter
   2. Opportunity Stage and Sales Process configuration
   3. Case Auto-Response Rule
   4. Knowledge Data Categories

Correct Answer: 2. Opportunity Stage and Sales Process configuration

Explanation: Opportunity stages are tied to sales processes and define the progression of sales records through the pipeline. Administrators should review the Stage values, sales process, and relevant record-type configuration when users need a specific stage experience. Page layouts and default field behavior may also affect the user experience depending on the exact requirement. Dashboard Filters, Case Auto-Response Rules, and Knowledge Data Categories belong to unrelated analytics, service, and knowledge-management functions. Sales processes should accurately represent the organization’s selling methodology because stages also influence probability, reporting, and forecasting behavior.

Q187. A sales manager wants the Probability field on Opportunities to change automatically when representatives select different Stage values. Which standard Salesforce behavior supports this?

1. Manual Sharing
   2. Campaign Influence
   3. Stage-to-probability mapping
   4. Queue membership

Correct Answer: 3. Stage-to-probability mapping

Explanation: Opportunity Stage values can be associated with default probabilities. When users change the stage, Salesforce can update the Probability field according to the configured mapping, providing a consistent pipeline estimate. Users may still be permitted to adjust probability depending on configuration and business practice, but the stage provides a standard default. Campaign Influence concerns marketing attribution, Manual Sharing provides record access, and queues provide shared ownership for supported objects. Administrators should ensure stage names, probabilities, forecast categories, and sales processes align with how the organization actually manages its pipeline.

Q188. A marketing team wants to calculate basic return on investment for a Campaign by comparing campaign costs with revenue associated with campaign Opportunities. Which records and fields should be maintained accurately?

1. Campaign cost information and related Opportunity revenue
   2. Only Chatter posts
   3. Only Lead Owner values
   4. Case escalation history

Correct Answer: 1. Campaign cost information and related Opportunity revenue

Explanation: Campaign performance analysis depends on accurate Campaign data and appropriate relationships to sales outcomes. Maintaining fields such as campaign cost, responses, and influenced or associated Opportunity revenue allows marketers to evaluate effectiveness and return on investment. The exact metrics depend on the organization’s Campaign Influence and reporting configuration. Chatter posts, Lead ownership alone, and Case escalation history do not provide a meaningful campaign ROI calculation. Administrators should ensure the marketing team uses Campaigns consistently and understands how Leads, Contacts, Campaign Members, and Opportunities contribute to campaign analysis.

Q189. A service agent wants to add internal troubleshooting notes to a Case without sending those notes to the customer. Which approach is MOST appropriate?

1. Change the Case Owner
   2. Use an internal Case collaboration or comment mechanism configured for internal visibility
   3. Convert the Case to a Lead
   4. Add the notes to the customer’s email address field

Correct Answer: 2. Use an internal Case collaboration or comment mechanism configured for internal visibility

Explanation: Support agents often need to document diagnostic details that should remain available to internal staff but not be sent directly to the customer. Salesforce service functionality supports internal collaboration and record notes through Case-related features and feeds, depending on the implementation. Administrators should ensure visibility is configured appropriately so internal information does not become customer-facing unintentionally. Changing ownership does not store troubleshooting notes, and converting a Case to a Lead is not a standard service workflow. Sensitive information should also be handled according to organizational data policies.

Q190. A Knowledge article contains outdated troubleshooting instructions. The support manager wants users to stop relying on it while preserving article history. What should be done?

1. Remove or archive the outdated article from active publication according to the Knowledge lifecycle
   2. Delete every Case that referenced the article
   3. Convert the article into a Campaign
   4. Change Account organization-wide defaults

Correct Answer: 1. Remove or archive the outdated article from active publication according to the Knowledge lifecycle

Explanation: Knowledge content should be governed through a publication lifecycle so outdated information is no longer presented as current guidance while historical records can be retained when appropriate. Depending on the Knowledge configuration, the organization can unpublish, archive, revise, or replace the article. Deleting related Cases would destroy service history and does not solve the knowledge-quality problem. Campaigns and Account sharing are unrelated. Administrators should ensure article owners periodically review important content so support agents and customers receive accurate, approved information rather than obsolete troubleshooting instructions.

Q191. An administrator wants a report to show only Accounts that have at least one related Contact whose Department equals Finance. Which report capability should be used?

1. Dashboard subscription
   2. Bucket field
   3. Validation Rule
   4. Cross filter with an appropriate subfilter**

Correct Answer: 4. Cross filter with an appropriate subfilter

Explanation: Cross filters can return records based on whether related records exist, and subfilters can further restrict those related records. An Account report can therefore use a cross filter such as Accounts with Contacts and a Contact subfilter where Department equals Finance. Bucket fields categorize values within a report but do not filter based on related-record existence. Dashboard subscriptions distribute dashboard updates, and Validation Rules enforce record data at save time. Cross filters are powerful when report requirements involve “with” or “without” relationships between objects.

Q192. A report groups Opportunity revenue by Region. Management wants to show each Region’s revenue as a percentage of the overall total. Which report feature is MOST appropriate?

1. Sharing Rule
   2. Auto Number
   3. Summary Formula
   4. Login IP Range

Correct Answer: 3. Summary Formula

Explanation: Summary Formulas calculate values using grouped or grand-total report results. They are well suited to calculations such as each Region’s revenue divided by the report’s total revenue. This provides analysis without creating a permanent field on Opportunity. Row-Level Formulas instead calculate values for individual records. Sharing Rules control data access, Auto Number fields generate identifiers, and Login IP Ranges control where users can authenticate. Administrators should select the reporting formula type according to whether the calculation depends on row-level values or aggregate report summaries.

Q193. An administrator wants to know whether a bulk data update changed a critical Account field and who made the change. Field History Tracking had already been enabled for the field. Where should the administrator look?

1. The Account field history related information or a corresponding history report
   2. Campaign Hierarchy
   3. Login Hours
   4. Price Book Entries

Correct Answer: 1. The Account field history related information or a corresponding history report

Explanation: Field History Tracking stores changes to selected fields and can provide information such as the prior value, new value, user, and time of change where supported. If history tracking was already enabled before the bulk update, the administrator can review the history related list or report on the appropriate history object. Setup Audit Trail focuses on Setup configuration rather than ordinary record-value changes. Campaigns, Login Hours, and Price Books do not provide record field-change history. Administrators should enable tracking before changes occur because it is not retroactive.

Q194. An administrator needs to import data into Salesforce but first wants to ensure the external CSV values match valid Salesforce picklist values. What is the BEST approach?

1. Import first and correct every failure manually afterward
   2. Validate and clean the source data against Salesforce field requirements before import
   3. Disable all picklists
   4. Convert every picklist to unrestricted text

Correct Answer: 3. Validate and clean the source data against Salesforce field requirements before import

Explanation: Data preparation before import reduces errors, improves data quality, and makes reconciliation easier. Administrators should review field types, required values, picklists, date formats, identifiers, duplicate handling, and ownership before loading data. Import tools can report failures, but relying on errors as the primary data-cleaning strategy increases effort and risk. Disabling controlled fields can weaken business processes and reporting. A well-managed migration typically includes source profiling, cleanup, backup, test imports, mapping validation, production loading, and post-import reconciliation.

Q195. A company wants a Flow to create a follow-up Task only if no open Task of the same type already exists for the Account. What should the Flow do FIRST?

1. Create the Task and then search for duplicates
   2. Delete all existing Tasks
   3. Use a Screen element
   4. Query for a matching open Task and use a Decision before creating a new one**

Correct Answer: 4. Query for a matching open Task and use a Decision before creating a new one

Explanation: The Flow should determine existing state before creating a potentially duplicate record. A Get Records element can search for an open matching Task, and a Decision can branch based on whether one was found. Only when no matching record exists should the Flow create the new Task. This design makes the automation more idempotent and avoids repeated follow-up tasks when the triggering process runs more than once. Creating first and checking later introduces unnecessary duplicates, while deleting all existing tasks could remove legitimate work.

Q196. A scheduled-triggered Flow processes many records every night. The administrator wants to reduce unnecessary processing. What is the BEST design improvement?

1. Define selective start criteria so only relevant records enter the Flow
   2. Query every record and immediately exit most interviews
   3. Duplicate the Flow for each user
   4. Replace filters with Chatter posts

Correct Answer: 1. Define selective start criteria so only relevant records enter the Flow

Explanation: Scheduled automation is more efficient when entry criteria restrict processing to records that actually require action. This reduces the number of Flow interviews and unnecessary database operations. The administrator should define criteria aligned with the business requirement, then use additional decisions only when more complex branching is necessary. Processing every record merely to exit immediately wastes platform resources and can make troubleshooting harder. Efficient declarative automation is especially important in large Salesforce organizations where nightly processes may otherwise touch hundreds of thousands of records.

Q197. A Flow must call reusable logic that is maintained separately and accepts input variables. Which Flow element should be used?

1. Assignment
   2. Subflow
   3. Loop
   4. Screen

Correct Answer: 2. Subflow

Explanation: A Subflow element invokes another eligible Flow and can pass input and output variables between the parent and reusable automation. This helps administrators centralize common business logic instead of copying the same elements into multiple Flows. Changes to the shared logic can then be maintained in one place, subject to appropriate testing and version management. Assignment elements set variable values, Loops iterate through collections, and Screens provide user interaction. Subflows are particularly useful for modular Flow architecture when several processes require the same actions or calculations.

Q198. An Agentforce agent is intended to assist employees with HR policy questions. It begins answering unrelated technical-support questions. What should the administrator review FIRST?

1. Opportunity Stage probabilities
   2. Dashboard folders
   3. Topic scope, classification, and instructions for the agent
   4. Price Book entries

Correct Answer: 3. Topic scope, classification, and instructions for the agent

Explanation: Agentforce topics help define the categories of work an agent is intended to handle. If an HR agent begins answering unrelated technical-support questions, the administrator should review topic descriptions, scope, instructions, routing, and any configured fallback behavior. The agent should clearly distinguish supported requests from unsupported ones and escalate or redirect when appropriate. Salesforce security and action permissions should also be reviewed if the agent can perform operations. Sales stages, dashboard folders, and Price Books do not govern conversational topic classification.

Q199. An Agentforce action can update customer records. What should the administrator verify before making that action available to the agent?

1. Only that the action has a short name
   2. That every employee can run the action
   3. Only that the agent can describe the action
   4. That the action is necessary, appropriately permissioned, tested, and limited to the intended business use**

Correct Answer: 4. That the action is necessary, appropriately permissioned, tested, and limited to the intended business use

Explanation: Agent actions can produce real Salesforce changes, so administrators should apply least privilege and verify that each action is necessary for the agent’s approved purpose. They should understand which records and fields can be affected, how Salesforce permissions apply, what inputs are accepted, and how unsupported or high-impact requests are handled. Testing should include normal and edge cases before broad activation. An action’s name or description does not provide a sufficient security boundary. Unnecessary write capabilities increase the impact of configuration mistakes or unexpected agent behavior.

Q200. A company wants to launch an Agentforce agent first to a limited internal audience before expanding availability. What is the PRIMARY benefit of this approach?

1. It allows the agent to bypass Salesforce security temporarily
   2. It eliminates the need for testing
   3. It removes the need for monitoring
   4. It limits initial impact while administrators observe behavior and refine configuration**

Correct Answer: 2. It limits initial impact while administrators observe behavior and refine configuration

Explanation: A limited rollout reduces the blast radius of unexpected responses, topic-classification problems, permission issues, or action behavior. Administrators can observe how the agent performs with real users, gather feedback, review logs, and refine topics, instructions, actions, and escalation before expanding access. The agent should still be fully tested before the pilot and must respect Salesforce security throughout. Limited release complements rather than replaces testing and monitoring. This staged approach is particularly useful with AI features because real user requests can expose scenarios that administrators did not anticipate during initial configuration.