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

Q61. A Salesforce user is leaving the company. The administrator must prevent the user from logging in while preserving the user’s historical record ownership and activity references. What should the administrator do?

1. Delete the user
   2. Deactivate the user
   3. Delete all records owned by the user
   4. Change the user’s profile to Read Only

Correct Answer: 2. Deactivate the user

Explanation: Salesforce user records generally are not deleted because historical records, audit information, ownership references, and activities may depend on them. Deactivating the user removes the ability to log in while preserving those relationships. Before deactivation, administrators may need to transfer active records or reassign responsibilities such as scheduled jobs. Simply changing a profile does not reliably prevent authentication, and deleting owned records would destroy business information. User management is a core administrator responsibility, and deactivation is the standard approach when an employee no longer requires access but organizational history must remain intact.

Q62. A company wants a trusted operations manager to reset passwords and create users without giving the manager full System Administrator access. Which Salesforce capability should be considered?

1. Role hierarchy
   2. Manual sharing
   3. Public group
   4. Delegated administration

Correct Answer: 4. Delegated administration

Explanation: Delegated administration allows selected users to perform limited administrative tasks without receiving broad System Administrator permissions. Depending on configuration, delegated administrators can manage specified users and perform certain setup activities within an assigned scope. This supports least privilege by giving business operations personnel only the administrative authority they require. Role hierarchy and public groups primarily affect record visibility and sharing, while manual sharing grants access to individual records. Delegated administration is useful when administrative duties need to be distributed without exposing the entire Salesforce configuration to additional users.

Q63. A custom field was deleted accidentally from an object yesterday. The administrator wants to restore it together with its field definition if possible. Where should the administrator look FIRST?

1. Deleted Fields for the object
   2. Recycle Bin on the Home page
   3. Data Export
   4. Setup Audit Trail only

Correct Answer: 1. Deleted Fields for the object

Explanation: Salesforce provides a Deleted Fields area for custom fields that have been removed but remain within the recoverable retention period. An administrator can restore an eligible deleted custom field from the object’s management settings rather than recreating it manually. The standard Recycle Bin is primarily for deleted records, not custom field definitions. Setup Audit Trail can help identify administrative changes but does not restore the field. Administrators should understand that deleting fields can also affect formulas, reports, layouts, and integrations, so restoration should be followed by validation of dependent configuration.

Q64. A company wants the available values in a Subcategory picklist to change automatically based on the value selected in a Category picklist. Which configuration should the administrator use?

1. Record ownership rule
   2. Roll-Up Summary field
   3. Field dependency
   4. Sharing rule

Correct Answer: 3. Field dependency

Explanation: Field dependencies control which values are available in a dependent picklist based on the value selected in a controlling field. For example, Category can act as the controlling field and Subcategory as the dependent picklist. This improves data quality and user experience by preventing irrelevant combinations from being selected. Roll-Up Summary fields aggregate related detail records, while sharing rules and ownership settings control record access. Field dependencies are a declarative way to guide users toward valid combinations without requiring custom code or separate objects for every possible selection.

Q65. A custom Invoice object has a lookup to Account. Users need a field on Invoice that displays the Account’s Industry without copying the value into a separate stored field. What should the administrator create?

1. Cross-object formula field
   2. Roll-Up Summary field
   3. Auto Number field
   4. External ID field

Correct Answer: 1. Cross-object formula field

Explanation: A cross-object formula can reference fields on a related parent record and display the calculated result dynamically. If Invoice has a lookup to Account, the formula can reference the related Account’s Industry field without maintaining duplicate data. The displayed value automatically reflects changes to the parent field. A Roll-Up Summary works in the opposite direction by aggregating detail records on a master object and requires a master-detail relationship. Auto Number creates sequential identifiers, while External ID fields support matching with external systems. Formula fields are useful when related data should be displayed rather than copied.

Q66. An administrator needs to model Students and Courses where each Student can enroll in many Courses and each Course can have many Students. Which data model is BEST?

1. One lookup directly from Student to Course
   2. One master-detail directly from Course to Student
   3. A junction object with relationships to Student and Course
   4. A formula field on Student

Correct Answer: 3. A junction object with relationships to Student and Course

Explanation: A many-to-many relationship in Salesforce is commonly modeled using a junction object. For example, an Enrollment custom object can relate a Student to a Course, with each Enrollment representing one student’s participation in one course. This enables any Student to have multiple Enrollments and any Course to have multiple Enrollments. Junction objects are often implemented using two master-detail relationships, depending on the required ownership and sharing behavior. A single lookup or master-detail relationship would support only one direct parent relationship and would not properly model many-to-many enrollment data.

Q67. Sales management wants to identify the Contacts who influence each Opportunity and record each person’s role in the buying process. Which feature should be used?

1. Campaign Members
   2. Opportunity Contact Roles
   3. Case Teams
   4. Account Sharing Rules

Correct Answer: 2. Opportunity Contact Roles

Explanation: Opportunity Contact Roles associate Contacts with an Opportunity and describe each person’s role in the sales process, such as Decision Maker, Evaluator, or Executive Sponsor. This gives sales teams visibility into the people influencing a deal without creating duplicate Contacts. Campaign Members track participation in marketing campaigns, Case Teams support collaboration on service Cases, and sharing rules affect record access. Opportunity Contact Roles are especially useful in business-to-business selling where multiple people from the same customer organization participate in one purchasing decision.

Q68. A sales manager wants to understand how Opportunities are classified for forecasting based on their stage. Which configuration should the administrator review?

1. Case Status values
   2. Campaign Member Status
   3. Account Team roles
   4. Forecast Category mapping for Opportunity stages

Correct Answer: 4. Forecast Category mapping for Opportunity stages

Explanation: Opportunity stages can be associated with forecast categories that indicate how likely revenue is to close, such as Pipeline, Best Case, Commit, Closed, or Omitted depending on configuration. Sales managers use these categories when reviewing forecast information across the pipeline. Case statuses apply to support processes, while Campaign Member Status tracks marketing responses and Account Team roles describe collaboration on customer Accounts. Administrators should understand how sales process configuration, Opportunity stages, probabilities, and forecast categories influence sales reporting and pipeline management.

Q69. A company wants website visitors to submit prospective customer information that creates new Lead records in Salesforce. Which feature should be used?

1. Email-to-Case
   2. Web-to-Case
   3. Web-to-Lead
   4. Case Auto-Response Rule

Correct Answer: 3. Web-to-Lead

Explanation: Web-to-Lead captures prospective customer information from a website and creates Lead records in Salesforce. After creation, Lead Assignment Rules and Auto-Response Rules can be used to route the Lead and acknowledge the submission. Web-to-Case creates customer support Cases instead, while Email-to-Case handles support requests submitted by email. Choosing the correct intake feature depends on whether the submission represents a sales prospect or a service request. Web-to-Lead is part of Salesforce’s sales and marketing automation capabilities tested for administrators.

Q70. Marketing managers want to organize several regional campaigns under one global marketing initiative and report on the hierarchy. Which feature should be used?

1. Campaign hierarchy
   2. Role hierarchy
   3. Opportunity team
   4. Price book hierarchy

Correct Answer: 1. Campaign hierarchy

Explanation: Campaign hierarchy allows related Campaigns to be organized under parent Campaigns, making it possible to represent a global initiative with regional or tactical child campaigns. This helps marketers report on results at both individual campaign and aggregate hierarchy levels. Role hierarchy affects record visibility, Opportunity Teams support collaboration on sales deals, and price books manage product pricing rather than marketing organization. Campaign hierarchies are useful when a company needs to connect multiple marketing activities and understand their combined performance under a broader program.

Q71. A support organization wants customers to search Knowledge articles and submit Cases through a branded self-service website. Which Salesforce capability should be considered?

1. Forecasts
   2. Experience Cloud site
   3. Opportunity Splits
   4. Data Loader

Correct Answer: 4. Experience Cloud site

Explanation: Experience Cloud can be used to create branded external sites where customers, partners, or other audiences interact with Salesforce content and processes. A customer service site can expose Knowledge content and allow authenticated or appropriately configured users to create and manage support Cases. Forecasts and Opportunity Splits are sales features, while Data Loader performs bulk data operations. Salesforce’s current administrator exam preparation includes sites using Experience Cloud within the Service and Support section because administrators may need to understand how external users interact with support functionality.

Q72. An administrator wants Cases owned by a support queue to be assigned automatically based on Region and Product when Cases are created. Which feature should be configured?

1. Lead Assignment Rule
   2. Case Assignment Rule
   3. Dashboard Filter
   4. Approval Process

Correct Answer: 2. Case Assignment Rule

Explanation: Case Assignment Rules automatically determine the owner of a Case according to ordered criteria. A rule can route Cases to specific users or queues based on values such as Region, Product, Priority, or Case Origin. This supports consistent workload distribution. Lead Assignment Rules perform a similar function for Leads, while Approval Processes handle formal approval decisions rather than ownership routing. Dashboard filters affect analytics. Salesforce’s administrator exam prep specifically includes Case Assignment Rules as a service automation capability.

Q73. An administrator needs to delete thousands of obsolete Lead records that meet specific criteria. Which administrative capability should be considered?

1. Mass Delete Records
   2. Lightning App Builder
   3. Role Hierarchy
   4. Campaign Influence

Correct Answer: 1. Mass Delete Records

Explanation: Mass Delete Records is a Salesforce administrative data-management capability for deleting groups of supported records that meet specified criteria. Administrators should review the selected records carefully and consider backup or export requirements before performing bulk deletion. Data retention policies and dependencies should also be considered. Lightning App Builder affects user-interface design, role hierarchy influences record visibility, and Campaign Influence deals with marketing attribution. Mass deletion is part of the data-management topics Salesforce includes in current Administrator certification preparation.

Q74. A sales analyst needs to calculate the percentage that each Opportunity’s Amount contributes to the total Amount displayed in the report. Which report feature should be considered?

1. Record Type
   2. Cross Filter
   3. Row-Level Formula
   4. Sharing Rule

Correct Answer: 4. Row-Level Formula

Explanation: Row-Level Formulas allow report builders to calculate a value for each report row without creating a field on the underlying object. They can be useful for derived calculations needed only in reporting. Depending on the exact percentage requirement and available report functionality, report summary formulas may also be used when calculations depend on grouped or grand totals. Record Types define business processes, Cross Filters filter records according to related-record conditions, and Sharing Rules control record access. Administrators should choose the reporting formula capability that best matches whether the calculation occurs per row or at summary level.

Q75. A report should show Accounts that do not have any related Opportunities. Which report filtering capability is BEST suited to this requirement?

1. Standard date filter
   2. Cross filter
   3. Bucket field
   4. Dashboard filter

Correct Answer: 3. Cross filter

Explanation: Cross filters allow report builders to filter records based on the existence or absence of related records. For example, a report can return Accounts without Opportunities or Accounts with Contacts matching additional criteria. This is more efficient than manually maintaining a flag solely for reporting. Bucket fields categorize field values, dashboard filters operate across dashboard components, and ordinary field filters do not directly express “with” or “without” related-object relationships in the same way. Cross filters are a useful advanced reporting capability for analyzing relationship-based business questions.

Q76. A sales manager has created a report that should be visible only to members of the Sales Management group. What should the administrator configure?

1. Report folder sharing
   2. Organization-Wide Defaults for Opportunities only
   3. Opportunity record types
   4. Lead assignment rules

Correct Answer: 1. Report folder sharing

Explanation: Reports and dashboards are stored in folders, and access to those folders determines who can view or manage the analytics content. Sharing the report folder with the appropriate group allows Sales Management to access the report without making it broadly visible to all users. Record-level sharing still applies to the underlying Salesforce data, so users see only records they are authorized to access unless dashboard running-user behavior changes context. Opportunity record types and Lead Assignment Rules do not control access to report definitions. Folder security is therefore essential to analytics administration.

Q77. An administrator needs an automation that runs every night and evaluates records even when no user edits them. Which Flow capability should be considered?

1. Screen Flow only
   2. Scheduled-triggered Flow
   3. Manual sharing
   4. Compact Layout

Correct Answer: 2. Scheduled-triggered Flow

Explanation: Scheduled-triggered Flow can run automatically according to a defined schedule and process records that meet specified criteria without requiring a user to create or update the record at that moment. This makes it useful for nightly or periodic automation such as updating status, flagging overdue records, or performing recurring maintenance. Screen Flows require user interaction, while manual sharing and compact layouts are unrelated to automation timing. Flow is the primary declarative automation platform emphasized in Salesforce’s current Administrator preparation.

Q78. A record-triggered Flow should create a related Task only after an Opportunity has been successfully saved. Which Flow timing should be used?

1. Before-save Flow
   2. Screen Flow
   3. After-save record-triggered Flow
   4. Validation Rule

Correct Answer: 4. After-save record-triggered Flow

Explanation: An after-save record-triggered Flow is appropriate when automation must perform actions involving other records, such as creating a Task, creating related records, sending notifications, or invoking additional actions after the triggering record has been committed. Before-save flows are optimized for quickly updating fields on the same record before it is saved. A Screen Flow provides interactive user screens, while Validation Rules prevent invalid data from being saved. Understanding before-save versus after-save behavior helps administrators design efficient and predictable Salesforce automation.

Q79. A company wants an Opportunity approval process to send the record first to the sales manager and then, for very large discounts, to the finance director. Which capability should be configured?

1. Multiple approval steps with criteria and assigned approvers
   2. Opportunity Team roles only
   3. Dashboard subscriptions
   4. Duplicate Rules

Correct Answer: 1. Multiple approval steps with criteria and assigned approvers

Explanation: An Approval Process can contain multiple approval steps, each with criteria determining whether the record enters that step and who should approve it. A discount request can first route to a sales manager and then, when a threshold is exceeded, move to finance. Approval and rejection actions can also update fields, send notifications, or perform other configured actions. Opportunity Team roles describe collaboration, while dashboards and Duplicate Rules solve unrelated requirements. Salesforce’s automation prep specifically includes criteria for approvers, approvals, and rejections.

Q80. A Flow updates hundreds of records and fails midway because of an unhandled error. What design practice would MOST improve troubleshooting?

1. Remove error handling to simplify the Flow
   2. Add fault paths and meaningful error handling to relevant Flow elements
   3. Hide all Flow errors from administrators
   4. Replace Flow with manual updates automatically

Correct Answer: 3. Add fault paths and meaningful error handling to relevant Flow elements

Explanation: Fault paths allow Flow designers to define what should happen when an element encounters an error. Depending on the process, fault handling can notify administrators, create an error record, present a useful message, or route the process through an appropriate recovery path. Without intentional error handling, failures can be difficult to diagnose and may leave users unsure what happened. Administrators should also test bulk behavior and avoid unnecessary record operations. Flow is a powerful automation platform, but maintainable automation requires clear entry criteria, efficient logic, testing, and fault management.