Free Salesforce Certified Platform Administrator Exam Plat-Admn-201 Exam Questions

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.

Creating effective Agentforce prompts requires a focus on clarity and simplicity to ensure the Large Language Model (LLM) follows instructions accurately. According to Salesforce best practices, administrators should use natural, easy-to-understand language and provide clear, concise instructions1919. This approach helps the AI accurately reason through the task without becoming confused by overly complex or nested logic (Option A). While technical accuracy is important, relying heavily on jargon or abbreviations (Option B) can sometimes lead to unexpected results if the LLM interprets those terms differently in various contextsFurthermore, providing high-level theoretical concepts (Option C) often results in vague or 'creative' answers that may not be helpful for technical troubleshooting, which requires specific and actionable steps22. Using direct instructions like 'Summarize the issue in three bullet points' is more effective than broad guidelines.

The requirement to have a record 'signed off' by a specific individual (the CFO) based on a dollar threshold is a classic use case for an Approval Process . While the 'Submit for Approval' button (Option A) allows a user to manually start the process, the prompt specifies that the process should happen 'automatically'50. To achieve this automation, the Platform Administrator should use Flow Builder to trigger the approval process . A Record-Triggered Flow can be set to run when an Opportunity is created or updated and meets the criteria (Amount > $100,000) . The flow would then use the 'Submit for Approval' action to launch the record into the predefined approval process without requiring the sales rep to click a button . Einstein Next Best Action (Option B) is a recommendation tool, not a workflow enforcement tool54. Apex Triggers (Option C) could perform this task, but Salesforce best practices recommend using 'clicks not code' (Flow) whenever possible for such requirements . Using Flow to launch an Approval Process provides the necessary automation, routing, and audit trail the CFO requires

For a custom object to support Tasks and Events, the 'Allow Activities' setting must be enabled in the object's properties. When a Platform Administrator creates a custom object, this checkbox is often left unchecked by default35. Enabling this feature allows the 'Related To' (WhatId) field on a Task or Event to be linked to records of that custom object type36. While adding the related list to the page layout (Option C) is a necessary step for visibility, it will not work if the underlying feature isn't enabled first37. Sharing rules (Option A) and profile permissions (Option D) manage access to existing records but do not control whether the object is technically capable of having activities associated with it.

The Mobile Only app is the default navigation experience in the Salesforce mobile app when no other Lightning apps have been assigned to a user for mobile use64. In this configuration, the navigation menu is controlled globally via the 'Salesforce Navigation' setup page6565. A key behavior of this interface is that the first four items placed in the navigation list become the 'persistent' icons that appear in the navigation bar at the bottom of the mobile screen for quick access66. These same items also appear at the top of the 'Menu' tab67. Option A is incorrect because pages must have a corresponding Tab created before they can be added to the navigation menu68. Option B is incorrect because the 'Mobile Only' navigation is a single global setting for the entire org; if you need different menus for different profiles, you must create and deploy specific Lightning Apps69. Option D is incorrect because standard objects do not appear automatically; the administrator must explicitly add them to the navigation list in Setup70. Understanding this behavior is essential for ensuring mobile users have a streamlined and intuitive interface

When relating two objects where the child records must persist even if the parent record is deleted, a Lookup Relationship is the correct choice18. In this scenario, the Shipment object should have a lookup field pointing to the Account. Unlike a Master-Detail relationship (Option B), which automatically deletes child records (cascade delete) when the master is deleted, a Lookup relationship allows the child record to remain in the system, either by clearing the lookup field or simply leaving it as is. Option A and D are architecturally incorrect because the relationship field is always created on the 'child' or 'many' side of the relationship (Shipments) to point to the 'parent' (Account). Using a Lookup relationship ensures data retention for historical shipment tracking while still allowing the shipment items to be visible via a related list on the Account page.

Profiles in Salesforce serve as the foundation for what a user can 'do' with records, specifically defining Object-Level Security (Create, Read, Edit, Delete permissions). The standard Marketing User profile typically does not include full 'Edit' access to the Opportunity object by default, as marketing roles are traditionally focused on Leads and Campaigns. To fulfill the requirement of allowing marketers to maintain campaign relationships on Opportunities, the administrator must ensure the profile has the necessary object permissions. If the organization is using a custom profile based on the Marketing User template, the admin should edit the object permissions directly on that profile to include 'Read' and 'Edit' for Opportunities. This allows the marketers to view the records and update the 'Primary Campaign Source' field. While a Permission Set could also grant this access, the question implies the admin is currently configuring the profile itself. Adjusting the profile's object permissions is the direct way to align the user's capabilities with the business's functional requirements.

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.

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.

To make a Screen Flow available to users on a specific record, such as a Case, the Platform Administrator should add the Flow component to the Lightning Record Page. Using the Lightning App Builder, the admin can drag the Flow component onto the page and select the specific 'Service Question' flow from the list8888. This allows the flow to be embedded directly into the workspace where the service reps are already looking at case details9. While flows can be placed on a Home Page (Option B), that would not provide the case-specific context needed for the reps10. Page Layouts (Option A) are used for standard fields and related lists but do not natively host dynamic screen flow components11. Component Filters (Option D) are used to show or hide the flow based on certain criteria, but the distribution itself is handled by placing it on the Lightning Page12.