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

Q261. A sales operations user should be able to create and edit Campaign records but must not be allowed to delete them. Which configuration should the administrator review?

1. Object permissions assigned through the user’s profile and permission sets
   2. Campaign Member Status values
   3. Role hierarchy
   4. Organization-wide defaults

Correct Answer: 1. Object permissions assigned through the user’s profile and permission sets

Explanation: Object permissions determine whether users can Create, Read, Edit, or Delete records of a particular object. If a user should manage Campaigns but not delete them, the administrator should ensure Create, Read, and Edit are granted while Delete is not. Profiles establish baseline permissions, and permission sets can add additional permissions. The role hierarchy and organization-wide defaults govern record-level visibility rather than whether the user possesses the Delete capability for the object. Administrators should always check all assigned permission sets because permissions are additive and another assignment could unintentionally grant Delete access.

Q262. An employee is covering another department for three months and needs additional Salesforce permissions only during that period. Which approach is MOST appropriate where assignment expiration is available?

1. Permanently modify the employee’s profile
   2. Assign an appropriate permission set with an expiration date
   3. Move the employee to the System Administrator profile
   4. Change all relevant organization-wide defaults

Correct Answer: 2. Assign an appropriate permission set with an expiration date

Explanation: A permission set is appropriate for granting additional access without altering a user’s baseline profile. Where Salesforce supports expiration for the assignment, the administrator can define when that temporary access should end, reducing the risk that elevated permissions remain after the temporary responsibility is complete. Permanently modifying a profile would affect other users assigned to that profile and make cleanup more difficult. Moving the user to System Administrator would grant excessive access, while changing organization-wide defaults would alter record visibility throughout the organization. Temporary access should follow least-privilege principles and have a defined end point.

Q263. A manager assumes that assigning a different record type will prevent users from viewing sensitive records. What should the administrator explain?

1. Record types automatically make records Private
   2. Record types replace field-level security
   3. Record types control processes and user experience, not record-level security
   4. Record types automatically create sharing rules

Correct Answer: 3. Record types control processes and user experience, not record-level security

Explanation: Record types are used to support different business processes, available picklist values, and page-layout assignments. They are not a record-security mechanism. Whether a user can access a particular record is determined by factors such as organization-wide defaults, role hierarchy, sharing rules, teams, manual sharing, and powerful permissions such as View All or Modify All. Field-level security separately governs field visibility and editability. Administrators should avoid treating a page or process difference as a security boundary. If sensitive records require restricted visibility, the sharing model must be designed specifically to enforce that restriction.

Q264. A Lightning record page should show a “Request Review” action only when an Opportunity Amount exceeds $250,000. Which feature should the administrator use?

1. Case Assignment Rule
   2. Public Group
   3. Campaign Hierarchy
   4. Dynamic Actions with visibility criteria

Correct Answer: 4. Dynamic Actions with visibility criteria

Explanation: Dynamic Actions allow administrators to control which actions appear on supported Lightning record pages based on conditions such as record-field values, user attributes, or other supported criteria. The administrator can therefore display the Request Review action only for Opportunities above the specified threshold. This creates a cleaner interface by showing users actions relevant to the current record context. Case Assignment Rules route Cases, Public Groups support access administration, and Campaign Hierarchies organize marketing efforts. Action visibility affects the interface but should not be considered a substitute for underlying permissions or authorization controls governing what the action can actually perform.

Q265. A custom Date field should initially contain today’s date whenever a user creates a new record, while still allowing the user to change the value before saving. Which configuration is BEST?

1. Configure a default value formula using the current date
   2. Create a Roll-Up Summary field
   3. Make the field Auto Number
   4. Use a sharing rule

Correct Answer: 1. Configure a default value formula using the current date

Explanation: A field default value can prepopulate a value when a new record is created while still allowing the user to change it before saving. For a Date field, a formula using the current date can satisfy this requirement without creating automation merely to populate an initial value. A formula field itself would be calculated and generally not directly editable, which would not satisfy the need for user adjustment. Roll-Up Summary fields aggregate child records, Auto Number generates identifiers, and Sharing Rules affect record access. Administrators should distinguish editable defaults from calculated values that must always remain derived.

Q266. A company has a checkbox named International Customer and a dependent picklist named Shipping Region. Different Shipping Region choices should appear depending on whether the checkbox is selected. Can the checkbox be used as a controlling field?

1. No, only text fields can control dependent picklists
   2. No, controlling fields must always be formulas
   3. No, only multi-select picklists can be controlling fields
   4. Yes, a checkbox can serve as a controlling field for a dependent picklist

Correct Answer: 4. Yes, a checkbox can serve as a controlling field for a dependent picklist

Explanation: Salesforce field dependencies can use supported picklist fields or checkbox fields as controlling fields. When a checkbox is used, the dependent picklist can display different available values depending on whether the checkbox is selected or cleared. This is useful for guiding users toward valid combinations and reducing incorrect data entry. Multi-select picklists can serve as dependent fields in some dependency scenarios but are not used as controlling fields. Formula fields are not generally used as controlling fields for standard field dependencies. Administrators should test dependencies carefully across record types because available picklist values may also be affected by record-type configuration.

Q267. A company offers a product in a custom Wholesale Price Book. Before the product can be added to that custom price book, what must generally exist?

1. A Case for the product
   2. A Campaign linked to the product
   3. A standard price for the product
   4. An Account Team

Correct Answer: 3. A standard price for the product

Explanation: Salesforce Products typically require a standard price in the Standard Price Book before administrators can add the product with prices to custom price books. Custom price books can then represent alternate pricing for channels such as wholesale, retail, regions, or customer segments. The Opportunity later uses a selected price book to determine which product prices are available. Cases, Campaigns, and Account Teams are unrelated to establishing a product’s pricing structure. Administrators should understand the relationship among Products, the Standard Price Book, custom price books, price book entries, and Opportunity Products when supporting product-based selling.

Q268. A sales representative adds several products to an Opportunity. What record type represents each individual product, quantity, and sales price associated with that Opportunity?

1. Campaign Member
   2. Opportunity Product
   3. Asset only
   4. Contract

Correct Answer: 2. Opportunity Product

Explanation: An Opportunity Product, also known as an Opportunity Line Item, represents a product included in a particular Opportunity together with information such as quantity, sales price, and related pricing details. The available products come from the price book selected for the Opportunity. Campaign Members represent Leads or Contacts associated with marketing campaigns. Assets generally represent products owned by customers after purchase, while Contracts represent formal agreements. Opportunity Products give sales teams a detailed breakdown of what is being sold instead of relying solely on a single Opportunity Amount value, supporting more accurate sales analysis and product reporting.

Q269. A company receives Cases through several support channels. Management wants a dashboard showing how many Cases entered through Email, Phone, and Web during each month. Which data is MOST important to maintain accurately?

1. Opportunity Probability
   2. Campaign Type
   3. Account Rating
   4. Case Origin

Correct Answer: 4. Case Origin

Explanation: Case Origin identifies the channel through which a support Case entered the organization, such as Email, Phone, or Web. Accurate Case Origin values allow reports and dashboards to compare service volume by channel and analyze trends over time. Automation may also use Origin for routing or communication decisions. Opportunity Probability belongs to sales pipeline management, Campaign Type categorizes marketing campaigns, and Account Rating describes Accounts rather than service channels. Administrators should ensure that automated intake mechanisms and manual Case creation populate Case Origin consistently so management reporting reflects the actual source of incoming service demand.

Q270. A customer sends a reply to an existing support email conversation. The organization wants the response associated with the existing Case rather than creating unrelated manual records. Which Salesforce service capability is designed around email-based Case communication?

1. Email-to-Case
   2. Web-to-Lead
   3. Opportunity Splits
   4. Campaign Influence

Correct Answer: 1. Email-to-Case

Explanation: Email-to-Case supports customer-service processes in which incoming support emails create and participate in Salesforce Case conversations. With appropriate threading and email configuration, replies can be associated with the appropriate Case so agents can manage the customer interaction in one service record. Administrators should test routing addresses, email handling, thread behavior, and automation carefully. Web-to-Lead captures sales prospects from websites, Opportunity Splits allocate sales credit, and Campaign Influence supports marketing attribution. Email-to-Case is specifically intended for organizations that want email-based customer support integrated with Salesforce Case management.

Q271. A support organization wants articles classified by both Product and Geographic Region so agents can find the most relevant troubleshooting information. Which Salesforce Knowledge feature should the administrator use?

1. Opportunity Teams
   2. Forecast Categories
   3. Data Categories
   4. Price Books

Correct Answer: 3. Data Categories

Explanation: Salesforce Knowledge Data Categories organize articles into logical classifications such as products, regions, customer types, or other business dimensions. They can improve article discoverability and, depending on configuration, participate in controlling which category content is visible to particular audiences. This makes them appropriate for classifying troubleshooting information across multiple dimensions. Opportunity Teams support deal collaboration, Forecast Categories support sales forecasting, and Price Books manage product prices. Knowledge administrators should define a category structure that is useful without becoming unnecessarily complex and should ensure article authors apply classifications consistently.

Q272. A Salesforce user wants to notify a specific colleague about an important discussion in Chatter so the colleague is directly referenced in the post. Which capability should the user use?

1. Opportunity Split
   2. Case Queue
   3. Dashboard Filter
   4. An @mention in Chatter

Correct Answer: 4. An @mention in Chatter

Explanation: Chatter supports @mentions, allowing users to reference people or supported groups directly within posts and comments. This can draw attention to information that requires a colleague’s awareness while keeping the discussion in the Salesforce collaboration context. The exact notification behavior depends on user and Chatter settings. Opportunity Splits distribute sales credit, Case Queues manage shared Case ownership, and Dashboard Filters alter analytics views. Administrators should understand Chatter feeds, following, groups, mentions, and security because collaboration functionality can improve productivity but must still respect access to the records and information being discussed.

Q273. A manager wants a visual chart from an existing Salesforce report displayed directly on a Lightning record page. Which configuration should the administrator evaluate?

1. Login Hours
   2. Lead Queue
   3. A report chart Lightning component with a suitable source report
   4. Duplicate Rule

Correct Answer: 3. A report chart Lightning component with a suitable source report

Explanation: Lightning App Builder can display supported analytics components, including report charts based on suitable reports, directly within a Lightning page. This can give users contextual analytical information without requiring them to navigate separately to the Reports tab. The underlying report must be configured appropriately, and users still need the necessary access to the analytics and data. Login Hours restrict authentication time, Lead Queues manage Lead ownership, and Duplicate Rules manage duplicate detection. Administrators should confirm that the report chart adds meaningful context and does not expose summarized information beyond the intended audience.

Q274. An administrator needs to update and delete records in bulk and also export data using a client tool rather than a browser-only wizard. Which Salesforce tool is MOST appropriate?

1. Lightning App Builder
   2. Data Loader
   3. Schema Builder
   4. Chatter

Correct Answer: 2. Data Loader

Explanation: Data Loader supports bulk data operations such as insert, update, upsert, delete, and export and is well suited to larger or more advanced data-management tasks. It provides more operational flexibility than Data Import Wizard, which is a browser-based tool focused mainly on supported import scenarios. Administrators should back up critical data, validate mappings, understand required fields and automation effects, and review success and error files after processing. Lightning App Builder configures user interfaces, Schema Builder visualizes object relationships, and Chatter supports collaboration. Bulk changes should always be tested before large production runs.

Q275. An administrator needs to permanently remove records so they do not go to the Salesforce Recycle Bin. Which Data Loader operation should be used only with appropriate caution and permissions?

1. Hard Delete
   2. Upsert
   3. Export
   4. Insert

Correct Answer: 1. Hard Delete

Explanation: Hard Delete permanently removes records without placing them in the Salesforce Recycle Bin. Because ordinary Recycle Bin recovery is unavailable afterward, the operation should be used only when the administrator has appropriate permissions, a clear business requirement, and a reliable backup or recovery plan. Upsert updates matching records or inserts new ones, Export extracts data, and Insert creates new records. Permanently deleting data can also affect related records, reports, integrations, and compliance requirements, so selection criteria should be carefully reviewed and preferably tested on a small controlled dataset before executing a large Hard Delete operation.

Q276. A record-triggered Flow should execute when a record is deleted so the organization can perform appropriate declarative cleanup actions supported by the Flow. Which trigger should the administrator evaluate?

1. A Screen Flow launched manually
   2. A record-triggered Flow configured for deletion
   3. A dashboard subscription
   4. A Campaign hierarchy

Correct Answer: 2. A record-triggered Flow configured for deletion

Explanation: Salesforce record-triggered Flow supports automation associated with record lifecycle events, including deletion in supported scenarios. When a business requirement involves actions that should occur as a record is deleted, the administrator should evaluate a delete-triggered Flow and verify which Flow elements and operations are available in that execution context. A Screen Flow requires user interaction and is not automatically initiated by deletion. Dashboard subscriptions and Campaign hierarchies solve unrelated analytics and marketing requirements. Delete automation should be designed carefully because the triggering record is being removed and some post-save assumptions used in create or update automation may not apply.

Q277. A Flow needs to compare the current value of an Opportunity field with the value that existed before the update. Which resource should the administrator use in an appropriate record-triggered Flow?

1. A Campaign Member record
   2. Only the current $Record value
   3. A dashboard component
   4. The prior-record resource such as $Record__Prior**

Correct Answer: 4. The prior-record resource such as $Record__Prior

Explanation: In an appropriate record-triggered Flow, the prior-record resource provides access to field values from before the current update. This lets administrators compare previous and current values and implement logic such as detecting a transition from one status to another or identifying meaningful data changes. Using only the current record cannot provide the old value needed for that comparison. Campaign Members and dashboard components are unrelated. Administrators should combine prior-value logic with selective entry conditions where practical so Flows run only when needed and do not perform unnecessary actions on unrelated record edits.

Q278. An administrator wants a Flow to calculate a value using several variables without writing the result permanently to a Salesforce field. Which Flow resource should be considered?

1. Queue
   2. Formula resource
   3. Public Group
   4. Record Type

Correct Answer: 2. Formula resource

Explanation: A Flow Formula resource can calculate a value dynamically using available variables, record values, functions, and other supported resources. This is useful when the result is needed only during Flow execution and does not need to be stored as a permanent field on a Salesforce object. Formula resources can simplify decisions, assignments, displayed messages, and other logic. Queues manage shared ownership, Public Groups support sharing and access assignments, and Record Types vary business processes. Administrators should keep formulas readable and test edge cases such as blank values, date calculations, and different data types.

Q279. An Agentforce administrator wants to allow an agent to read customer information but avoid giving it unnecessary capabilities to change customer records. Which approach BEST follows Salesforce security principles?

1. Give the agent all available write actions in case they are needed later
   2. Assign unrestricted administrative permissions
   3. Provide only the required read-oriented data access and approved actions
   4. Disable field-level security for the agent

Correct Answer: 3. Provide only the required read-oriented data access and approved actions

Explanation: Least privilege means providing only the data access and actions required for an approved business purpose. If the agent’s role is informational, unnecessary record-update capabilities should not be exposed. This reduces the potential impact of unexpected prompts, configuration errors, or incorrect agent behavior. Salesforce object permissions, field-level security, sharing, and the set of available actions all contribute to effective controls. Giving the agent broad administrative or write access simply for convenience would increase risk. Administrators should also test the agent with users who have different access levels to verify that security boundaries remain effective.

Q280. An administrator wants centralized visibility into Flow performance and execution information using a current Spring ’26 capability highlighted in Salesforce maintenance material. Which feature should the administrator evaluate?

1. Flow Logs tab
   2. Opportunity Contact Roles
   3. Campaign Member Status
   4. Account Hierarchy

Correct Answer: 1. Flow Logs tab

Explanation: Salesforce’s Spring ’26 Platform Administrator maintenance material highlights the Flow Logs tab as a capability that uses Data 360 to provide centralized visibility into Flow performance. This can help administrators monitor automation behavior and investigate execution patterns more systematically. The feature has prerequisites and should be evaluated within the organization’s edition and Data 360 configuration. Opportunity Contact Roles identify stakeholders in deals, Campaign Member Status tracks marketing responses, and Account Hierarchy represents corporate Account relationships. Monitoring is an important part of Flow administration because active automation can affect many users and records when performance or logic issues occur.