ADM-201 Exam Dumps - Salesforce Administrator Questions and Answers

For an AI agent to provide " complete and accurate " support, it needs access to a unified, 360-degree view of the customer data. Data Cloud is the critical prerequisite because it ingests, harmonizes, and unifies data from multiple sources (Salesforce, external databases, legacy systems) into a single " Unified Profile. " When Agentforce is " grounded " in Data Cloud, it can reference real-time customer interactions, purchase history, and cross-channel behavior that might not exist in a single Case or Contact record. Without Data Cloud, the agent ' s knowledge is limited to siloed data, which increases the risk of providing incomplete or irrelevant answers. While Console layouts (Option B) and intake methods (Option A) are important for the UI, they do not provide the data foundation necessary for advanced AI reasoning.

Access to the Service Console and other advanced Service Cloud features (like Entitlements or Knowledge) requires a specific Feature License called the Service Cloud User. Even if a user ' s profile has the " Manage Cases " permission, they will not be able to access the specialized Console app unless the " Service Cloud User " checkbox is selected on their individual User record. This is a common administrative step when onboarding new support staff. Permission sets (Option B) grant functional permissions but cannot grant feature licenses. Assigning a " Platform User License " (Option D) would actually restrict them, as that license type does not include access to standard CRM objects like Cases or the Service Console.

When a user needs to be temporarily prevented from logging in—but their records, role, and historical data need to remain intact—the best practice is to Freeze the user. Freezing an account stops the user from accessing the system immediately without " Deactivating " them. Deactivation can be problematic if the user is a " running user " for dashboards or is part of active hierarchy logic that might break if the account is disabled. Freezing is a simple " one-click " action on the user record. Reassigning the license (Option A) would require deactivating the user first. Changing login hours (Option B) or IP addresses (Option D) at the profile level would impact all users assigned to that profile, not just the individual manager on leave. Freezing provides a targeted and temporary solution for managing individual user access.

In the Salesforce Setup menu, Company Settings (formerly Company Profile) is the central location where global organizational parameters are managed. This section contains several key settings. Under Company Information, the admin can view the Org ID, default time zone, and primary currency. The Fiscal Year settings allow the admin to define whether the organization follows a standard Gregorian calendar or a custom fiscal cycle. Business Hours are used to define the working times for the organization, which is critical for calculating milestones in Service Cloud or escalation rules. If Multi-Currency is enabled, this is also where exchange rates and active currencies are managed. Viewing and configuring these settings is a foundational task for any Platform Administrator, as they establish the baseline for how data is interpreted and how time-based automation functions across the entire instance. Ensuring these are correct is vital for accurate financial reporting and maintaining service level agreements (SLAs).

To create a " guided " experience combined with " routing and authorizations, " a Platform Administrator should leverage the power of Flow Builder and the Approval Process engine. Flow Builder is used to create the user-facing interface (Screen Flow) that guides the employee through the expense report submission, ensuring all necessary data is collected in a structured way. This replaces a static page layout with a dynamic, step-by-step wizard. Once the data is captured and the record is created, the Flow can automatically submit the record into an Approval Process. The Approval Process then handles the " routing and authorizations " by sending the report to the appropriate manager or director for sign-off. While Quick Actions (Option B) can launch flows, they are a entry point rather than the logic engine itself. Validation Rules (Option A) only prevent errors but do not guide users or route records. Together, Flow and Approvals provide a seamless end-to-end automation for complex business requirements like expense management.

Agentforce is built to be dynamic, meaning it doesn ' t just follow a static script but rather " reasons " through a problem using an agentic loop. The feature that directly allows an agent to adapt its behavior and take specific, real-time steps based on customer input is Custom Actions 3 . When a customer provides information—such as a specific order number or a request to change an address—the agent identifies the user ' s intent and selects the most relevant action to execute 4 . These actions can be powered by Flows, Apex, or Prompt Templates, giving the agent the ability to interact with Salesforce data in real-time. While Data Cloud (Option A) provides the data foundation for grounding, it is the actions themselves that define the agent ' s behavioral capabilities 6 . Screen flows (Option C) provide a guided UI for humans, but custom actions are what allow the agent to function autonomously 7 . Tableau (Option D) is an analytics tool and does not drive real-time agent behavior 8 .

The Kanban view provides a visual representation of a set of records, such as an opportunity pipeline, organized by a specific field like " Stage " . It allows sales teams to see all their deals as cards in columns. The primary benefit of Kanban is its " drag-and-drop " functionality, which lets users move a card from one column to another to automatically update the stage, effectively " moving opportunities forward " with minimal effort. While reports (Option A) and dashboards (Option B) provide visual summaries, they do not allow for the interactive, one-click record updates that the Kanban view offers11. Standard list views (Option D) show data in a grid format which is less visual for tracking pipeline progress compared to the column-based Kanban layout.

A Validation Rule is the only way to enforce conditional requirement logic based on both record data (the stage) and user data (the user ' s profile or role). To achieve this, the Platform Administrator would write a formula that checks three things: if the Stage is " Negotiation, " if the Amount field is blank, and if the user is not a manager. The formula would look something like: AND(ISPICKVAL(StageName, " Negotiation " ), ISBLANK(Amount), $Profile.Name < > " Sales Manager " ). This allows the system to block standard sales users from saving the record without an amount, while the exception for the manager ' s profile allows them to bypass the requirement. Making the field required on the page layout (Option A) would affect all users equally, failing to meet the requirement for managers. Assigning the Admin profile to managers (Option B) is a major security risk and violates the principle of least privilege.1

The Lightning App Builder includes a built-in Analysis tool (often referred to as Page Analysis or Analytics) that provides administrators with a performance score for a record page. This tool evaluates the page ' s metadata and components to identify factors that contribute to slow load times, such as having too many fields in a single section, using complex related lists, or including multiple heavy Lightning Web Components. It provides specific suggestions, such as using " Dynamic Forms " to break up the page or moving less-used components into separate tabs to improve the " time to interact " for the user. The Lightning Usage App (Option B) provides broad metrics on adoption and browser usage across the whole org but does not offer granular, component-level performance analysis for a single record page. Visibility Rules (Option C) are for showing/hiding content, not for technical performance auditing.

Case Escalation Rules are used in Service Cloud to ensure that cases are handled within specific timeframes, helping organizations meet their Service Level Agreements (SLAs) 23232323232323 . When a case meets the criteria defined in an escalation rule and remains unresolved for a specified period, the system can perform two primary automated actions:

Reassign the Case: The rule can automatically transfer ownership of the case to another user or a specific queue (e.g., a " Tier 2 Support " queue) to ensure it gets specialized attention 242424242424242424 .

Send Email Notifications: The system can send alerts to the new owner, the current owner, or up to five additional email addresses to notify management that a case has escalated .

While administrators often use other tools like Flow Builder to change the " Case Priority " (Option B) or " Reopen " a case (Option C), these are not standard features within the Escalation Rule interface26. Escalation rules focus specifically on the routing and notification aspects of case management to prevent tickets from " sitting " too long without a response .