Pass the Salesforce Salesforce Administrator ADM-201 Questions and answers with CertsForce

The Lightning App Builder is the primary tool for creating custom user interfaces in both the desktop and mobile versions of Salesforce. For mobile customization, administrators primarily focus on two page types:

App Page: These are custom " landing pages " or " home pages " for an app. They can contain a mix of components like lists, charts, and flows, and they appear as items in the mobile navigation menu.

Record Page: These allow administrators to customize the layout of a specific object (like an Account or a custom Property record) for mobile users. Admins can use " Component Visibility Rules " to show or hide specific sections when the record is viewed on a mobile device, ensuring a streamlined experience on smaller screens.

There is no such thing as a " User Page " (Option B) in the App Builder. While dashboards can be viewed on mobile, they are created in the Dashboard Builder, not the Lightning App Builder (Option D).

In an agentic loop, the AI agent iteratively tries to solve a user ' s request by calling actions and evaluating the results. If the results of those actions are unsatisfactory (e.g., the data returned doesn ' t answer the prompt or a required input is missing), the agent ' s next logical step is to ask for additional information. By clarifying the user ' s intent or requesting the missing data point, the agent can initiate a new loop with better inputs. Giving up with an error message (Option B) or providing a " best guess " (Option A) are considered failures of the reasoning process. Routing to a live agent (Option C) is an escalation step that typically happens after the agent has failed to resolve the issue even after clarification, or if the user explicitly asks for human help.

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.

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.

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.

Grounding is the process by which an AI agent retrieves and uses specific, trusted data to ensure its responses are accurate and relevant 41 . During this process, Salesforce ' s Einstein Trust Layer performs several critical checks, including identifying Prompt Injection risks 424242 . Prompt injection refers to attempts by a user to " trick " the AI into ignoring its instructions or revealing sensitive data by entering malicious commands into the chat interface 43 . By checking for these risks during the grounding phase, the agent can ensure that the instructions it uses to generate a response remain secure and aligned with company policies 44 . While the agent respects field security, " Encrypted fields " (Option C) are handled at the data access layer rather than as part of the linguistic grounding check 45 . Standard Agentforce agents do not browse the open web for verification (Option D) as they are intended to remain grounded strictly in the company ' s verified internal data 46 .

The Mass Transfer Records tool is a built-in Salesforce feature designed specifically for the scenario of a person leaving the company or changing roles. It allows a Platform Administrator to select a " From " user and a " To " user and then choose specific record types to transfer, such as Accounts and Opportunities. A major advantage of this tool is that it gives the administrator the option to transfer related records (like open opportunities or cases) and keep existing teams (like Account Teams) intact during the move. While Data Loader (Option A) or Dataloader.io (Option B) could technically perform a bulk update of the " OwnerId " field, they require several steps, including exporting data, manipulating CSV files, and re-uploading. The Data Import Wizard (Option D) is primarily for creating or updating records from an external file and does not have a dedicated " transfer " function. Mass Transfer is the fastest and safest standard way to reassign ownership within the Setup menu.

Best practices for Agentforce Action Instructions emphasize clarity, intent, and specific usage scenarios to help the LLM (Large Language Model) understand exactly when and why to trigger an action13. Option B is the best choice because it explicitly defines the Action (create a Case), the Goal (document a customer ' s issue), and the User Intent (formal record of a problem or question)14. High-quality instructions act as a guide for the agent ' s reasoning process15. Vague instructions, like those in Option A or C, may lead to the agent triggering the action at inappropriate times, such as during a simple inquiry that doesn ' t require a formal case. Instructions that focus on " code snippets " (Option D) are less effective because the LLM needs to understand the functional business context rather than the technical implementation details to interact naturally with the user17.

Tasks and Events are both part of the Activity object, but they often require different picklist values for the standard Subject field. To achieve this, the Platform Administrator must manage the picklist values for the Subject field specifically for each record type or activity type. In the Object Manager, under the Activity object (or Task/Event objects individually in some setups), the admin should edit the Subject field. Because Task and Event are distinct entities with their own picklist value sets for the Subject field, the admin can add " Schedule Site Visit " and " Send Contract " to the Task Subject list and " Site Visit " and " Ride Along " to the Event Subject list. This ensures that when a user creates a Task, they only see task-related subjects, and when they create an Event, they see event-related subjects. Option D is incorrect because it would mix all values together, causing confusion for the users. Option A (Predefined Field Values) is used to set a single default value for a field when an action is clicked, but it does not manage the available list of options in a picklist.

A Delegated Approver is a user designated by an individual or an administrator to act on their behalf when an approval request is received. This is particularly useful for planned absences, such as vacations. While the delegated approver has the power to approve or reject a record, they cannot reassign the request to someone else. This is a temporary manual assignment and is different from a Manager (Option D), who is part of the permanent role hierarchy, or a Queue (Option B), which allows a group of people to share approval tasks. There is no feature called an " Approval Rule " (Option A) that handles temporary user reassignment in this manner.