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

Q141. A Salesforce administrator suspects that a user’s account has been compromised and wants to prevent login immediately without deactivating the user or releasing the license. What should the administrator do?

1. Delete the user
   2. Remove the user’s role
   3. Freeze the user
   4. Change the user’s record ownership

Correct Answer: 3. Freeze the user

Explanation: Freezing a Salesforce user prevents that user from logging in while leaving the user record active. This is useful when access needs to be stopped immediately but the administrator is not yet ready to deactivate the account, perhaps because background ownership, integrations, or other dependencies still need investigation. Deactivating a user also prevents login and releases the license, but freezing is useful as an immediate temporary measure. Removing a role changes record-access behavior rather than authentication. Record ownership likewise does not prevent the user from signing in. Administrators should still investigate the incident and follow normal offboarding or security procedures afterward.

Q142. A company wants Salesforce users to change their passwords at least every 90 days and requires a minimum password length. Which configuration should the administrator review?

1. Password Policies
   2. Organization-Wide Defaults
   3. Sharing Rules
   4. Record Types

Correct Answer: 1. Password Policies

Explanation: Password Policies contain organization-level controls for password requirements such as minimum password length, password history, expiration periods, lockout behavior, and related authentication settings. They help administrators apply consistent password requirements across Salesforce users. Organization-Wide Defaults establish baseline record-level visibility, while Sharing Rules extend record access beyond that baseline. Record Types control business processes, layouts, and picklist values. Password policy configuration belongs to the authentication and organization-security layer of Salesforce administration and should be coordinated with other controls such as MFA, session settings, login hours, and approved IP restrictions.

Q143. A user needs the ability to view every Account record regardless of sharing rules, but the administrator does not want to give access to all records across every Salesforce object. Which permission is MOST appropriate?

1. View All Data
   2. Modify All Data
   3. Manage Users
   4. View All on the Account object

Correct Answer: 4. View All on the Account object

Explanation: View All on a specific object allows a user to view all records of that object regardless of normal record-sharing restrictions. It is narrower than View All Data, which provides broad visibility across Salesforce records on many objects. Modify All Data is far more powerful because it provides broad administrative data access and modification capability. Manage Users relates to user administration rather than Account record visibility. Administrators should assign the narrowest permission that satisfies the business requirement. Object-specific View All can be appropriate for auditors, managers, or specialists who require comprehensive visibility into one object without broad access elsewhere.

Q144. An organization wants users to understand how subsidiary Accounts relate to a parent corporate Account. Which Salesforce feature BEST supports this requirement?

1. Campaign Hierarchy
   2. Account Hierarchy
   3. Case Team
   4. Opportunity Split

Correct Answer: 2. Account Hierarchy

Explanation: Account Hierarchy uses the Parent Account relationship to show how related business Accounts are organized. This is helpful for companies that sell to enterprises containing headquarters, subsidiaries, branches, or regional entities. Users can navigate the relationships while retaining separate Account records for each business entity. Campaign Hierarchies organize marketing initiatives rather than customer organizations. Case Teams support service collaboration, while Opportunity Splits divide sales credit among participants. Administrators should use Account hierarchy when the business needs to model corporate relationships without combining separate legal or operational customer entities into one record.

Q145. An administrator wants to convert an existing lookup relationship on a custom child object into a master-detail relationship. Which condition must generally be addressed first?

1. Every existing child record must have a value in the relationship field
   2. The child object must contain no custom fields
   3. The parent object must have Public Read/Write sharing
   4. All users must have Modify All Data

Correct Answer: 1. Every existing child record must have a value in the relationship field

Explanation: A master-detail relationship requires each detail record to be associated with a master record. Therefore, when converting a lookup relationship to master-detail, existing child records generally must already contain valid parent values. Master-detail relationships also affect ownership, sharing, deletion behavior, and availability of roll-up summary fields, so administrators should evaluate the broader implications before conversion. The child object can still contain custom fields, and the parent’s organization-wide default does not need to be Public Read/Write. Modify All Data is unrelated to the structural requirement for every detail record to have a master.

Q146. A custom Detail record is related to a Master record through a master-detail relationship. What happens by default when the Master record is deleted?

1. The Detail records automatically become independent
   2. The Detail records remain but lose ownership
   3. Salesforce converts the relationship to lookup
   4. The related Detail records are deleted through cascade deletion

Correct Answer: 4. The related Detail records are deleted through cascade deletion

Explanation: In a master-detail relationship, the detail record is strongly dependent on its master. When the master is deleted, related detail records are normally deleted as part of cascade deletion. The detail also derives certain ownership and sharing behavior from the master. This is very different from a typical lookup relationship, where child records can often exist independently. Administrators should consider this lifecycle dependency carefully before choosing master-detail. It can be beneficial when detail records have no business meaning without their parent, but inappropriate when child records must survive deletion or reassignment of the related parent.

Q147. An administrator creates a custom Lead field and wants its value transferred automatically to a custom Contact field when the Lead is converted. What should the administrator configure?

1. Lead field mapping
   2. Opportunity Splits
   3. Campaign Influence
   4. Case Assignment Rules

Correct Answer: 2. Lead field mapping

Explanation: Lead field mapping controls how custom Lead field values are transferred to corresponding custom fields on Account, Contact, or Opportunity records during Lead conversion. The destination field must be compatible with the source field according to Salesforce requirements. This allows organizations to preserve important prospect information when the Lead moves into the customer and sales pipeline process. Opportunity Splits allocate sales credit, Campaign Influence connects marketing activities with Opportunities, and Case Assignment Rules route service Cases. Administrators should configure and test custom Lead mappings before users begin converting records to avoid losing important business data.

Q148. Marketing managers want to understand which Campaigns contributed to an Opportunity and potentially influenced its revenue. Which Salesforce feature should they use?

1. Account Teams
   2. Case Escalation Rules
   3. Campaign Influence
   4. Support Processes

Correct Answer: 3. Campaign Influence

Explanation: Campaign Influence allows Salesforce organizations to associate marketing Campaigns with Opportunities and analyze which campaigns contributed to sales pipeline or revenue. This helps marketing and sales teams evaluate campaign effectiveness beyond simple response counts. The exact attribution model and configuration can vary depending on Salesforce capabilities and organizational processes. Account Teams support collaboration on customer Accounts, while Case Escalation Rules and Support Processes belong to service management. Campaign Influence is therefore relevant when the organization wants to connect marketing activity with downstream Opportunity outcomes and analyze marketing’s contribution to sales.

Q149. A global company wants to organize sales representatives into geographic sales territories that do not exactly match the management role hierarchy. Which feature should the administrator consider?

1. Enterprise Territory Management
   2. Case Queues
   3. Chatter Groups
   4. Support Processes

Correct Answer: 1. Enterprise Territory Management

Explanation: Enterprise Territory Management allows organizations to structure Account and Opportunity coverage around sales territories rather than relying exclusively on the role hierarchy. Territories can reflect geography, market segment, product line, or another sales-coverage model and can differ from the company’s management reporting structure. This is useful when users participate in multiple sales territories or when coverage changes frequently. Case Queues and Support Processes apply to customer service, while Chatter Groups support collaboration. Territory management should be planned carefully because assignment rules, forecasting, access, and sales processes may depend on the territory design.

Q150. A company wants sales users to identify which competitor is involved in an Opportunity. Where should this information be maintained?

1. Case Teams
   2. Opportunity Competitors
   3. Campaign Members
   4. Public Groups

Correct Answer: 4. Opportunity Competitors

Explanation: Opportunity Competitors allow sales teams to identify competing companies associated with a particular Opportunity. This can help sales management analyze competitive trends and give representatives context about who they are selling against. Case Teams support support-case collaboration, Campaign Members connect Leads or Contacts with Campaigns, and Public Groups are commonly used for sharing and permissions administration. Competitive information belongs in the sales process around the Opportunity rather than in unrelated marketing or security configuration. Administrators should ensure users understand where to maintain such data so reporting remains consistent.

Q151. A support organization wants a custom Case Status value to be treated as a closed status. Which configuration should the administrator review?

1. Case Status picklist configuration and the Closed designation
   2. Lead Status mapping
   3. Opportunity Forecast Category
   4. Campaign Member Status

Correct Answer: 2. Case Status picklist configuration and the Closed designation

Explanation: Case Status values can be configured so specific statuses represent a closed Case. This affects how Salesforce treats the Case in service workflows and reporting. Administrators should ensure the organization’s support process includes the correct status values and that closed statuses accurately represent completed service work. Lead Status and Opportunity Forecast Categories apply to sales processes, while Campaign Member Status tracks marketing participation. Proper Case status configuration is important because automation, reporting, service metrics, and user behavior may depend on whether Salesforce considers a Case open or closed.

Q152. An organization wants to use a standard response repeatedly when support agents send emails from Case records. Which Salesforce capability is MOST appropriate?

1. Role Hierarchy
   2. Email Template
   3. Opportunity Team
   4. Forecast Category

Correct Answer: 3. Email Template

Explanation: Email Templates allow organizations to create standardized reusable messages that users and automation can send in consistent formats. Templates can include merge fields so information from Salesforce records appears dynamically in the message. This is useful for Case acknowledgements, status updates, sales communications, and other recurring correspondence. Role hierarchy controls record visibility, Opportunity Teams support sales collaboration, and Forecast Categories classify sales pipeline. Administrators should make templates clear, accurate, and appropriately accessible and should understand that templates can also be used by automation such as email alerts or auto-response processes.

Q153. A report has filters for Region, Industry, and Annual Revenue. The business requires records where Region is East AND either Industry is Technology OR Annual Revenue exceeds $10 million. Which report capability should be used?

1. Filter Logic
   2. Record Type
   3. Queue
   4. Compact Layout

Correct Answer: 1. Filter Logic

Explanation: Filter Logic allows report builders to define Boolean relationships among multiple report filters using expressions such as 1 AND (2 OR 3). This is necessary when the required conditions cannot be represented correctly by simply applying all filters with the default AND behavior. In this scenario, Region must always be East, while either Industry or Annual Revenue can satisfy the secondary requirement. Record Types affect business processes, Queues support shared ownership, and Compact Layouts control highlighted fields. Report filter logic is a useful analytics capability for translating complex business questions into precise Salesforce reports.

Q154. A sales manager wants a dashboard to display all Opportunity data available to one designated sales operations user, regardless of who is viewing the dashboard. Which configuration should be used?

1. Dynamic dashboard running as the logged-in user
   2. Dashboard with the sales operations user selected as the running user
   3. Personal list view
   4. Private report folder only

Correct Answer: 4. Dashboard with the sales operations user selected as the running user

Explanation: A standard dashboard can run using a specified running user’s security context. Viewers then see dashboard data based on what that running user can access, subject to dashboard and folder permissions. This differs from a dynamic dashboard, which runs as the logged-in viewer and therefore reflects each viewer’s own record access. Administrators should select the running-user model carefully because choosing a highly privileged user can expose aggregated information more broadly than intended. Report and dashboard folder access remains important, but folder security alone does not determine which underlying records the dashboard components can include.

Q155. An administrator wants report users to see only records whose Close Date is within the current fiscal quarter. Which feature should be used?

1. A relative date filter in the report
   2. A new custom object
   3. A public group
   4. A permission set group

Correct Answer: 2. A relative date filter in the report

Explanation: Relative date filters allow Salesforce reports to use dynamic date ranges such as THIS QUARTER, LAST MONTH, or NEXT 90 DAYS rather than hard-coded dates. This keeps the report current over time without requiring users to edit the filters every period. The correct available syntax depends on the date field and report builder. Custom objects, Public Groups, and Permission Set Groups solve unrelated data-modeling, sharing, and permission requirements. Relative filters are especially useful for recurring management reports because they automatically adjust as the current date moves forward.

Q156. A report owner wants to exclude records where a text field is blank. Which report configuration should be used?

1. Record Type
   2. Role Hierarchy
   3. An appropriate report field filter for nonblank values
   4. Approval Process

Correct Answer: 3. An appropriate report field filter for nonblank values

Explanation: Report filters can restrict results according to field values, including whether supported fields are blank or nonblank. This lets users exclude incomplete records from a report without changing the underlying Salesforce data. The exact filter expression depends on field type and report functionality. Record Types change business processes and layouts, Role Hierarchy influences record visibility, and Approval Processes route records for authorization. Reports should use filtering when the requirement concerns what appears in the analysis rather than requiring a permanent change to the underlying data model.

Q157. A record-triggered Flow should run only when an Opportunity Amount changes, regardless of whether the new amount is higher or lower. What should the administrator use in the Flow logic?

1. A function or condition that detects whether the field changed
   2. A dashboard filter
   3. A queue assignment
   4. A campaign hierarchy

Correct Answer: 1. A function or condition that detects whether the field changed

Explanation: Record-triggered automation can use change-detection logic to determine whether a particular field’s value changed between the prior and current record state. This is useful when the automation should respond to any change rather than only when a record enters a specific threshold. The administrator should also configure suitable entry conditions and timing to avoid unnecessary executions. Dashboard filters, queues, and Campaign hierarchies are unrelated. Designing Flow conditions precisely helps prevent duplicate actions, unnecessary processing, and automation that runs on every edit even when the relevant business data did not change.

Q158. A Flow needs to wait for a business event from another process before continuing. Which Flow capability should the administrator evaluate?

1. Compact Layout
   2. Pause or event-based waiting behavior where supported
   3. Lead Assignment Rule
   4. Dashboard Subscription

Correct Answer: 4. Pause or event-based waiting behavior where supported

Explanation: Some Flow designs require processing to pause until a later time or until an expected event occurs. Salesforce provides supported waiting and resume mechanisms depending on Flow type and use case. The administrator should select the appropriate declarative capability and understand how interviews are resumed, how time or events are evaluated, and what happens when records change while waiting. Compact Layouts affect highlighted fields, Lead Assignment Rules route Leads, and dashboard subscriptions deliver analytics updates. Long-running automation should be designed carefully so delayed steps remain reliable and understandable.

Q159. An Agentforce agent is configured with a topic that should handle order-status questions but not refund requests. What is the BEST configuration approach?

1. Clearly define topic scope and route refund requests outside the topic or to an approved separate capability
   2. Give the topic authority over every customer-service action
   3. Remove all topic instructions
   4. Grant refund permissions and trust the model not to use them

Correct Answer: 2. Clearly define topic scope and route refund requests outside the topic or to an approved separate capability

Explanation: Agentforce topics should have a clearly defined scope so the agent knows which customer requests they are intended to handle. If order-status inquiries are supported but refunds require a separate process or authorization, the topic and available actions should reflect that distinction. Behavioral instructions help guide the agent, while action permissions and Salesforce security provide stronger boundaries. Giving unnecessary refund capabilities would expand risk. Administrators should test both in-scope and out-of-scope requests to ensure the agent behaves appropriately and escalates or redirects unsupported tasks.

Q160. An Agentforce agent answers a user’s question using Salesforce record data. What determines which Salesforce records the agent should be permitted to use?

1. The length of the user’s prompt
   2. The Agentforce topic name only
   3. Appropriate Salesforce data-access permissions, sharing, and agent configuration
   4. The number of actions configured for the agent

Correct Answer: 3. Appropriate Salesforce data-access permissions, sharing, and agent configuration

Explanation: Agentforce does not eliminate Salesforce’s underlying security model. Access to Salesforce data should remain governed through appropriate permissions, field-level security, sharing, and agent-specific configuration. Topic names and prompt wording do not grant access to otherwise restricted records. Administrators should apply least privilege, verify which data sources and actions the agent can use, and test with realistic user and record-access scenarios. As Agentforce now represents a dedicated portion of the Platform Administrator exam, understanding how AI agents interact with established Salesforce security is increasingly important.