ADM-201 Exam Dumps - Salesforce Certified Platform Administrator (Plat-Admn-201)

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.

During the Lead Conversion process, Salesforce automatically transfers the history and interaction data associated with the Lead to the newly created Account, Contact, and Opportunity. This includes all activities, meaning both Open Activities (like upcoming tasks or events) and Activity History (like past emails or logged calls) are attached to the resulting records to maintain a complete customer timeline. Campaign history is also typically associated with the resulting Contact, but the question specifically asks about "related records" in a broader sense, and the transfer of all activities is a primary mechanical function of the conversion. Option A is incorrect because custom object records do not automatically move unless specific custom mapping or code is in place. Option B is incorrect because the system does not limit the transfer to only open activities.

Groundingis the process by which an AI agent retrieves and uses specific, trusted data to ensure its responses are accurate and relevant41. During this process, Salesforce'sEinstein Trust Layerperforms several critical checks, including identifyingPrompt Injection risks424242. 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 interface43. 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 policies44. 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 check45. 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 data46.

A Validation Rule is the only way to enforce conditional requirement logic based on both record data (the stage) and user data (the user's profile or role). To achieve this, the Platform Administrator would write a formula that checks three things: if the Stage is "Negotiation," if the Amount field is blank, and if the user is not a manager. The formula would look something like: AND(ISPICKVAL(StageName, "Negotiation"), ISBLANK(Amount), $Profile.Name <> "Sales Manager"). This allows the system to block standard sales users from saving the record without an amount, while the exception for the manager's profile allows them to bypass the requirement. Making the field required on the page layout (Option A) would affect all users equally, failing to meet the requirement for managers. Assigning the Admin profile to managers (Option B) is a major security risk and violates the principle of least privilege.1

In Salesforce, access to reports and dashboards is determined by the folder in which they are stored. If a dashboard is in a shared folder, anyone with access to that folder can view it. To "temporarily remove" a specific dashboard from public view without affecting the rest of the folder's contents, the Platform Administrator should edit the dashboard's properties and move it to a private dashboards folder (such as "My Private Dashboards"). Once moved, only the administrator (and those with high-level "View All Data" permissions) can see it while the changes are being made. Removing view access to the shared folder (Option A) would hide all dashboards in that folder, which is not the goal. Permission sets (Option C) control functional access (the ability to create or edit dashboards) but not individual record/dashboard visibility. Private groups (Option D) are for Chatter collaboration, not for managing dashboard folder security.

For an AI agent to provide "complete and accurate" support, it needs access to a unified, 360-degree view of the customer data. Data Cloud is the critical prerequisite because it ingests, harmonizes, and unifies data from multiple sources (Salesforce, external databases, legacy systems) into a single "Unified Profile." When Agentforce is "grounded" in Data Cloud, it can reference real-time customer interactions, purchase history, and cross-channel behavior that might not exist in a single Case or Contact record. Without Data Cloud, the agent's knowledge is limited to siloed data, which increases the risk of providing incomplete or irrelevant answers. While Console layouts (Option B) and intake methods (Option A) are important for the UI, they do not provide the data foundation necessary for advanced AI reasoning.

Case Assignment Rules are the standard Salesforce tool for automatically routing cases to specific users or queues based on record criteria. A single assignment rule can contain multiple "Rule Entries" processed in a specific order. To meet this requirement, the Platform Administrator would create a rule with two entries: one that checks if the Account's "Level" field equals "Platinum" and routes it to the Priority Support Queue, and another that checks if the level is "Silver" or "Gold" and routes it to the Regular Support Queue. This automation happens the moment the case is created, ensuring that high-value customers receive immediate attention from the appropriate team. Escalation Rules (Option A) are used to move a case after it has been sitting for a period of time, not for initial routing. Workflow Rules (Option D) are a legacy tool that cannot natively assign cases to queues in the same direct manner as Assignment Rules.

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.