Free Practice Questions for Salesforce ADM-201 Exam

In this scenario, the two teams are " peers " in the role hierarchy (both reporting to the same manager). In a private sharing model, peers cannot see each other ' s records by default. To grant lateral access between these specific groups, an Owner-based Sharing Rule is the most effective solution. The administrator can create a rule stating that any records owned by members of " Role: Sales Team A " should be shared with members of " Role: Sales Team B " with specific access levels (e.g., Read/Write). Hierarchical sharing (Option C) only grants upward visibility to the Manager role, not across to the other team34. Manual sharing (Option D) is inefficient for an entire team35. Criteria-based sharing (Option A) is used when record field values determine access, whereas this requirement is based specifically on who owns the records36.

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.

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.

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 .

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.

In Salesforce reporting, administrators can use relative date and user filters to make a single report template dynamic for every person who views it. By setting the filter to Opportunity Owner (or Order Owner) equals $USER, the report will automatically filter the results to show only those records owned by the individual currently logged in and viewing the report. This is much more efficient than creating separate reports for every rep. While setting the Organization-Wide Defaults to Private (Option C) would restrict general visibility, it does not help if the reps need to be able to see each other ' s data for other business reasons but simply want a " clean " personal view for daily tasks36. Saving the report in a private folder (Option D) only restricts who can see the report itself, not the data contained within it. Using the $USER variable is the standard way to provide personalized, relevant data views in a shared reporting environment.

A Roll-up Summary Field is a powerful feature that calculates values from related records and displays them on a master record. However, this functionality is natively available only on the " Master " side of a Master-Detail relationship. For standard objects, Salesforce provides a built-in Master-Detail-like relationship between Accounts and Opportunities . Specifically, the Account object acts as the master, and the Opportunity object acts as the detail. This relationship allows a Platform Administrator to create roll-up summary fields on the Account to calculate the sum of " Total Opportunity Amount, " the " Minimum Close Date, " or a " Count " of all related opportunities . Other standard objects like Contacts (Option B) and Cases (Option C) have a lookup relationship to Accounts rather than a master-detail relationship, and therefore do not support native roll-up summaries20. Campaigns (Option D) also do not share this specific relationship with Accounts21. If an administrator needs to roll up data from these other objects, they would typically need to use a custom solution like Flow Builder or a third-party app, whereas Opportunities are supported natively out of the box .

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.

When defining Topics for an Agentforce agent, the quality of instructions is vital for ensuring the agent identifies the correct topic when a user asks a question. Best practice includes providing a variety of example user questions (utterances). This helps the agent ' s natural language processing (NLP) model recognize the different patterns and ways a human might phrase a request related to that specific topic. Writing instructions too generically (Option A) can lead to " topic overlap, " where the agent gets confused about which topic to use75. Minimal instructions (Option C) may reduce latency slightly but often result in poor accuracy and failed topic identification76. Using " plain language " is generally preferred over overly " business-specific " jargon (Option D) because the agent needs to match the way customers or employees naturally speak during a conversation

I apologize for that mistake. I understand now that you want the citations and source markers completely removed from the entire response, including the explanations. I will ensure they are not included moving forward.

An Approval Process consists of several stages, each with its own set of automated actions. When a record is first submitted, it is typically locked to prevent further edits. If a user needs to " reverse " that submission—perhaps because they realized they made a mistake or the deal terms changed—the administrator must configure Recall Actions12. A recall action is specifically designed to allow the submitter or an administrator to pull the record back out of the approval queue. Common recall actions include a Field Update to change the status back to " Draft " and, most importantly, an action to unlock the record so it can be edited again. Final Rejection Actions (Option A) occur when an approver denies the request, and Final Approval Actions (Option C) occur when the request is fully granted. Initial Submission Actions (Option D) are what lock the record and start the process in the first place.