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

In Salesforce, Support Settings is the primary configuration page for determining how the Service Cloud handles automated case updates. This section allows a Platform Administrator to define the " Default Case Owner " and the " Automated Case User. " The Automated Case User is the user listed in the Case History for automated actions, such as those triggered by assignment rules, escalation rules, or Email-to-Case. If the business sees an " unexpected " user name in the Created By or Last Modified By fields during these automated processes, it is usually because this setting is pointing to a specific administrator or a system user. By updating the Automated Case User to a dedicated " Integration User, " the admin ensures that the audit trail clearly distinguishes between manual edits made by staff and automated updates made by the system. This provides better clarity for the support team and prevents confusion regarding who is responsible for specific record changes.

To ensure that a field is populated on every single record, regardless of how it is created (manually, via API, or through an integration), the best method is to make the field universally required at the field definition level. When a field is marked as " Required " in the Object Manager, the Salesforce database will reject any attempt to save a record if that field is empty. While requiring a field on a Page Layout or Record Type (Option B) provides a good user experience for manual entry, it does not prevent records from being created without that data via the API or background processes25. Using a flow (Option A) to update the field is reactive rather than preventative26. Universal requirement is the most robust way to maintain data integrity for critical fields like " Billing System " that are essential for reporting and external system alignment.

To ensure data integrity and guide sales reps through a structured process, a Platform Administrator should use a combination of tools. Opportunity Path (Option C) provides a visual representation of the stages and allows the admin to highlight " Key Fields " and " Guidance for Success " for each stage, making it clear what information is needed to progress. To enforce the entry of that data, Validation Rules (Option D) are used to prevent a user from moving to the next stage if specific fields are blank (e.g., AND(IsChanged(StageName), IsBlank(Discovery_Notes__c))). Additionally, marking fields as required on the Page Layout (Option A) ensures that the most fundamental data points are always captured. While Flow (Option B) can perform many tasks, it is not the primary way to mark fields as " required " in the UI. " Guided Selling " (Option E) is a specific term often associated with Salesforce CPQ rather than standard Opportunity management. Using Path, Validation Rules, and Page Layout requirements provides a robust framework for managing the sales lifecycle effectively.

When an administrator needs to extract a specific subset of records (e.g., Opportunities filtered by stage and date) with specific fields, the Data Loader is the most appropriate tool . Data Loader is a client application that allows for bulk operations, including " Export " and " Export All " 43. It allows the administrator to write a SOQL (Salesforce Object Query Language) query or use the built-in query builder to apply filters, such as StageName = ' Closed Won ' and CloseDate = LAST_90_DAYS44. The Data Import Wizard (Option B) is primarily used for importing data and has very limited export capabilities, usually confined to simple CSV samples45454545. The Data Export Service (Option D), also known as " Weekly Export, " is designed for full backup purposes; it exports the entire database into zip files and does not allow for specific filtering of records or fields for a quick ad-hoc report . Data Cloud (Option C) is a large-scale data platform and is overkill for a simple file export task47. Thus, for targeted, field-specific exports of 90 days of data, Data Loader is the standard choice .

The Data Import Wizard is the most efficient and user-friendly tool for importing a relatively small number of records (up to 50,000) when those records involve standard objects like Accounts and Contacts simultaneously. A key advantage of this tool is its built-in capability to handle " Account and Contact " imports in a single pass, which includes automatic matching to prevent duplicates based on name or email. For a volume of 300 records, the browser-based wizard is much faster to set up than the Data Loader, as it does not require a separate installation or complex CSV mapping for simple standard objects. While the Data Loader (Option D) and Dataloader.io (Option C) can handle this volume, they are typically preferred for much larger datasets (up to 5 million records) or more complex custom objects. The " Wizard " provides a guided experience that is ideal for sales reps or administrators performing routine data entry tasks.

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.

Salesforce allows for the creation of multiple Business Hours records to support global teams working in different time zones. To solve the requirement for Ursa Major Solar, the Platform Administrator should create two distinct sets of business hours: one for " Pacific Support " (9 AM - 5 PM PT) and one for " Eastern Support " (9 AM - 5 PM ET). This is essential because Business Hours are used by the system to calculate escalation rules and milestones correctly. For example, an escalation rule for an Eastern-based case 1should start counting at 9 AM ET, not 9 AM PT. Adjusting the current record to " accommodate " both (Option A) would result in a 12-hour window that doesn ' t accurately reflect either team ' s true availability. Users cannot manually set their own business hours (Option B) in a way that affects system automation. Creating one set per time zone ensures that the support team ' s performance metrics and automated routing are accurate and localized.

In Salesforce, a flow must be Active for it to execute in a production environment. When an administrator builds or updates a flow, it is saved as a new version. Even if the logic is perfect and passes all debug tests, the flow will not run for end-users unless the administrator explicitly clicks the " Activate " button. If a flow is intended to create records but nothing is happening, the first troubleshooting step is always to verify the status in the Flow Builder or the Flows list in Setup. A flow version that is simply " Saved " but not " Active " will remain dormant. Option D is unlikely because the Flow Builder usually prevents saving a record-triggered flow without a trigger defined. Option C ( " Read Only " ) is not a state that would prevent a flow from running. Option B ( " Flow URL " ) only applies to specific types of screen flows launched via custom links, whereas the question implies a general failure of the automation to execute.

Flow Builder is the recommended tool for automating updates to multiple related records based on a change to a single record. A " Record-Triggered Flow " can be configured to execute whenever an Opportunity is updated to " Closed Won " . The flow can then find all other Opportunities related to the same Account where the " IsClosed " field is false, and use an Update Records element to set their stage to " Closed Lost " . Outbound Messages (Option B) are used for notifying external systems, not for internal data updates 31 . Flow Orchestration (Option C) is designed for multi-user, complex business processes and would be overly complicated for this simple record update 32 . Quick Actions (Option D) require a user to click a button, which does not meet the requirement for automatic rendering upon the stage change 33 .

When an object ' s Organization-Wide Default (OWD) is set to Private, the " Record Sharing " engine must be used to grant additional access.

Sharing Rules: These allow the administrator to grant lateral access to records based on criteria or ownership (e.g., share all " Large Deals " with the " Strategic Sales " group).

Role Hierarchy: This standard feature automatically grants vertical access, ensuring that managers and users higher in the hierarchy can see and edit records owned by their subordinates.

Profiles (Option D) control what actions a user can perform (Create, Read, Edit) but do not grant access to specific records that the user does not own in a Private model. A Sharing Set (Option B) is a specific feature used for Experience Cloud (Community) users to grant them access to records related to their account and is not used for standard internal sales users.

In Salesforce, security restrictions like Login Hours and Login IP Ranges are managed at the Profile level. When these are configured on a profile, they are strictly enforced; if a user attempts to log in outside of the allowed hours or from an unauthorized IP address, the system will deny access entirely. This is one of the most robust ways to secure an organization against unauthorized access. Company Settings (Option A) can set " Trusted IP Ranges " for the whole org, but these only bypass multi-factor authentication; they do not restrict login. Roles (Option B) control record visibility, not system access. While Permission Sets (Option D) can grant many permissions, Login Hours and IP Ranges remain a core profile-level security setting.

For an administrator who needs to deliver high-quality dashboards " quickly " and " doesn ' t know where to start, " the AppExchange is the best resource. Salesforce Labs provides several free, pre-configured dashboard packages (like the " CRM Dashboards " ) that include standard components for sales pipeline, lead tracking, and case management. These packages serve as an excellent baseline that can be installed in minutes and then customized to fit the specific needs of Cloud Kicks. Manually creating everything (Option D) is time-consuming. Einstein Analytics (Option B) is a separate, more complex product that requires extra licensing and setup. Option A is too narrow, as it focuses specifically on " Field Service " rather than general sales and service visibility.

When naming actions for an AI agent, consistency is key to helping the Large Language Model (LLM) categorize and understand the available tools. Following a consistent naming convention, such as starting all retrieval actions with the verb " Get, " allows the agent to more easily map user intent (e.g., " I need information about... " ) to the appropriate action. This reduces ambiguity during the reasoning phase of the agentic loop. Using inconsistent verbs like Find, Retrieve, or Identify (Option D) can confuse the model regarding which action is most appropriate for a given task. Removing verbs entirely (Option A) makes it harder for the model to distinguish between an action (doing something) and a data object (a thing). Adding " Salesforce " (Option B) is generally redundant as the agent ' s context is already within the Salesforce environment.

To " predict upcoming revenue " and " benchmark performance, " Salesforce provides the Collaborative Forecasting feature.

Forecasting (Option B): This tool allows managers to see their pipeline summarized by time period (quarters) and category. It provides a real-time view of what the team expects to close.

Opportunity Stages (Option D): Forecasting relies directly on the Opportunity Stage. Each stage is mapped to a " Forecast Category " (e.g., Pipeline, Best Case, Commit, Closed). By accurately defining these stages and their associated probabilities, the Platform Administrator ensures that the forecast reflects a realistic revenue prediction.

Sales Quotes (Option A) are for generating customer-facing documents. List Views (Option C) are for managing individual records but do not provide the multi-quarter aggregation and benchmarking capabilities required by the sales director.

To provide reps with an " easy way " to perform a repetitive sequence of manual tasks, Macros are the ideal solution. A Macro allows a user to perform multiple steps—such as changing a Case Status, reassigning the Case Owner, and sending a pre-written email—with a single click. When combined with Quick Actions, Macros can navigate the user interface, populate fields, and submit changes automatically. This significantly reduces manual data entry and ensures that the company ' s required support process is followed consistently. Case Assignment Rules (Option A) and Autolaunched Flows (Option D) are fully automated and trigger on save, which might not be appropriate if the rep needs to decide when to trigger the support request. Quick Text (Option C) only assists with typing but does not automate field changes or ownership transfers.

A Chatter Stream is a custom feed that users (or administrators) can create to consolidate updates from multiple sources. You can combine feeds from specific groups, individual people (like the CEO), and specific records into a single view. This allows users to stay organized and monitor diverse sets of information in one place without having to navigate between different groups or records. A Chatter Group (Option A) is for a specific set of members. A Daily Digest (Option B) is an email summary. A Chatter Feed (Option C) is a general term for the individual lists of updates but does not natively allow for the targeted " multi-source " consolidation that a Stream provides.

Agentforce is designed to handle multi-step processes that require reasoning and adaptation. Unlike traditional automation (like Workflow or simple Bots) that follows a linear, " If-This-Then-That " path, an Agentforce agent uses generative AI to understand user intent and choose the best sequence of actions to reach a goal. If a customer ' s request changes mid-conversation or requires the agent to check multiple systems and make a judgment call, the agentic loop allows it to adapt its behavior in real-time. Single-step processes (Option A) or tasks without decision-making (Option D) are better handled by standard Flow or Macros, which are more cost-effective for simple tasks. Static document generation (Option B) is a fixed output task. Agentforce ' s true value lies in managing the " gray areas " of business processes where human-like flexibility is needed.

In Salesforce, a many-to-many relationship allows each record of one object to be linked to multiple records of another object and vice versa. This is achieved by using a Junction Object. A junction object is a custom object that sits between the two objects you want to relate. To implement this correctly, the administrator must follow two specific steps: first, create the custom object to serve as the " junction " ; second, create two Master-Detail relationship fields on that new junction object. One master-detail field points to the first custom object, and the second points to the other. Because these are master-detail relationships, the junction record ' s visibility and deletion behavior are controlled by its parents. This structure allows for powerful reporting and roll-up summaries on both parent objects. Using simple lookup relationships (Option D) would not enforce the strict data integrity or the specific roll-up capabilities that define a true many-to-many relationship in the Salesforce architecture.

Delegated Administration is a powerful feature that allows a System Administrator to pass off specific administrative tasks to non-admin users without granting them the full " Modify All Data " permission. However, there are strict security boundaries to what a delegated admin can do. One of the most critical limitations is that delegated administrators cannot modify permission sets. They are primarily intended to manage users within specific roles, reset passwords, and manage specific custom objects. While they can assign users to certain profiles that have been explicitly allowed in the Delegated Administration group configuration, they are not permitted to manage the broader security architecture of the org, such as Permission Sets or Field-Level Security (Option B). This ensures that while junior staff can handle day-to-day user maintenance (like unlocking users, contrary to Option A), they cannot inadvertently elevate their own permissions or those of others through permission set manipulation.