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

Q201. A company wants users to receive access to additional fields and objects based on their job function without creating numerous profiles. Which Salesforce access-management approach is BEST?

1. Create a separate role for every permission combination
   2. Use a minimal baseline profile and assign additional access through permission sets
   3. Change organization-wide defaults for each job function
   4. Create a new record type for every department

Correct Answer: 2. Use a minimal baseline profile and assign additional access through permission sets

Explanation: Permission sets allow administrators to add object, field, application, and system permissions without creating many nearly identical profiles. A common maintainable approach is to provide users with an appropriate baseline profile and then layer additional permissions according to job responsibilities. Roles primarily influence record-level visibility rather than object or field permissions. Organization-wide defaults determine baseline record sharing for the organization, and record types control processes, layouts, and picklist availability. Using permission sets reduces profile proliferation and makes access easier to adjust when employees change responsibilities.

Q202. A user needs to view records owned by colleagues at the same level of the role hierarchy, but the organization-wide default is Private. Which mechanism can an administrator use to open the required access systematically?

1. Compact Layout
   2. Validation Rule
   3. Record Type
   4. Sharing Rule

Correct Answer: 4. Sharing Rule

Explanation: Sharing Rules extend record access beyond the baseline established by organization-wide defaults. They can share records based on ownership or record criteria with roles, roles and subordinates, or public groups, depending on configuration. Users at the same hierarchy level do not automatically gain access to one another’s privately owned records merely because their roles are peers. Compact Layouts affect highlighted fields, Validation Rules enforce data quality, and Record Types control business processes. Sharing Rules are therefore appropriate when a repeatable access exception must apply to a defined group of records and users.

Q203. An administrator wants to ensure that a custom checkbox field is checked automatically whenever a numerical score exceeds 90, and users should not manually edit the checkbox. What is the BEST solution?

1. Create a formula checkbox field based on the score
   2. Create a manual checkbox and train users
   3. Use a sharing rule
   4. Use a queue

Correct Answer: 1. Create a formula checkbox field based on the score

Explanation: A formula checkbox field can evaluate a condition such as Score__c > 90 and automatically display TRUE or FALSE. Because the value is calculated rather than manually stored, users cannot alter it independently of the score. This ensures consistent behavior without requiring automation or user training. A manually maintained checkbox could become inconsistent with the score. Sharing Rules control record access, and Queues support shared ownership. Formula fields are appropriate when a value should always be derived from other data and should update automatically whenever referenced fields change.

Q204. A company has two divisions that use the same custom object but require different page layouts and different picklist values. Which configuration should the administrator use?

1. Two public groups
   2. Two queues
   3. Record types associated with appropriate page layouts and picklist values
   4. Separate Salesforce organizations

Correct Answer: 3. Record types associated with appropriate page layouts and picklist values

Explanation: Record Types allow one Salesforce object to support different business processes, picklist selections, and page-layout assignments. This makes them appropriate when separate divisions work with the same underlying object but need different user experiences or process values. Public Groups help with sharing, while Queues support shared ownership for supported objects. Creating separate Salesforce organizations would introduce unnecessary complexity and fragmented reporting. Administrators should use record types when there is a meaningful difference in process or available values rather than creating them merely to distinguish user groups.

Q205. An administrator needs to prevent users from changing an Account’s Customer Number after the field has initially been populated. Which solution is MOST appropriate?

1. A validation rule comparing the current and prior field values
   2. A report filter
   3. A dashboard subscription
   4. An Account Team

Correct Answer: 1. A validation rule comparing the current and prior field values

Explanation: A Validation Rule can detect whether a field has changed and prevent the save when the change violates a business requirement. The administrator can create logic that allows the Customer Number to be entered initially but blocks later modification once a value exists. This protects an identifier that downstream systems or processes may depend on. Report filters and dashboard subscriptions affect analytics rather than data entry, while Account Teams govern collaboration. A clear validation error message should explain why the change is prohibited so users know how to proceed when corrections are legitimately required.

Q206. A custom Child object should inherit ownership and sharing behavior from its Parent record. The Child records should also be deleted when the Parent is deleted. Which relationship type should be used?

1. Lookup relationship
   2. External lookup relationship
   3. Hierarchical relationship
   4. Master-detail relationship

Correct Answer: 4. Master-detail relationship

Explanation: A master-detail relationship creates a strong dependency between the detail record and its master. The detail record inherits important ownership and sharing behavior from the master, and deleting the master normally cascades deletion to its details. Master-detail also enables roll-up summary fields on the master. A standard lookup is more loosely coupled and generally allows the child record to exist independently. External lookups connect external data scenarios, while hierarchical relationships are specialized User-to-User relationships. Administrators should choose master-detail only when the lifecycle and security dependency accurately represent the business relationship.

Q207. A company wants Leads with an annual revenue greater than $5 million to be routed to an Enterprise Sales queue, while other Leads go to a General Sales queue. Which feature should be configured?

1. Campaign Influence
   2. Lead Assignment Rule
   3. Opportunity Split
   4. Case Escalation Rule

Correct Answer: 2. Lead Assignment Rule

Explanation: Lead Assignment Rules evaluate incoming Leads against ordered criteria and can assign them to users or queues. The administrator can create one rule entry for Leads above the revenue threshold and another for the remaining Leads. This provides consistent ownership routing and avoids manual triage. Campaign Influence measures marketing contribution, Opportunity Splits allocate sales credit, and Case Escalation Rules apply to customer service Cases. Administrators should order assignment-rule entries carefully because Salesforce evaluates them according to the configured sequence and applies the matching assignment behavior.

Q208. A sales manager wants to distinguish Opportunities that are likely to close this period from those that remain earlier in the pipeline. Which Salesforce feature is designed to support this classification for forecasting?

1. Case Status
   2. Campaign Member Status
   3. Forecast Categories
   4. Knowledge Data Categories

Correct Answer: 3. Forecast Categories

Explanation: Forecast Categories classify Opportunities according to their expected likelihood of closing and support pipeline forecasting. Opportunity stages map to forecast categories such as Pipeline, Best Case, Commit, Closed, or Omitted, depending on configuration. This helps managers analyze expected revenue independently of the exact stage labels used in the sales process. Case Status belongs to customer service, Campaign Member Status tracks marketing engagement, and Knowledge Data Categories organize Knowledge content. Administrators should ensure stage-to-forecast mappings reflect the organization’s sales methodology because forecasting accuracy depends partly on consistent Opportunity management.

Q209. A support department wants urgent Cases automatically reassigned to a senior support queue if they remain unresolved for a defined amount of business time. Which feature should be used?

1. Lead Assignment Rule
   2. Opportunity Team
   3. Campaign Hierarchy
   4. Case Escalation Rule

Correct Answer: 4. Case Escalation Rule

Explanation: Case Escalation Rules can evaluate unresolved Cases after specified amounts of time and then perform escalation actions such as reassigning ownership or sending notifications. They can work with configured business hours so the elapsed time reflects the support organization’s operating schedule. Lead Assignment Rules apply to sales Leads, Opportunity Teams facilitate sales collaboration, and Campaign Hierarchies organize marketing initiatives. Escalation rules are particularly useful when service-level expectations require unresolved high-priority Cases to receive increased attention after a predictable threshold.

Q210. A service organization wants new Cases for the “Hardware” product family sent directly to a specialized queue as soon as they are created. Which feature should the administrator configure?

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

Correct Answer: 2. Case Assignment Rule

Explanation: Case Assignment Rules automatically route new Cases to specific users or queues based on criteria such as product, priority, origin, or region. This allows Hardware Cases to reach the appropriate specialists immediately without manual reassignment. Escalation Rules address Cases after time-based conditions occur, while Assignment Rules control initial routing. Dashboard filters affect analytics, Approval Processes handle formal approvals, and Account Hierarchy represents corporate Account relationships. Administrators should ensure assignment criteria are ordered logically so each Case reaches the intended destination when multiple conditions might apply.

Q211. A data migration must load records into Salesforce while updating records whose external identifier already exists and inserting records when the identifier is new. Which operation should the administrator use?

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

Correct Answer: 1. Upsert

Explanation: Upsert combines insert and update behavior. Salesforce attempts to match incoming rows to existing records using an appropriate Salesforce ID or External ID. When a match is found, the existing record is updated; when no match exists, a new record can be inserted. This makes upsert useful for synchronizing Salesforce with external systems or performing migrations in which records may already exist. Delete removes records, Export extracts data, and Merge consolidates supported duplicate records rather than processing a general integration dataset. Administrators should test mappings and matching identifiers carefully before running large upsert operations.

Q212. An administrator needs to identify possible duplicate Contacts when Email and Last Name match existing records. Which configuration should be created?

1. Sharing Rule and Queue
   2. Sales Process and Record Type
   3. Matching Rule and Duplicate Rule
   4. Dashboard and Report Type

Correct Answer: 3. Matching Rule and Duplicate Rule

Explanation: A Matching Rule defines how Salesforce compares records to identify possible duplicates, while a Duplicate Rule determines what happens when a match is detected. The administrator can configure a matching strategy using fields such as Email and Last Name and then decide whether Salesforce should block the save or allow it with a warning. Sharing Rules, Queues, Record Types, and dashboards serve different purposes. Duplicate management improves data quality, but administrators should test criteria to balance accurate detection with the risk of false positives that could interfere with legitimate record creation.

Q213. A manager wants to see all Opportunities that have Opportunity Products but exclude Opportunities that do not contain any products. Which reporting capability is BEST?

1. Bucket Field
   2. Cross Filter
   3. Compact Layout
   4. Login IP Range

Correct Answer: 2. Cross Filter

Explanation: Cross Filters allow report builders to include or exclude records based on whether related records exist. A report can therefore show Opportunities with Opportunity Products, and additional subfilters can further refine the related records when necessary. Bucket Fields group values into reporting categories but do not filter according to related-record existence. Compact Layouts control highlighted record fields, and Login IP Ranges control authentication locations. Cross Filters are useful when business questions involve relationships such as Accounts without Contacts, Opportunities with Products, or Cases with specific related records.

Q214. A report displays revenue grouped by product family. The manager wants to calculate each product family’s percentage of total revenue. Which feature should the administrator use?

1. Summary Formula
   2. Sharing Rule
   3. Validation Rule
   4. Auto Number

Correct Answer: 1. Summary Formula

Explanation: Summary Formulas perform calculations using grouped or grand-total values in reports. They can calculate each product family’s summarized revenue as a percentage of the overall total without requiring a permanent field on the underlying records. Row-Level Formulas instead calculate a value for each individual report row. Sharing Rules manage record access, Validation Rules enforce data quality, and Auto Number fields create generated identifiers. Administrators should use report formulas when the calculation is primarily analytical and does not need to exist as operational data elsewhere in Salesforce.

Q215. A company needs a nightly process to find Contracts expiring within 30 days and create renewal Tasks. No user action should be required to start the process. Which automation is BEST?

1. Screen Flow
   2. Validation Rule
   3. Scheduled-triggered Flow
   4. Manual Sharing

Correct Answer: 4. Scheduled-triggered Flow

Explanation: A Scheduled-Triggered Flow can run automatically according to a defined schedule and evaluate records that meet configured criteria. This makes it appropriate for nightly processes such as identifying contracts approaching expiration and creating follow-up work. A Screen Flow requires user interaction, while Validation Rules enforce record-save requirements. Manual Sharing governs record access rather than automation. The Flow should use selective criteria so it processes only relevant records and should include safeguards to avoid creating duplicate renewal Tasks on repeated nightly executions.

Q216. A Flow retrieves several records and must build a new text value by processing each record individually. Which element is required to iterate through the collection?

1. Screen
   2. Pause
   3. Loop
   4. Approval Step

Correct Answer: 3. Loop

Explanation: A Loop element processes each item in a Flow collection one at a time. Within the loop, the administrator can evaluate record values, assign information to variables, or build another collection. Administrators should avoid placing unnecessary database Create, Update, or Delete operations inside loops because repeated operations can reduce efficiency. Where possible, records should be accumulated in a collection and processed in bulk after the loop. Screen elements interact with users, Pause handles waiting scenarios, and Approval Steps belong to approval processes rather than Flow collection iteration.

Q217. A user needs a button-like action on an Opportunity record that launches a guided Flow and automatically passes the current Opportunity’s ID into the Flow. Which approach is MOST appropriate?

1. Place a Flow action on the Opportunity record page and pass the record context
   2. Create a public calendar
   3. Change organization-wide defaults
   4. Use a Case Queue

Correct Answer: 1. Place a Flow action on the Opportunity record page and pass the record context

Explanation: A Screen Flow can be exposed as an action on a record page so users can launch a guided process in the context of the current record. A properly configured input variable can receive the current record ID, allowing the Flow to retrieve or update the relevant Opportunity. This creates a streamlined user experience without asking the user to search for the Opportunity again. Public Calendars, organization-wide defaults, and Case Queues do not launch contextual guided automation. Administrators should also ensure the user has permissions for all data and actions performed by the Flow.

Q218. An Agentforce agent is configured to answer policy questions from approved company information. Users report that it sometimes handles requests outside its intended area. What should the administrator refine?

1. Opportunity Forecast Categories
   2. Topic scope, topic instructions, and appropriate fallback behavior
   3. Account Team roles
   4. Campaign Member Statuses

Correct Answer: 4. Topic scope, topic instructions, and appropriate fallback behavior

Explanation: An Agentforce agent should have clearly defined topics describing the kinds of requests it is intended to handle. Instructions should guide behavior within that scope, and appropriate fallback or escalation should exist for unsupported requests. If the agent responds outside its intended area, the administrator should review how topics are classified and what guidance governs out-of-scope conversations. Salesforce permissions and available actions must also remain appropriately constrained. Sales forecasting, Account Teams, and Campaign Member Status do not control an agent’s conversational scope.

Q219. An Agentforce action can perform a sensitive update to a customer record. Which administrative approach BEST follows least-privilege principles?

1. Give the agent every available action to avoid failures
   2. Give all users Modify All Data
   3. Expose the sensitive action only when required, with appropriate permissions and tested safeguards
   4. Rely only on the action’s display name to prevent misuse

Correct Answer: 3. Expose the sensitive action only when required, with appropriate permissions and tested safeguards

Explanation: Actions that modify sensitive customer information should be made available only when necessary for the approved agent use case. Administrators should verify permissions, data access, inputs, expected behavior, and escalation paths and should test both normal and adversarial or unexpected scenarios. Providing unnecessary actions increases the potential impact of incorrect agent behavior. Granting users broad permissions would violate least-privilege principles, while names and descriptions are not security controls. Agentforce configuration should complement rather than bypass Salesforce’s established object, field, and record-level security.

Q220. A company is piloting Agentforce with internal users. Which measurement would be MOST useful for deciding what configuration needs refinement before broader deployment?

1. The number of Salesforce objects in the organization
   2. Patterns in successful resolutions, escalations, incorrect responses, and failed actions
   3. The number of inactive users
   4. The total number of page layouts

Correct Answer: 2. Patterns in successful resolutions, escalations, incorrect responses, and failed actions

Explanation: A pilot should provide evidence about how well the agent performs in realistic use. Administrators should examine whether intended requests are handled successfully, when human escalation occurs, which answers are inaccurate or unsupported, and whether configured actions fail or behave unexpectedly. These patterns help identify where topics, instructions, knowledge grounding, permissions, actions, or handoff behavior need refinement. Counts of objects, inactive users, or page layouts do not directly indicate agent quality. Controlled monitoring and iterative configuration help reduce risk before an Agentforce agent is exposed to a larger audience.