ADM-201 Salesforce Certified Platform Administrator (Plat-Admn-201) Free Practice Exam Questions (2026 Updated)

In Salesforce, dashboards can be configured to run as a specific user, known as the Running User. This user ' s security settings determine which data is visible to anyone viewing the dashboard. To allow users with restricted record access (due to a Private sharing model) to see company-wide totals, the Platform Administrator should set the dashboard to " Run as a specified user " who has " View All " permissions or is high enough in the role hierarchy to see all records. This creates a " Static Dashboard. " While the viewers cannot click into individual records they don ' t own, they can see the summarized totals and charts for the entire organization. Using a Dynamic Dashboard or filtering by role (Option B) would still respect individual sharing and hide data. Changing folder settings (Option D) only affects who can open the dashboard, not the data displayed within it.

In the Lightning App Builder, Component Visibility Filters allow an administrator to show or hide parts of a record page based on specific criteria, such as the user ' s profile, a field value, or the record type. This is the best way to make pages " dynamic. " For example, the administrator can configure a " Financial Details " component to only appear when the user viewing the case has the " Finance User " profile, or hide a " Recall Instructions " component unless the " Case Reason " is set to " Product Defect. " This prevents " information overload " by ensuring that users only see the tools and data relevant to their specific role or the current state of the record. Simply deleting components (Option D) or removing fields (Option C) would affect all users equally, failing to provide role-specific utility. Component visibility creates a personalized, streamlined experience that improves user productivity and reduces clutter on complex record pages.

While modern tools like Flow Orchestration exist, the standard and most robust way to handle complex, criteria-based routing for record sign-offs is an Approval Process. An approval process can handle many different " Approval Steps, " and each step can have its own " Step Entry Criteria. " For instance, Step 1 could route to Leader A if the region is " North, " while Step 2 routes to Leader B if the region is " South " and the discount is > 20%. With 30 potential sets of criteria, the administrator can build a comprehensive process that automatically identifies the correct approver without user intervention. Using an email button (Option A) or a manual form (Option D) is prone to human error, as the salesperson might select the wrong leader. A record-triggered flow (Option C) can launch an approval process, but the complex multi-step routing logic is best managed within the Approval engine itself to maintain a clear audit trail of who approved what and why.

In Salesforce Lightning Dashboards, Text Widgets allow administrators to add descriptive text, titles, and custom narratives directly alongside data visualizations. This is a key feature for " telling a compelling data story " because it allows the admin to provide context, explain the significance of certain charts, or provide instructions and motivational messages to the team. By adding text widgets, a dashboard moves from being a collection of raw charts to a guided analytical experience. The Highlights Panel (Option C) is a feature of Record Pages, not Dashboards. Assigning tasks (Option B) or sending mass emails (Option D) are communication methods but do not enhance the visual or narrative quality of the dashboard itself. Text widgets empower administrators to highlight trends and call out specific goals, making the data more actionable and easier to interpret for the sales reps.

A common cause of errors in an Approval Process is a breakdown in the " Approver " chain. If an approval step is configured to route to a specific user or a manager who has been deactivated, Salesforce will throw an error when the current step tries to advance. The Platform Administrator should check the " Next Approver " field on the record or the step definition in Setup to ensure the target user is active and has a valid Salesforce license. While field visibility (Options B and C) is important for the user experience, missing field access typically doesn ' t " error out " the approval engine itself; it just prevents the user from seeing the data. Checking for inactive users is the first step in troubleshooting runtime errors in automated routing processes.

In the Salesforce Lightning Experience, the buttons and actions that appear in the header (Highlights Panel) of a record are controlled by the Salesforce Mobile and Lightning Experience Actions section of the Page Layout. If a specific action like " Log a Call " is missing, it is usually because it has not been dragged into this specific section in the Page Layout editor. While standard actions sometimes appear in the Activity component (Option A), they are explicitly configured for the header via the Page Layout. There is no specific " Log a Call permission " (Options C and D) that would hide only that button; if a user has permission to create Tasks, they generally have the ability to use the Log a Call feature if it is present on the layout.

To manage a structured, multi-step sign-off requirement like the one described by the finance team, the Approval Process is the standard and most effective tool. An approval process allows an administrator to define a sequence of " Approval Steps. " In this scenario, Step 1 would be configured to route the request to the Seller ' s Manager. Only after the manager approves does the record move to Step 2, which would be configured to route the request to the specific Finance Team member. This ensures the " manager first " logic is strictly enforced. Approval processes also provide a native " Approval History " related list, which serves as a vital audit trail for the finance team to verify that all necessary signatures were obtained before the deal was finalized. Using a screen flow (Option A) or quick actions (Option C) would lack the built-in locking mechanism and formal status tracking that the Approval engine provides. A Lightning Web Component (Option B) would require significant custom coding for a process that is easily handled by standard " click-not-code " configuration.

In Salesforce, certain dependencies prevent a user record from being deactivated. One of the most common blockers is if the user is the Running User of a Dashboard. Because the dashboard relies on that user ' s security context to display data to others, deactivating them would break the dashboard. To resolve this, the administrator must first change the running user of the dashboard to someone else. Being part of an Opportunity Team (Option C) or Account Team (Option D) does not prevent deactivation; the user simply remains on the team but is inactive. For Assignment Rules (Option B), while you cannot delete a user in a rule, deactivation is usually permitted, though it may result in an error when the rule attempts to assign a record to the inactive user. However, the " Running User " requirement is a hard system block.

When building prompt templates within the Prompt Builder, the most direct way to inject specific record data into the AI ' s instructions is through Merge Fields. Much like an email template or a mail merge, merge fields allow the administrator to reference specific fields from the object in context—in this case, the Case object. For example, an administrator might use {!$Input:Case.Subject} or {!$Input:Case.Description} within the prompt template. When the agent runs, it replaces these placeholders with the actual data from the specific case record being viewed. This ensures that the AI has the " grounding " information it needs to generate an accurate and relevant summary. While Flows (Option A) can be used for more complex data retrieval, Merge Fields are the standard, low-code tool for simple record-to-prompt data population. Agent Instructions (Option C) provide the " how-to " logic for the AI but do not themselves represent the dynamic data points from the Salesforce database.

The Setup Audit Trail is the primary tool for tracking administrative and configuration changes within a Salesforce organization. It records a history of modifications made by any administrator, including the date and time of the change, which user made it, and exactly what was altered (e.g., creating a new field, changing a profile permission, or modifying a workflow rule). The history is available for the last six months of activity. Health Check (Option A) is a security tool that compares your settings against Salesforce standards. History Tracking (Option C) and Feed Tracking (Option D) are used to track changes to records (like an Account ' s phone number), whereas the Setup Audit Trail is dedicated to tracking metadata and system configuration.

In Flow Builder, the most efficient and user-friendly way to handle dynamic user interfaces is through Component Visibility. This feature allows an administrator to set logic on individual screen components (like a picklist) so they only appear when specific criteria are met. In this scenario, the administrator would select the " Specific Search Engine " picklist component within the Flow Screen and configure its visibility to show only when the " Lead Source " screen component equals " Search Engine. " This provides a " clean " user experience where the form adapts in real-time to the user ' s input without requiring the user to navigate to a new screen or trigger a validation error. Validation rules (Option D) are reactive and only tell the user they made a mistake after they try to save, whereas conditional visibility is proactive. Option B is inefficient as it would require multiple screens and complex branching logic, whereas component visibility handles everything within a single screen element.

A Master-Detail Relationship is a tight coupling between two objects that provides several unique functionalities:

Master Object Types: The master can be either a standard object (like Account) or a custom object (Option B).

Roll-up Summaries: This relationship type is the only one that natively supports Roll-up Summary fields, allowing the master record to calculate counts, sums, or averages of fields on the detail records (Option C).

Ownership and Security: The detail record inherits its owner and its security/sharing settings from the master record. Consequently, there is no " Owner " field on a detail record; it is always owned by the owner of the master (Option D).

Option A is incorrect because detail records cannot have independent permissions. Option E is incorrect because an object can only have a maximum of two master-detail relationships. This relationship is ideal for parent-child scenarios where the child ' s existence is entirely dependent on the parent.

When an administrator needs to perform a " cleanup " of existing data in bulk, a Schedule-triggered flow is the most efficient choice. This type of flow can be configured to run once (or on a recurring schedule) and process all Lead records that meet the " inconsistent " criteria (e.g., Lead Source equals ' Website ' or ' Online ' )46. The flow can then automatically update those records to the standard " Web " value. A Record-triggered flow (Option B) only works on records as they are being created or updated, so it would not fix historical data unless every record was manually touched Screen flows (Option D) require manual user interaction for each record. 53Segment-triggered flows (Option A) are used in Data Cloud marketing conte54xts rather than standard core record cleanup.

Salesforce Critical Updates (now often called Release Updates) can significantly change the behavior of the platform, potentially impacting custom code, integrations, or existing automation. The best practice for any Platform Administrator is to activate and test the update in a Sandbox environment first. This allows the administrator to identify and resolve any breaking changes without disrupting the live business operations in Production. Only after the update has been thoroughly vetted and all necessary adjustments have been made should the update be activated in the Production environment. Allowing an update to " auto-activate " (Options A and D) is risky because it removes the administrator ' s control over the timing and testing of the change. Activating directly in Production (Option B) bypasses the essential quality assurance steps that are fundamental to professional org management.

Omni-Channel is a comprehensive service tool designed to route work items (like Cases, Leads, or custom objects) to the most available and qualified support agents in real-time. Unlike Case Assignment Rules, which are often static and require administrative intervention to update complex logic, Omni-Channel allows for more dynamic management through the use of Queues and Presence Statuses. By using Omni-Channel, a support manager or " Supervisor " can monitor agent workloads and adjust capacity or move people between service channels without needing to modify the underlying system configuration or involve the Platform Administrator. It supports various routing models, such as " Least Active " or " Most Available, " ensuring that work is distributed fairly and efficiently. This flexibility is vital for growing organizations that need to scale their support operations quickly while maintaining high service levels. Furthermore, it provides the business with the autonomy to manage its workforce effectively, as managers can see who is logged in and what they are working on, allowing for immediate adjustments to handle spikes in case volume.

The Activity Timeline is a standard Lightning component that displays open tasks, upcoming events, and past activities (like logged calls or sent emails) in a chronological view. If this timeline is missing from an Account page, it is usually because the component has been removed from the Lightning Record Page layout. To fix this, the Platform Administrator should open the Account record in the Lightning App Builder. From the list of standard components on the left, the admin must drag the Activities component onto the page canvas—typically in the right-hand column or a dedicated tab. Once the page is saved and activated, the timeline will be visible to users. Visibility of the timeline is a layout configuration, not a specific " Edit access " permission (Option B). Running a report (Option C) might confirm if data exists, but it won ' t fix the UI issue. There is no " button " for the Activity Timeline in the Object Manager (Option D); it is managed strictly as a component within the App Builder.

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

Creating effective Agentforce prompts requires a focus on clarity and simplicity to ensure the Large Language Model (LLM) follows instructions accurately. According to Salesforce best practices, administrators should use natural, easy-to-understand language and provide clear, concise instructions1919. This approach helps the AI accurately reason through the task without becoming confused by overly complex or nested logic (Option A). While technical accuracy is important, relying heavily on jargon or abbreviations (Option B) can sometimes lead to unexpected results if the LLM interprets those terms differently in various contextsFurthermore, providing high-level theoretical concepts (Option C) often results in vague or " creative " answers that may not be helpful for technical troubleshooting, which requires specific and actionable steps22. Using direct instructions like " Summarize the issue in three bullet points " is more effective than broad guidelines.

In Salesforce, access to reports and dashboards is determined by the folder in which they are stored. If a dashboard is in a shared folder, anyone with access to that folder can view it. To " temporarily remove " a specific dashboard from public view without affecting the rest of the folder ' s contents, the Platform Administrator should edit the dashboard ' s properties and move it to a private dashboards folder (such as " My Private Dashboards " ). Once moved, only the administrator (and those with high-level " View All Data " permissions) can see it while the changes are being made. Removing view access to the shared folder (Option A) would hide all dashboards in that folder, which is not the goal. Permission sets (Option C) control functional access (the ability to create or edit dashboards) but not individual record/dashboard visibility. Private groups (Option D) are for Chatter collaboration, not for managing dashboard folder security.