Northern Trail Outfitters has the Case object set to private. The support manager raised a concern that reps have a broader view of data than expected and can see all cases on their group's dashboards. What is causing reps to have inappropriate access to data on dashboards?
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.
Question 2
What is the next step an agent performs when the tasks within an agentic loop are all unsatisfactory?
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.
Question 3
A Platform Administrator at Universal Containers has a screen flow that helps users create new leads. When Lead Source is "Search Engine", the administrator needs to require the user to choose a specific search engine from a picklist. If Lead Source is not "Search Engine", this picklist should be hidden. What is the most efficient way for the administrator to complete this requirement?
Answer : C
In Flow Builder, the most efficient and user-friendly way to handle dynamic user interfaces is through Component Visibility. This feature allows an administrator to set logic on individual screen components (like a picklist) so they only appear when specific criteria are met. In this scenario, the administrator would select the 'Specific Search Engine' picklist component within the Flow Screen and configure its visibility to show only when the 'Lead Source' screen component equals 'Search Engine.' This provides a 'clean' user experience where the form adapts in real-time to the user's input without requiring the user to navigate to a new screen or trigger a validation error. Validation rules (Option D) are reactive and only tell the user they made a mistake after they try to save, whereas conditional visibility is proactive. Option B is inefficient as it would require multiple screens and complex branching logic, whereas component visibility handles everything within a single screen element.
Question 4
Universal Containers (UC) customers have provided feedback that their support cases are not being responded to quickly enough. UC wants to send all unassigned cases that have been open for more than 2 hours to an urgent Case queue and alert the support manager. Which feature should a Platform Administrator configure to meet this requirement?
Answer : C
Case Escalation Rules are specifically designed to automate actions when a case has remained in a certain state for a defined period of time. In this scenario, the requirement involves two specific time-based triggers: moving the case after 2 hours and alerting a manager. Escalation rules allow the administrator to define 'Escalation Actions' that execute when the time threshold is reached, such as 'Reassign to Queue' and 'Notify Manager'. Case Assignment Rules (Option D) only fire when a case is first created or manually triggered, not after a time delay63. Reports (Option A) and Dashboards (Option B) provide information but do not physically move records or perform automated reassignments.
Question 5
Cloud Kicks wants users to only be able to choose the opportunity stage Closed Won if the Lead source has been selected. How should a Platform Administrator accomplish this goal?
Answer : C
A Validation Rule is the correct tool for enforcing conditional data entry requirements. When a business rule dictates that a field (Lead Source) must be populated only when another field (Stage) reaches a specific value (Closed Won), a validation rule can evaluate this logic every time a record is saved. The formula would check if the Stage is 'Closed Won' and simultaneously check if the Lead Source field is blank. If both conditions are true, the system displays an error message and prevents the user from saving the record. This ensures 100% data compliance. Dependent picklists (Options A and D) are used to filter available options in one list based on the selection of another, but they cannot 'require' a value to be present based on a stage change in the same way a validation rule can. Making the stage 'Read Only' (Option B) would prevent users from ever winning a deal. Validation rules are the standard method for maintaining data quality during critical transitions in the sales lifecycle.
Question 6
In an approval process, what happens when a queue is selected as the approver?
Answer : B
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).
Question 7
A Platform Administrator created a new prompt template and is testing it. Every time the administrator tests the template, it gives a different response. Why is the prompt template giving different responses each time it's run?
Answer : B
Generative AI models are inherently probabilistic, meaning they do not produce the exact same output every time, even when given the same input. When a Platform Administrator uses the Prompt Builder to test a template, each 'Preview' or 'Test' execution initiates a fresh, unique call to the Large Language Model (LLM). Because the LLM considers a range of linguistic possibilities and probabilities for each word it generates, the resulting text will vary slightly (or significantly) with each iteration. This behavior is expected and is a core characteristic of generative AI. To ensure consistent and high-quality results, administrators must refine their instructions to be as specific as possible, narrowing the LLM's range of creative interpretation. Options A, C, and D are incorrect because the Prompt Builder is designed to provide real-time feedback from the actual LLM to help administrators debug and perfect the prompt's logic before it is deployed to end-users or agents.
All Official Question Types