Free Salesforce ADM-201 Practice Exam with Questions & Answers | Set: 5

In Salesforce, a dashboard’s running user determines which data is displayed to anyone viewing the dashboard. If a dashboard is configured with a "Static" running user (e.g., a Support Manager who has "View All" permissions), every user who views that dashboard will see the manager's level of data, regardless of their own personal sharing permissions. This bypasses the Organization-Wide Default (OWD) of "Private" for the Case object. When the support manager observes that reps can see all cases on a group dashboard, it is almost certainly because the dashboard is "running" as a user with high-level access. To correct this and ensure users only see data they are entitled to, the Platform Administrator should convert it into a Dynamic Dashboard. A dynamic dashboard is set to "Run as the logged-in user," meaning the data reflected in the components will automatically filter based on the individual viewer's specific sharing rules and record ownership. This ensures that the dashboard remains a useful tool for the team while strictly adhering to the company's data privacy and security requirements.

Salesforce allows Queues to be designated as assigned approvers in an approval process. When a record is submitted for approval and routed to a queue, an email notification is sent to all queue members (depending on queue settings). The core behavior is that any member of the queue can "claim" the request and either approve or reject it. Once one member takes action, the step is considered complete, and the queue is treated as a single decision-making entity. Unanimous approval (Option A) is a specific setting for multiple individual assigned approvers, but it does not apply to queues in this way. Option C is incorrect because the purpose of a queue is to notify all members to ensure a timely response. Queues are supported for most standard and all custom objects (negating Option D).

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 Data Import Wizard is the ideal tool for importing a relatively small number of records (up to 50,000) when those records involve standard objects like Accounts and Contacts simultaneously. One of the unique strengths of the Data Import Wizard is its ability to handle "Account and Contact" imports in a single pass, automatically linking the contacts to the correct accounts based on name or site. Because the volume in this request is only 300 records, the Data Import Wizard provides a simple, browser-based interface that includes built-in duplicate checking, which is highly beneficial for maintaining data quality. While the Data Loader (Option D) and Dataloader.io (Option A) can also handle 300 records, they are typically reserved for much larger datasets (up to 5 million records) or more complex objects. The "Wizard" is the most user-friendly and efficient choice for this specific sales rep request.