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

Q161. A Salesforce administrator wants to investigate whether a user successfully logged in yesterday and which IP address was used. Which feature should the administrator review?

1. Setup Audit Trail
   2. Field History Tracking
   3. Sharing Settings
   4. Login History

Correct Answer: 4. Login History

Explanation: Login History provides information about user authentication attempts, including timestamps, usernames, source IP addresses, login types, and whether attempts succeeded or failed. This makes it the appropriate place to investigate user login activity. Setup Audit Trail focuses on configuration changes made in Setup rather than authentication events. Field History Tracking records selected record-field changes, while Sharing Settings govern record access. Administrators troubleshooting suspicious or failed authentication should use Login History together with relevant user, profile, MFA, IP-range, and session settings to understand what occurred.

Q162. A company wants users to access Salesforce through a branded URL such as company.my.salesforce.com and needs a consistent domain identity for Lightning features. Which capability should the administrator configure?

1. Public Group
   2. My Domain
   3. Campaign Hierarchy
   4. Opportunity Team

Correct Answer: 2. My Domain

Explanation: My Domain gives a Salesforce organization a unique subdomain and is important for branding, authentication, Lightning functionality, and several platform features. Administrators can configure and deploy a My Domain so users access Salesforce through an organization-specific address. Public Groups are used primarily in sharing and access administration, Campaign Hierarchies organize marketing efforts, and Opportunity Teams support collaboration on deals. Because My Domain can affect login URLs and integrations, administrators should plan and communicate domain changes carefully before deployment.

Q163. A user has access to an Account record but cannot see a sensitive custom field on that Account. The field is visible on the page layout for other users. Which setting is MOST likely restricting the user?

1. Field-level security
   2. Role hierarchy
   3. Organization-Wide Defaults
   4. Account Team membership

Correct Answer: 1. Field-level security

Explanation: Field-level security controls whether a user can view or edit an individual field regardless of record access or page-layout placement. A user may have access to the Account record but still be unable to see a particular field if their profile or permission sets do not grant field visibility. Role hierarchy and Organization-Wide Defaults primarily govern record-level access, while Account Teams can grant collaboration and record access. Administrators should remember that field permissions are separate from record sharing and that page layouts should not be treated as the primary security boundary for sensitive fields.

Q164. A company uses several record types on a custom object. One user should automatically get the Retail record type when creating a record but should still be able to choose another permitted record type. Which setting should the administrator review?

1. Sharing Rule
   2. Queue Membership
   3. Default Record Type for the user’s profile or permission configuration
   4. Login Hours

Correct Answer: 3. Default Record Type for the user’s profile or permission configuration

Explanation: Users can have access to multiple record types while one is designated as the default for record creation. The administrator should review the record-type assignments and default record type associated with the user’s access configuration. The default determines which type is initially selected, while available record types determine what the user can choose. Sharing Rules govern record visibility, Queues support shared ownership, and Login Hours control authentication times. Record-type configuration is important because it also affects available page layouts, picklist values, and business processes.

Q165. An administrator wants users to enter a value only when a related checkbox is selected. Which declarative feature is BEST for enforcing this requirement when the record is saved?

1. Validation Rule
   2. Sharing Rule
   3. Compact Layout
   4. Dashboard Filter

Correct Answer: 1. Validation Rule

Explanation: Validation Rules evaluate record data during save and can prevent a record from being saved when business requirements are not satisfied. A formula can check whether the checkbox is selected and whether the dependent field is blank, then display an error message instructing the user to provide the required value. Sharing Rules manage record access, Compact Layouts control highlighted fields, and Dashboard Filters affect analytics. Validation Rules are appropriate for enforcing conditional data quality requirements across users and interfaces where the rule applies.

Q166. A company wants to store a customer’s signed agreement and associate the same document with both the Account and a related Opportunity. Which Salesforce feature is MOST suitable?

1. Case Comment
   2. Campaign Member
   3. Public Calendar
   4. Salesforce Files

Correct Answer: 4. Salesforce Files

Explanation: Salesforce Files allows one file to be shared and associated with multiple Salesforce records, making it suitable for documents such as signed agreements, proposals, or supporting materials that relate to more than one business record. Users can collaborate around the same managed file rather than uploading separate uncontrolled copies. Case Comments are service notes, Campaign Members represent people associated with marketing campaigns, and Public Calendars manage shared events. File access should still be governed carefully because sensitive customer documents may require restricted visibility.

Q167. A salesperson wants to create a follow-up Task quickly from several different record types using the same action. Which Salesforce capability should the administrator consider?

1. Record Type
   2. Global Action
   3. Sharing Rule
   4. Case Queue

Correct Answer: 2. Global Action

Explanation: Global Actions allow users to perform certain actions from multiple places in Salesforce rather than only from a specific record context. An administrator can configure actions for activities or record creation and expose them in appropriate global action menus. This can improve productivity for actions users perform frequently across the application. Record Types influence processes and layouts, Sharing Rules grant record access, and Case Queues support service ownership. Administrators should choose between global and object-specific actions based on whether the action requires a particular parent-record context.

Q168. A custom object has a Status picklist with values New, Active, and Retired. The administrator wants to prevent new records from using Retired while preserving the value on historical records. What should the administrator do?

1. Delete every record containing Retired
   2. Convert the field to text
   3. Deactivate the Retired picklist value
   4. Remove the field from all layouts

Correct Answer: 3. Deactivate the Retired picklist value

Explanation: Deactivating a picklist value prevents it from being selected for new or updated records while generally preserving the value on existing historical records that already use it. This is safer than deleting or replacing business data simply because a value is no longer valid for future use. Administrators may also need to review automation, reports, and integrations that reference the value. Converting the field to text would remove the controlled-value benefits of a picklist, and removing it from layouts would not prevent other interfaces or automation from using it.

Q169. A company wants to track recurring revenue after an Opportunity closes and represent the customer’s installed products. Which standard Salesforce object should the administrator consider?

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

Correct Answer: 4. Asset

Explanation: Assets can represent products or services that a customer owns or has purchased, helping organizations track installed products after a sale. They can be useful for service, renewal, warranty, or customer-product history scenarios. Opportunities represent prospective or completed sales pipeline activity, while Campaigns support marketing, Cases support customer service, and Leads represent prospects. The exact design depends on the company’s sales and service processes, but Assets are the standard concept to consider when the business needs to represent customer-owned products after purchase.

Q170. A salesperson needs to indicate that one Contact is the primary decision maker for an Opportunity. Which Salesforce feature is MOST appropriate?

1. Opportunity Contact Role
   2. Account Team
   3. Case Contact
   4. Campaign Member

Correct Answer: 1. Opportunity Contact Role

Explanation: Opportunity Contact Roles connect Contacts to an Opportunity and identify each person’s role in the sales process, such as Decision Maker, Evaluator, or Technical Buyer. This helps sales teams understand the stakeholders involved in a deal and supports more complete Opportunity data. Account Teams define user collaboration around an Account rather than customer Contact roles in a specific deal. Campaign Members represent marketing participation, while Cases track customer support. Opportunity Contact Roles are therefore the appropriate feature for documenting who influences or decides a particular sales opportunity.

Q171. A customer service manager wants users to find Cases that were created by email and remain open for more than five days. Which feature is BEST suited for an operational working list?

1. Dashboard only
   2. Campaign Hierarchy
   3. Filtered Case List View
   4. Price Book

Correct Answer: 3. Filtered Case List View

Explanation: A filtered List View is appropriate when service users need a recurring operational set of records matching defined criteria, such as Case Origin = Email, Status not Closed, and an age-related condition where supported. List views provide a convenient working interface for reviewing and acting on records without requiring a formal report each time. Dashboards are better for summarized analytics, Campaign Hierarchies organize marketing records, and Price Books handle product pricing. Administrators should use reports for deeper analysis and list views for day-to-day record work.

Q172. A support organization wants some Knowledge articles available internally while others can be exposed to customers. What should the administrator manage?

1. Opportunity Stages
   2. Article visibility and Knowledge audience settings
   3. Forecast Categories
   4. Lead Queues

Correct Answer: 2. Article visibility and Knowledge audience settings

Explanation: Salesforce Knowledge supports controlling where articles can be used or exposed according to the organization’s Knowledge configuration and audience needs. Administrators should ensure articles intended only for employees are not inadvertently exposed externally, while customer-facing articles are appropriately published and visible. Data Categories and other Knowledge permissions may also contribute to access design. Opportunity Stages and Forecast Categories belong to sales management, and Lead Queues support sales record ownership. Knowledge governance should address publication status, audience, content quality, and user permissions.

Q173. A report should show Opportunities whose Amount is greater than the average Opportunity Amount for a particular management analysis. The administrator wants to calculate values within the report without adding a new field to Opportunity. Which feature should be considered first?

1. Report formula capability appropriate to the required calculation
   2. Role Hierarchy
   3. Case Assignment Rule
   4. Compact Layout

Correct Answer: 1. Report formula capability appropriate to the required calculation

Explanation: Salesforce report formulas can provide derived calculations without adding fields to the underlying object. Depending on the exact requirement, the administrator may use row-level or summary formulas and report grouping to create the needed comparison. The formula capabilities and report format should be evaluated against the business question. Role Hierarchy affects record visibility, Case Assignment Rules route Cases, and Compact Layouts display highlighted fields. Administrators should avoid creating permanent object fields when a calculation is needed only for reporting and can be handled cleanly within the report.

Q174. A dashboard contains several components based on different source reports. A user can open the dashboard but cannot open one of the source reports because its folder is restricted. What should the administrator review?

1. Lead Conversion settings
   2. Opportunity Contact Roles
   3. Data Import Wizard
   4. Report and dashboard folder sharing**

Correct Answer: 4. Report and dashboard folder sharing

Explanation: Salesforce reports and dashboards are stored in folders with their own sharing settings. A user can sometimes encounter differences between access to a dashboard and access to the underlying reports depending on folder permissions and the dashboard configuration. Administrators should review both dashboard and report folder sharing to ensure users have the intended analytics access. Underlying record-level security still controls which Salesforce records users can see according to the dashboard’s running context. Sales and data import features are unrelated to analytics folder access.

Q175. An administrator wants a Flow to update a collection of 200 records efficiently. Which design is BEST?

1. Perform one Update Records operation for each item inside a loop
   2. Build a collection of changed records and update the collection in one operation after the loop
   3. Create 200 separate Flows
   4. Use Chatter posts instead of record updates

Correct Answer: 2. Build a collection of changed records and update the collection in one operation after the loop

Explanation: In Flow, performing database operations repeatedly inside a loop can be inefficient and may contribute to platform governor limits. A better pattern is often to loop through records, modify values in memory, add records to a collection, and perform one bulk Update Records operation after the loop. This mirrors bulk-processing best practices on the Salesforce platform. The exact design depends on the business requirement, but minimizing repeated database actions helps improve scalability. Creating separate Flows for each record would be unmanageable and unnecessary.

Q176. A Flow needs to determine whether a collection contains any records before processing it. Which design should the administrator use?

1. An appropriate Decision element checking the collection or related condition
   2. Opportunity Split
   3. Sharing Rule
   4. Dashboard Subscription

Correct Answer: 3. An appropriate Decision element checking the collection or related condition

Explanation: A Decision element allows a Flow to branch based on whether expected records or conditions are present. The administrator can use an appropriate collection or record-existence condition to determine whether subsequent processing should continue. This prevents unnecessary loop or record operations when the collection is empty. Opportunity Splits are a sales feature, Sharing Rules grant record access, and Dashboard Subscriptions distribute analytics updates. Clear decision logic is important in Flow because it makes the automation easier to read, test, and maintain.

Q177. A company creates a custom permission named Can_Approve_Exception and wants a Flow to check whether the running user has that permission. What is the PRIMARY benefit of using a custom permission?

1. It provides a reusable way to represent a business authorization without hard-coding individual users
   2. It automatically grants access to all Salesforce records
   3. It replaces Organization-Wide Defaults
   4. It creates a new user license

Correct Answer: 1. It provides a reusable way to represent a business authorization without hard-coding individual users

Explanation: Custom permissions can represent specific business capabilities and can be assigned through profiles or permission sets. Automation, validation logic, and other supported platform features can then check the permission instead of referencing particular usernames or profiles. This improves maintainability because administrators can change who receives the capability without rewriting business logic. Custom permissions do not automatically grant broad record access and do not replace Salesforce’s sharing model or user licenses. They are useful for decoupling business authorization logic from organizational structures that may change over time.

Q178. An Agentforce agent should hand a conversation to a human when a customer’s request is outside the approved topic scope. Which design principle is MOST appropriate?

1. Let the agent invent a new unsupported process
   2. Define an escalation or handoff path for unsupported requests
   3. Grant the agent additional permissions automatically
   4. Ignore the customer request

Correct Answer: 2. Define an escalation or handoff path for unsupported requests

Explanation: Agentforce agents should have a clearly defined scope and should handle unsupported or sensitive requests safely. A handoff or escalation path allows the user to receive assistance from an appropriate human or another approved process rather than encouraging the agent to improvise outside its capabilities. The administrator should test out-of-scope scenarios and ensure the agent does not gain unnecessary permissions simply because a user asks for unsupported actions. Agent governance should combine clear topics and instructions with controlled actions, Salesforce security, and appropriate escalation behavior.

Q179. An administrator changes an Agentforce topic instruction. What should happen before the revised agent behavior is made widely available?

1. Activate it immediately because only text changed
   2. Disable Agentforce security testing
   3. Retest representative conversations and actions to confirm the change did not create unwanted behavior
   4. Give the agent System Administrator permissions temporarily

Correct Answer: 3. Retest representative conversations and actions to confirm the change did not create unwanted behavior

Explanation: Changes to Agentforce instructions can alter how an agent interprets requests, selects actions, or responds to users even when underlying Salesforce configuration is unchanged. Administrators should therefore retest important scenarios, including edge cases and security-sensitive interactions, before broad deployment. Testing should confirm that record access, action permissions, topic scope, and escalation still behave as intended. Treating instruction changes as harmless text edits can create unexpected behavior. AI agent configuration should follow disciplined change and testing practices similar to other consequential automation.

Q180. A company wants an Agentforce agent to summarize Case information but not expose a restricted field that the user cannot view directly in Salesforce. What should the administrator ensure?

1. The agent’s access respects Salesforce field-level security and relevant data permissions
   2. The restricted field is placed on every page layout
   3. The user receives Modify All Data
   4. The agent is instructed to ignore Salesforce permissions

Correct Answer: 1. The agent’s access respects Salesforce field-level security and relevant data permissions

Explanation: Agentforce should operate within Salesforce’s established data-security model. A user should not gain access to a restricted field merely because an agent summarizes the record. Administrators should verify object permissions, field-level security, record sharing, agent actions, and any additional grounding or data-access configuration. Prompt instructions alone are not an appropriate substitute for actual access controls. This principle helps ensure AI functionality enhances productivity without creating a new pathway around Salesforce security. Testing should include users with different permission levels to confirm restricted information remains protected.