Salesforce Certified Platform Administrator Plat-Admn-201 Exam Questions

Answer : B

In the Salesforce Setup menu, Company Settings (formerly Company Profile) is the central location where global organizational parameters are managed. This section contains several key settings. Under Company Information, the admin can view the Org ID, default time zone, and primary currency. The Fiscal Year settings allow the admin to define whether the organization follows a standard Gregorian calendar or a custom fiscal cycle. Business Hours are used to define the working times for the organization, which is critical for calculating milestones in Service Cloud or escalation rules. If Multi-Currency is enabled, this is also where exchange rates and active currencies are managed. Viewing and configuring these settings is a foundational task for any Platform Administrator, as they establish the baseline for how data is interpreted and how time-based automation functions across the entire instance. Ensuring these are correct is vital for accurate financial reporting and maintaining service level agreements (SLAs).

Answer : B

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.

Answer : C

In Salesforce, there are different types of sharing: Managed Sharing (Role Hierarchy, Sharing Rules) and Manual Sharing. A critical behavior of the platform is that when a user is deactivated, all their Manual Shares (records shared with them by other users using the 'Share' button) are automatically and permanently deleted from the system. Even if the user record is reactivated later, those manual shares do not return. Because the organization uses a 'Private' model and does not use criteria-based sharing rules, the user's previous access likely relied on manual sharing or their previous position in the hierarchy. While activating the record and adding them back to teams provides new access, the historical 'one-off' shares are gone. Options A and B are unlikely to be the cause of a total loss of visibility. Option D is incorrect because permission sets control what a user can do, not which specific records they can see in a private sharing model.

Answer : D

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.

Answer : D

In an agentic loop, the AI agent iteratively tries to solve a user's request by calling actions and evaluating the results. If the results of those actions are unsatisfactory (e.g., the data returned doesn't answer the prompt or a required input is missing), the agent's next logical step is to ask for additional information. By clarifying the user's intent or requesting the missing data point, the agent can initiate a new loop with better inputs. Giving up with an error message (Option B) or providing a 'best guess' (Option A) are considered failures of the reasoning process. Routing to a live agent (Option C) is an escalation step that typically happens after the agent has failed to resolve the issue even after clarification, or if the user explicitly asks for human help.

Answer : A

To provide a single dashboard that allows users to 'drill down' or toggle between different data subsets, the administrator should add Dashboard Filters. A dashboard filter allows the manager or agent to select a value (e.g., 'Origin = Phone' or 'Status = New'), and all components on the dashboard will instantly refresh to show only the data matching that criteria. Salesforce allows up to three filters per dashboard, which perfectly accommodates the request for origin, status, and owner. While a Bucket Column (Option D) can group data within a report, it does not provide the interactive 'drill down' capability on the dashboard itself. Widgets (Option B) are the components themselves, and Combination Charts (Option C) display multiple data sets in one visual but do not offer filtering functionality.

Answer : B

While modern tools like Flow Orchestration exist, the standard and most robust way to handle complex, criteria-based routing for record sign-offs is an Approval Process. An approval process can handle many different 'Approval Steps,' and each step can have its own 'Step Entry Criteria.' For instance, Step 1 could route to Leader A if the region is 'North,' while Step 2 routes to Leader B if the region is 'South' and the discount is >20%. With 30 potential sets of criteria, the administrator can build a comprehensive process that automatically identifies the correct approver without user intervention. Using an email button (Option A) or a manual form (Option D) is prone to human error, as the salesperson might select the wrong leader. A record-triggered flow (Option C) can launch an approval process, but the complex multi-step routing logic is best managed within the Approval engine itself to maintain a clear audit trail of who approved what and why.