ADM-201 questions and answers

In Salesforce, when a Platform Administrator changes a field's data type from Auto Number to Text, the operation is considered "safe" regarding data retention. The existing values that were automatically generated by the system (e.g., "INV- 1001") will remain unchanged and stay within the field as static text strings 12. However, once the change is saved, the system will no longer increment or automatically generate new numbers for future records; users will have to enter data manually. It is important to note that
the reverse operation-changing a Text field to an Auto Number-is different, as it would require the administrator to decide whether to overwrite existing data or only number new records 14. Options B, C, and D are incorrect because Salesforce explicitly supports this specific conversion without deleting or fundamentally transforming the existing data into a different format other than plain text.

In Salesforce, access to reports and dashboards is controlled at the Folder level. Even if a user has the direct URL to a dashboard, they cannot view it unless the folder containing that dashboard has been shared with them. When a user receives the "We couldn't find the record" error, it typically means they lack View access to the folder. To resolve this, the owner of the folder (or an administrator) must go to the folder's sharing settings and explicitly add the sales manager, their role, or a public group they belong to.
Options A and B are less likely because standard sales profiles usually have the general "Run Reports" and "View Dashboards" permissions; the issue here is specific record-level access to that folder's content. Option C
is a specific state of a folder (Private to the creator), which is essentially the same as saying access has not been granted to others.

When users click the "New Report" button, they are presented with a list of Report Types, which act as templates determining which objects and fields are available for the report. Often, an org has many standard report types that are irrelevant or confusing to the average user. To "limit the kinds of reports" and simplify the user experience, a Platform Administrator can use the Select Report Types to Hide feature in the Report and Dashboard Settings. By hiding unnecessary or redundant report types, the admin ensures that users only see the specific templates that align with company reporting standards. This reduces the risk of users creating inaccurate reports using the wrong data models. Report Folder Sharing (Option B) controls who can view or edit existing reports, but it does not restrict the creation of new ones from specific templates. While creating Custom Report Types is a way to define what data is available, the specific act of "limiting" the visible list is handled by the "Hide" functionality.

The foundation of Salesforce data security is the Organization-Wide Default (OWD). To ensure that users can only see their own records (and those above them in the hierarchy), the administrator must set the OWD for the object to Private. When an object is private, a user can only see records they own. When that user runs a report, the report engine automatically respects these sharing settings and only displays the records the user is authorized to see. This is a much more secure and scalable solution than creating separate reports for every user (Option C).
Option A (Public Read/Write) would allow everyone to see everything, violating the privacy requirement.
Option D (Apex sharing) is a complex coding solution that is unnecessary when the standard "Private" sharing model fulfills the requirement through simple configuration.

To manage different business requirements for a single object like Opportunities, Salesforce utilizes a combination of Record Types and Sales Processes. A Sales Process is a specific feature for the Opportunity object that allows an administrator to select which "Stage" picklist values are visible. In this scenario, the admin would create one Sales Process for "Business" (4 stages) and another for "Partner" (8 stages). Once these processes are defined, they are linked to Record Types. Record Types are the engine that allows different users to see different Page Layouts and picklist options based on the "type" of record they are creating. This architecture ensures that users working on Partner deals are guided through the appropriate eight stages and see the relevant fields on their layout, while Business users have a streamlined four-stage experience. This separation is critical for maintaining data integrity and ensuring that the reporting for each pipeline is accurate. It prevents confusion by only showing users the options that are relevant to the specific context of the deal they are managing.

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.

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 action 13.
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 process 15. 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 user 17.

A Validation Rule is the correct tool for enforcing conditional data entry requirements. When a business rule dictates that a field (Lead Source) must be populated only when another field (Stage) reaches a specific value (Closed Won), a validation rule can evaluate this logic every time a record is saved. The formula would check if the Stage is "Closed Won" and simultaneously check if the Lead Source field is blank. If both conditions are true, the system displays an error message and prevents the user from saving the record. This ensures 100% data compliance. Dependent picklists (Options A and D) are used to filter available options in one list based on the selection of another, but they cannot "require" a value to be present based on a stage change in the same way a validation rule can. Making the stage "Read Only" (Option B) would prevent users from ever winning a deal. Validation rules are the standard method for maintaining data quality during critical transitions in the sales lifecycle.

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.

Opportunity Contact Roles allow sales reps to link multiple Contacts to a single Opportunity and assign a specific "Role" to each, such as "Decision Maker," "Influencer," or "Economic Buyer." This provides the visibility needed to understand the "buying committee" for a deal. It also allows for the designation of a "Primary Contact." Opportunity Teams (Option A) are used to track internal staff working the deal. Account Teams (Option B) track collaboration at the account level but are not deal-specific. Standard fields (Option C) are insufficient for tracking a "one-to-many" relationship between an opportunity and multiple contacts
with unique roles. Contact Roles are the standard feature designed exactly for stakeholder management in the sales process.

There are two primary ways to display different picklist values to different groups of users. The first, and most common, is using Record Types (Option C). A single picklist field can have its available values filtered at the Record Type level. By creating a "Sales" record type and a "Marketing" record type, the admin can select which values are visible for each. These record types are then assigned to the respective users' profiles. The second method (Option D) involves using different Page Layouts and two separate picklist fields. In this scenario, the admin creates two distinct fields (e.g., "Sales Category" and "Marketing Category") and places only the relevant field on the page layout assigned to that specific team. This is less common but effective if the data needs to be stored in entirely different buckets. Option B is incorrect because profiles themselves do not filter picklist values; they only control which record types a user can
access.

Account Teamsare designed specifically for "collaborative selling," allowing multiple users to work together on a single Account. By using Account Teams, an administrator can define specific roles (e.g., Sales Engineer, Support Rep) and grant them varying levels of access (Read/Write or Read Only) to the Account and its related Opportunities and Case. To meet the manager's requirement of "streamlining" and "automatically adding" members, the administrator should encourage users to set upDefault Account Teams. Once a user defines their default team in their personal settings, they can click a single button to add that entire team to any Account they own. Sharing Rules (Option B) are typically too broad for this requirement because they apply to all records meeting a criteria, rather than specific collaborative groups 61. The Role Hierarchy (Option C) provides vertical access but doesn't easily handle the horizontal, project-based access required for support reps and engineers working on specific accounts 62. Permission Sets (Option D) grant functional permissions (what a user can do) but do not grant access to specific data records in a collaborative way 63.

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).

When a specific user encounters an error that an administrator cannot replicate, the most effective troubleshooting technique is to "Login as" that user. This feature, which must be enabled in the organization's login policies, allows the administrator to see exactly what the user sees and experience the system through their specific profile, role, and sharing permissions 22. This is vital for identifying issues related to Validation Rules, Field-Level Security, or Record-Triggered Flows that might only trigger under specific user contexts. Logging in as a system administrator (Option A) is ineffective because administrators often bypass certain restrictions that apply to standard users 4. Asking for a password (Option D) is a major security violation and is never required in Salesforce5. By using the "Login as" feature, the admin can pinpoint whether the error is caused by the user's data input or a specific permission conflict assigned to their profile.

Agentforce is designed to handle sophisticated, multi-step business processes that traditionally require human intervention. In a sales organization, a primary use case is Automating Lead Qualification. Unlike basic web bots (Option C) that follow a rigid, pre-defined script, an Agentforce agent can engage in natural language conversations with prospects. It can ask relevant discovery questions, handle objections, and determine if a lead meets the company's "Qualified" criteria based on the information provided. Once qualified, the agent can autonomously update the Salesforce record or even book a meeting for a human sales representative. While AI can assist with content, "automating all marketing content" (Option B) is overly broad and typically handled by specialized marketing tools. Generating cold calls (Option A) involves voice technology and legal complexities that are not the core focus of the Agentforce platform's digital agent capabilities. Lead qualification represents a high-value, repeatable process that perfectly leverages the agent's ability to reason and interact with Salesforce data.

A Dynamic Dashboard is a specific type of dashboard where the data displayed changes based on which user is currently viewing it. By setting the "View Dashboard As" property to "The logged-in user," the dashboard components will respect each individual user's sharing settings, role hierarchy, and record ownership. For example, if a sales rep views a dynamic dashboard, they might only see their own $100k pipeline, while their manager viewing the same dashboard would see the team's combined $1M pipeline.
This eliminates the need for an administrator to create and maintain dozens of identical dashboards for different individuals. Dashboard Filters (Option A) allow users to narrow down data but do not change the fundamental "running user" security context. Setting the dashboard to run as "Me" (the admin) or "Another person" (Options C and D) creates a static view where everyone sees the same data, which is the opposite of providing an individualized view.

For any business process that needs to run at a specific time interval (in this case, "once a week"), a Scheduled flow is the standard tool. A scheduled flow allows the Platform Administrator to define a frequency (Daily, Weekly, or Once) and a start time 57. The flow can then query all relevant Account records and perform the logic of counting open cases and updating the parent record autonomously 58.
Record-triggered flows (Option B) are inappropriate here because the count needs to happen on a schedule rather than being triggered by an individual record edit 59. Autolaunched flows (Option C) must be called by another process, such as a button or Apex, and do not have their own timing mechanism 60.
"Automation event triggered flow" (Option D) is not a standard type of flow used for recurring batch processing

When users share the same profile but require different user interface experiences, Component Visibility is the most effective tool. In the Lightning App Builder, the administrator can select the "Related List" component (or a "Related List - Single" component for Retention) and add a visibility filter. The filter can be set to "User > Permission > Custom Permission" or "User > Profile," but since they share a profile, the best
approach is to filter based on a Permission Set or a specific user field. This allows the Retention list to be visible only to the Client Services team members while remaining hidden for the Customer Support team, even though they are looking at the same record. Page Layout Assignment (Option A) and Record Type Assignment (Option C) are profile-based and would not work since the teams share a profile. Sharing Settings (Option D) control access to the data itself, but the request specifically asks to hide the UI element (the related list).

The administrator's goal is togain a better understandingof current data quality and record completeness issues in Accounts and Opportunities. Creating reports (or dashboards) that highlight blank or missing key fields-using filters like "Field equals (blank)" or formula fields to flag incompleteness-directly assesses the existing data by showing which records lack required information. Why B is correct: Salesforce Trailhead modules on data quality emphasize using reports and dashboards (e.g., Account, Contact & Opportunity Data Quality Dashboard) to identify missing fields and measure completeness before implementing fixes.
Why not the others
A: Exploring AppExchange apps is useful for advanced or ongoing solutions but skips the initial assessment step.
C: Subscribing reps to reports helps with awareness but doesn't provide the admin with an overview of data quality.
D: Making fields required prevents future issues but doesn't reveal current missing data or outdated records. This approach aligns with Salesforce best practices: assess data quality first through reporting, then enforce improvements.