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

Q81. A Salesforce administrator wants users to access only the Lightning apps relevant to their job functions. Which configuration is MOST appropriate?

1. Change the organization-wide defaults
   2. Control app visibility through profiles and permission sets
   3. Create separate role hierarchies for each app
   4. Create duplicate user records

Correct Answer: 2. Control app visibility through profiles and permission sets

Explanation: App visibility determines which Salesforce apps users can access from the App Launcher or navigation. Administrators can manage app access through profile and permission-set assignments, allowing different job functions to receive different applications without modifying the record-sharing model. Organization-wide defaults govern record-level access rather than app availability, while role hierarchy primarily affects record visibility. Creating duplicate users is unnecessary and would complicate licensing and security. Salesforce administrators should distinguish between application access, object permissions, field-level security, and record-level sharing because each layer addresses a different aspect of the user-access model.

Q82. A sales organization wants users to access a custom object from the navigation bar of a Lightning app. What should the administrator configure?

1. A validation rule
   2. A sharing rule
   3. A workflow action
   4. Add the custom object’s tab or navigation item to the Lightning app**

Correct Answer: 4. Add the custom object’s tab or navigation item to the Lightning app

Explanation: Lightning apps can be configured with navigation items that determine which objects, tabs, and features appear in the app’s navigation bar. Adding the custom object’s tab allows authorized users to access the object conveniently from within the app. The users must still have object and record permissions separately. Validation rules control data entry, sharing rules extend record visibility, and workflow-related automation does not control app navigation. Administrators should understand that interface configuration and security are separate: displaying an object in navigation does not itself grant users permission to view or edit its records.

Q83. Users complain that the global search returns too many irrelevant record types. Which administrator setting should be reviewed?

1. Search settings and object search availability
   2. Case escalation rules
   3. Opportunity forecast categories
   4. Campaign hierarchy

Correct Answer: 1. Search settings and object search availability

Explanation: Salesforce search behavior can be influenced by which objects are searchable and by the user’s permissions and recent activity. If users are receiving irrelevant results, the administrator should review search-related configuration and whether unnecessary objects need to appear in the users’ experience. Security permissions also influence what records can appear. Case escalation, forecasting, and Campaign hierarchies solve unrelated business requirements. Search and user-interface configuration are part of the Configuration and Setup section of the Platform Administrator exam, so administrators should understand how search availability affects user productivity.

Q84. A company wants a custom field to be required for users on one page layout but optional for users on another. Which configuration should the administrator use?

1. Make the field universally required at the field definition
   2. Create a validation rule that always requires the field
   3. Mark the field required on the appropriate page layout only
   4. Change the field to an Auto Number field

Correct Answer: 3. Mark the field required on the appropriate page layout only

Explanation: Page layouts can make a field required for users assigned to that particular layout without making it universally required for every record and interface. This is appropriate when different business processes have different data-entry requirements. Marking the field required at the field-definition level makes it mandatory everywhere Salesforce enforces that field requirement. A validation rule could enforce conditional logic, but for a simple layout-specific requirement the page layout is more appropriate. Administrators should understand the difference between page-layout requirements, field-level security, field-definition requirements, and validation rules because they affect data entry in different ways.

Q85. A company needs users in one business unit to see a different set of picklist values for a custom object than users in another business unit. Which feature should the administrator use?

1. Record types
   2. Sharing rules
   3. Role hierarchy
   4. Login IP ranges

Correct Answer: 1. Record types

Explanation: Record types can control the available picklist values for different business processes and can also be associated with different page layouts. This makes them appropriate when separate groups use the same object but require different picklist options. Sharing rules and role hierarchy affect record visibility rather than picklist values, while login IP ranges restrict where users can authenticate from. Record types should be designed carefully because excessive use can create administrative complexity. They are most valuable when there is a genuine difference in business process, layout, or available picklist selections.

Q86. A sales manager wants Salesforce to notify a Lead immediately after the Lead submits information through a web form. Which feature is MOST appropriate?

1. Case Auto-Response Rule
   2. Opportunity Team
   3. Campaign Influence
   4. Lead Auto-Response Rule

Correct Answer: 4. Lead Auto-Response Rule

Explanation: Lead Auto-Response Rules can automatically send different email responses to newly created Leads according to criteria. They are useful for acknowledging web inquiries and providing relevant follow-up information immediately. Lead Assignment Rules determine who owns the Lead, while the auto-response rule communicates with the prospect. Case Auto-Response Rules perform a similar function for support Cases, not Leads. Opportunity Teams and Campaign Influence address sales collaboration and marketing attribution. Administrators should understand how Lead Assignment and Lead Auto-Response rules work together in a complete Lead-management process.

Q87. A company wants to categorize Leads as Hot, Warm, or Cold according to business criteria while keeping the classification available for reports and list views. Which approach is BEST?

1. Use a dashboard filter only
   2. Create and maintain an appropriate Lead field for the classification
   3. Store the value only in a Chatter post
   4. Use the Recycle Bin

Correct Answer: 2. Create and maintain an appropriate Lead field for the classification

Explanation: If a classification is required across record pages, reports, list views, automation, and integrations, it should normally be stored in an appropriate Salesforce field. The field could be a picklist populated manually or through automation, depending on requirements. Dashboard filters affect visualization only, while Chatter posts are unstructured collaboration content and are not suitable as authoritative business data. The Recycle Bin is unrelated. Administrators should distinguish between report-only categorization and persistent business data: when the value must support multiple processes, a real field is generally preferable.

Q88. A company sells subscription products and wants users to track quantities and sales prices associated with each Opportunity. Which Salesforce records should the administrator ensure are being used?

1. Case and Knowledge records
   2. Campaign and Campaign Member records
   3. Opportunity Products associated with Products and a Price Book
   4. Account Team records only

Correct Answer: 3. Opportunity Products associated with Products and a Price Book

Explanation: Products and Price Books define what an organization sells and at what prices. Opportunity Products, also known as Opportunity Line Items, associate selected products, quantities, and pricing with a specific Opportunity. This provides more detailed pipeline and revenue information than storing only one Opportunity Amount. Cases and Knowledge support service, while Campaigns support marketing and Account Teams support customer collaboration. Administrators working with sales applications should understand how Products, Price Books, Opportunities, and Opportunity Products relate when configuring Salesforce for product-based selling.

Q89. A support manager wants agents to execute several repetitive Case actions quickly, such as updating fields and sending an email. Which Salesforce productivity feature should be considered?

1. Record Type
   2. Role Hierarchy
   3. Campaign Hierarchy
   4. Macros

Correct Answer: 4. Macros

Explanation: Macros can help service users perform repetitive sequences of supported actions more efficiently, such as updating Case fields or sending standardized communications. This can improve productivity in high-volume service environments by reducing repeated manual steps. Record types control processes and layouts, role hierarchy affects record visibility, and Campaign hierarchies organize marketing activities. Macros should be designed according to the actions agents perform frequently and should complement broader Case automation such as assignment rules, queues, and Flow rather than replacing all service-process automation.

Q90. A company wants agents to see the amount of time remaining before a support commitment is breached for a customer Case. Which Salesforce service concept is MOST relevant?

1. Entitlements and milestones
   2. Opportunity Splits
   3. Lead Conversion
   4. Campaign Member Status

Correct Answer: 1. Entitlements and milestones

Explanation: Entitlements represent the support level a customer is eligible to receive, while milestones can track time-based commitments within entitlement processes. They are useful when support organizations must manage service commitments such as response or resolution targets. Opportunity Splits allocate sales credit, Lead Conversion transitions prospects into Account and Contact records, and Campaign Member Status tracks marketing responses. Although detailed entitlement configuration may vary by Salesforce edition and service implementation, administrators should recognize the role of entitlement-based service processes when business requirements involve formal support commitments.

Q91. A manager wants Salesforce to display only records that meet a set of saved filters and to make that view available to an entire team. Which feature is MOST appropriate?

1. Dashboard subscription
   2. Shared list view
   3. Approval Process
   4. Record Type

Correct Answer: 3. Shared list view

Explanation: List views provide filtered working sets of records for an object. A list view can be personal or shared with appropriate groups of users, allowing teams to work from the same filtered set without running a report each time. Dashboards focus on analytics and visualization, Approval Processes route records for authorization, and Record Types influence business processes and page layouts. Shared list views are especially useful for operational tasks such as viewing Leads requiring follow-up, Accounts in a territory, or Cases awaiting action. Administrators should manage list-view visibility to ensure users see relevant working queues without unnecessary clutter.

Q92. A user wants Salesforce to send a copy of a dashboard by email on a recurring schedule. Which capability should the administrator consider?

1. Lead Assignment Rule
   2. Page Layout Assignment
   3. Validation Rule
   4. Dashboard subscription

Correct Answer: 2. Dashboard subscription

Explanation: Dashboard subscriptions allow users, subject to Salesforce limits and permissions, to receive scheduled dashboard updates by email. This is useful for managers who want recurring visibility into sales, service, or operational metrics without manually opening the dashboard each time. Subscription behavior and availability can depend on Salesforce features and permissions. Lead Assignment Rules route Leads, Page Layout Assignments control user-interface layouts, and Validation Rules enforce data-entry requirements. Administrators should also remember that dashboard data is influenced by the dashboard’s running-user model and underlying record security.

Q93. A report should highlight Opportunity Amounts above a management-defined threshold with special formatting. Which report feature is MOST appropriate?

1. Conditional highlighting
   2. Sharing rule
   3. Record type
   4. External ID

Correct Answer: 1. Conditional highlighting

Explanation: Conditional highlighting can visually emphasize summarized report values that fall within specified ranges. This helps managers quickly identify results that are high, low, or otherwise noteworthy without manually inspecting every number. The report must be configured in a format that supports the feature. Sharing Rules affect record access, Record Types control business processes and layouts, and External IDs support external-system matching. Administrators should select report visualization features according to the decision the report supports, while still ensuring that the report folder and underlying records are accessible to the intended users.

Q94. A manager needs a report showing a calculation based on grouped totals rather than a calculation for each individual record. Which report capability should be considered?

1. Auto Number field
   2. Summary formula
   3. Lookup filter
   4. Duplicate rule

Correct Answer: 4. Summary formula

Explanation: Summary formulas perform calculations using summarized report values at group or grand-total levels. This is useful for ratios, percentages, and other analytics based on aggregates rather than individual records. Row-Level Formulas calculate a value for each report row, so administrators should select the correct formula type based on whether the required calculation is record-level or summary-level. Auto Number fields create identifiers, Lookup Filters restrict lookup selections, and Duplicate Rules manage duplicate detection. Summary formulas can make reports significantly more informative without adding new fields to the underlying Salesforce object.

Q95. An administrator wants to view a history of recent configuration changes made in Setup, including who made them. Which feature should be reviewed?

1. Recycle Bin
   2. Setup Audit Trail
   3. Opportunity History report only
   4. Campaign Influence

Correct Answer: 2. Setup Audit Trail

Explanation: Setup Audit Trail records many administrative configuration changes and identifies information such as who made the change and when it occurred. It is useful for troubleshooting, change review, and governance when administrators need to determine how organization configuration changed. It does not capture every possible business-data modification and should not be confused with field history tracking. The Recycle Bin contains deleted records, while Opportunity History and Campaign Influence serve sales and marketing purposes. Administrators should understand which Salesforce auditing feature is appropriate for configuration changes versus record-level data changes.

Q96. A company needs to track previous values of a critical custom field whenever users change it on a record. Which Salesforce feature should be enabled?

1. Field History Tracking
   2. List View
   3. Queue
   4. Search Layout

Correct Answer: 3. Field History Tracking

Explanation: Field History Tracking records changes to selected fields, including previous and new values where supported, along with information about when the change occurred and who made it. This can help with audit, troubleshooting, and understanding record evolution. The administrator enables tracking on the object and selects the appropriate fields within platform limits. A List View filters records, a Queue supports shared record ownership, and Search Layout controls aspects of the search interface. Field History Tracking is designed specifically for retaining a history of important record-field changes.

Q97. A user must work with Salesforce from a mobile device and needs a streamlined set of actions available on the record page. Which configuration should the administrator review?

1. Salesforce Mobile and Lightning Experience Actions on the page layout
   2. Opportunity Forecast Categories
   3. Data Export settings
   4. Case escalation criteria

Correct Answer: 1. Salesforce Mobile and Lightning Experience Actions on the page layout

Explanation: Page layouts can control which supported Salesforce Mobile and Lightning Experience actions are available to users on records. Administrators can prioritize frequently used actions so mobile users can update records, create related information, or perform common tasks efficiently. Compact layouts determine key highlighted fields but do not define the full action set. Forecast categories, exports, and Case escalation criteria solve unrelated business requirements. Mobile productivity should be designed around the tasks users need to complete while still respecting their object, field, and record permissions.

Q98. A record-triggered Flow should execute an action several days after a record meets the triggering criteria. Which Flow capability should the administrator use?

1. Formula field
   2. Scheduled path in the record-triggered Flow
   3. Manual sharing
   4. Dashboard filter

Correct Answer: 4. Scheduled path in the record-triggered Flow

Explanation: Scheduled paths allow actions within an appropriate record-triggered Flow to occur at a defined time offset relative to a record date or triggering event. They can be useful for follow-up activities, reminder actions, or other delayed automation tied to a record. This differs from a scheduled-triggered Flow, which runs on a recurring schedule and finds records meeting criteria at execution time. Formula fields calculate values rather than schedule actions, while sharing and dashboard filters are unrelated. Administrators should understand the difference between scheduled paths and scheduled-triggered flows when selecting automation timing.

Q99. An administrator is testing a Flow and wants to observe how the Flow moves through elements without affecting production users. Which capability should be used?

1. Flow Debug
   2. Case Queue
   3. Approval History
   4. Campaign Hierarchy

Correct Answer: 2. Flow Debug

Explanation: Flow Builder provides debugging capabilities that help administrators test a flow, inspect variable values, and understand which decisions and elements are executed. Debugging should be part of the development process before automation is activated broadly. Administrators should use appropriate test data and understand whether a particular debug option can perform record operations. Case queues, approval history, and Campaign hierarchies do not troubleshoot Flow execution. Testing declarative automation is important because a configuration error can affect many records or users once activated.

Q100. A record-triggered Flow updates the same record that caused the Flow to run, creating repeated executions. What should the administrator investigate FIRST?

1. Whether the Flow’s entry criteria and update logic are causing recursion or repeated triggering
   2. Whether the user’s dashboard subscription is active
   3. Whether the record belongs to a Campaign
   4. Whether the Recycle Bin is full

Correct Answer: 3. Whether the Flow’s entry criteria and update logic are causing recursion or repeated triggering

Explanation: Record-triggered automation should be designed so that updates do not repeatedly satisfy the conditions that launch the same automation unnecessarily. The administrator should review entry criteria, whether the Flow runs every time a record is updated or only when conditions become true, and whether the Flow changes fields that retrigger other automation. Before-save flows may also be more efficient for same-record updates in appropriate scenarios. Dashboards, Campaigns, and the Recycle Bin are unrelated. Careful automation design reduces recursion, unexpected updates, and performance issues.