Salesforce Certified Platform Administrator Plat-Admn-201 Exam Questions

Answer : A

Salesforce does not provide a robust, native 'document merge' engine that can handle complex templates, headers, and advanced formatting out of the box. Therefore, the standard practice for implementing such a solution is to download a third-party application from the AppExchange. The AppExchange is the primary marketplace for Salesforce-integrated solutions, offering popular document generation tools like Conga Composer, Nintex DocGen, or S-Docs. These tools allow administrators to create professional-grade documents (like quotes, contracts, and invoices) by merging Salesforce record data into Word, PDF, or Excel templates. As a Platform Administrator, the process involves researching the best-fit app for the requirements, installing the package into a Sandbox for testing, and then deploying it to Production. This approach is highly efficient because it leverages existing, vetted technology that is specifically designed to handle the complexities of document generation, saving the organization from trying to build a costly and difficult-to-maintain custom solution using code or complex automation.

Answer : B, C

When a user is locked out of Salesforce due to too many incorrect login attempts, the Platform Administrator must take specific actions on the user's record detail page to restore access. First, the administrator should click the Unlock button19. This clears the lockout status immediately20. Second, because the user likely forgot their credentials (causing the failed attempts), the administrator should use the Reset Password button21. This sends a temporary link to the user's email, allowing them to create a new password and log in successfully. 'Logging in as the user' (Option A) is a troubleshooting tool for existing sessions but cannot bypass a lockout or change a password on the user's behalf. Changing 'Password Policies' (Option D) would affect the entire organization and is not a valid way to help a single locked-out individual.

Answer : B

Grounding is 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's Einstein Trust Layer performs several critical checks, including identifying Prompt 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.

Answer : D

In Salesforce, Support Settings is the primary configuration page for determining how the Service Cloud handles automated case updates. This section allows a Platform Administrator to define the 'Default Case Owner' and the 'Automated Case User.' The Automated Case User is the user listed in the Case History for automated actions, such as those triggered by assignment rules, escalation rules, or Email-to-Case. If the business sees an 'unexpected' user name in the Created By or Last Modified By fields during these automated processes, it is usually because this setting is pointing to a specific administrator or a system user. By updating the Automated Case User to a dedicated 'Integration User,' the admin ensures that the audit trail clearly distinguishes between manual edits made by staff and automated updates made by the system. This provides better clarity for the support team and prevents confusion regarding who is responsible for specific record changes.

Answer : C

An Approval Process is the dedicated Salesforce feature for managing workflows that require human 'review and decision-making.' Unlike Assignment Rules (Option A), which simply change the owner of a record, an Approval Process locks the record to prevent further changes and routes a formal request to an 'Approver.' This approver can then choose to Approve, Reject, or Reassign the request. The process can include multiple steps, entry criteria (e.g., 'only if discount > 10%'), and specific automated actions that occur once the final decision is made. Validation Rules (Option B) are used to prevent saving bad data, not for routing. Schema Builder (Option D) is a visualization tool for the data model. Therefore, when a business process requires an official 'sign-off' or 'decision,' the Approval Process engine is the correct architectural choice.

Answer : C

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.

Answer : B

The Data Import Wizard is the most efficient and user-friendly tool for importing a relatively small number of records (up to 50,000) when those records involve standard objects like Accounts and Contacts simultaneously. A key advantage of this tool is its built-in capability to handle 'Account and Contact' imports in a single pass, which includes automatic matching to prevent duplicates based on name or email. For a volume of 300 records, the browser-based wizard is much faster to set up than the Data Loader, as it does not require a separate installation or complex CSV mapping for simple standard objects. While the Data Loader (Option D) and Dataloader.io (Option C) can handle this volume, they are typically preferred for much larger datasets (up to 5 million records) or more complex custom objects. The 'Wizard' provides a guided experience that is ideal for sales reps or administrators performing routine data entry tasks.