How many Refer to the Exhibit Practice Questions questions are on this page?

This page has 12 Refer to the Exhibit Practice Questions scenario questions for the SF-Admin exam, each with detailed explanations and wrong-answer analysis.

How should I approach SF-Admin scenario questions?

Read the full scenario before looking at the answer options. Identify the constraint or requirement in the scenario, then eliminate options that are generally true but wrong for this specific case. Scenario questions reward careful reading over pattern matching.

← Back to Salesforce Certified Platform Administrator questions

Scenario-based practice

Refer to the Exhibit Practice Questions

Practise Salesforce Certified Platform Administrator practice questions — original exam-style scenarios covering every exam domain, with detailed explanations, wrong-answer analysis, and common exam traps.

Start full practice test Read exam guide

scenario questions

SF-Admin

exam code

Salesforce

vendor

Scenario guide

How to approach refer to the exhibit practice questions

Practise exhibit-style questions that ask you to read a topology, table, command output or diagram before choosing the best answer.

Quick answer

Exhibit-style questions test whether you can read a topology, command output, diagram or table before choosing the best answer.

How to extract the relevant detail from an exhibit.

How topology, command output or routing information affects the answer.

How to avoid answering from memory before reading the evidence.

How to map the exhibit back to the exam objective.

Practice scenarios

Question 1mediummultiple choice

Full question →

Refer to the exhibit. A user reports that their account is locked and they cannot log in. Based on the JSON configuration, what must the administrator do to restore access?

Exhibit

Login Policy Configuration: 
{
  "PasswordExpiration": "90 Days",
  "EnforcePasswordHistory": "3 Passwords",
  "MaximumInvalidLoginAttempts": "5",
  "LockoutEffectivePeriod": "Forever"
}

A
Wait for the lockout period to expire in 30 minutes.
Why it fails: The exhibit explicitly defines the 'LockoutEffectivePeriod' as 'Forever'. Therefore, waiting for an automatic expiration is not a valid solution. The system will continue to block login attempts indefinitely until a manual intervention is performed by an administrator with the appropriate system permissions to unlock the account.
B
Reset the user's password via the login screen.
Why it fails: Resetting the password does not automatically unlock a user account that has been locked due to excessive failed attempts. The lock status is a separate state maintained by the security engine. The administrator must specifically unlock the account, as a password reset alone will not clear the active lockout flag.
C
Manually unlock the user account in Setup.
Since the lockout policy is set to 'Forever', the only way to re-enable the account is through an administrator performing the unlock action on the specific user detail record. This manual step ensures that security policies are enforced while allowing legitimate users to regain access after verification.
D
Update the password history setting.
Why it fails: The password history setting governs password reuse policies and has no functional link to the account lockout state. Modifying this setting will not unlock the account or allow the user to regain access. The administrator needs to focus specifically on the account status to resolve the current access issue.

Full breakdown with real-world context →

Question 2hardmultiple choice

Review the full routing breakdown →

Refer to the exhibit.

```json

{
  "routing_type": "QueueBased",
  "service_channel": "Case",
  "push_routing": true,
  "fallback_queue": "Tier_1_Support"
}

```

An administrator is reviewing a routing configuration payload for a new support implementation. Based on the routing type specified, how will work items be distributed to agents?

A
Work items will be routed dynamically based on real-time agent skill proficiencies.
Why it fails: Queue-based routing delivers work items to queues, not by matching agent skill proficiencies in real time. Skill-based routing is tempting because it also distributes cases to agents, and it would be correct if the payload specified a skills-based routing type instead of QueueBased.
B
Work items will be distributed to available agents who are members of the designated queue.
QueueBased routing assigns incoming work items to the designated service channel queue, then distributes them to agents who are members of that queue and currently available, with the fallback queue handling overflow when no members are free.
C
Work items will be assigned automatically using round-robin user assignment rules.
Why it fails: Queue-based routing places work items into queues for agents to pull or receive; round-robin assignment is a separate Omni-Channel routing model. Round-robin is tempting because it also distributes cases automatically, and it would be correct if the routing type were configured as round-robin rather than QueueBased.
D
Work items will be broadcasted simultaneously to all online agents regardless of queue membership.
Why it fails: Queue-based routing scopes delivery to agents belonging to the relevant queue, with the fallback queue handling overflow; it does not broadcast to every online agent. Broadcasting is tempting because push routing does send work to agents, and it would be correct if the configuration used a broadcast routing model.

Full breakdown with real-world context →

Question 3hardmultiple choice

Full question →

Refer to the exhibit. A user with the 'Sales User' profile has 'View All' permissions on the Opportunity object, but the Org-Wide Default is set to 'Private'. What is the effective access for this user?

Exhibit

{
  "Profile": "Sales User",
  "Object": "Opportunity",
  "Permission_Override": "None",
  "System_Permission": "View All",
  "Org_Wide_Default": "Private"
}

A
The user can only see records they own.
Why it fails: The 'Private' Org-Wide Default limits access to owners and those above them in the role hierarchy. However, the 'View All' permission supersedes these sharing restrictions, granting the user visibility into all records regardless of the record's ownership status.
B
The user can see all records for the object.
System permissions like 'View All' are designed to bypass standard sharing model constraints. By granting this permission, the administrator ensures that the user can access every record of that object within the organization, rendering the 'Private' Org-Wide Default irrelevant for this user.
C
The user requires a manual share record.
Why it fails: Manual sharing is used when a specific record owner wants to provide access to a user on a case-by-case basis. Since the user already has the 'View All' permission, they already have full visibility to all records without requiring individual manual shares.
D
The user can only see records shared via roles.
Why it fails: Role hierarchies allow users to see records owned by users below them. Because the user has the 'View All' system permission, they are not constrained by the role hierarchy or the Org-Wide Default, making this statement technically incorrect regarding their actual access.

Full breakdown with real-world context →

Question 4hardmultiple choice

Full question →

Refer to the exhibit. A user cannot access a report, despite having 'Read' access to the underlying object. What is the most likely cause?

Exhibit

Error: You do not have permission to view this report. Please contact your administrator if you believe this is an error. The report is based on a Report Type that includes accounts with no activity.

A
The user lacks 'View All' permissions on the Account object
Why it fails: While 'View All' can bypass certain sharing restrictions, it is not strictly required to run a report. If the user has standard read access and the report folder is shared correctly, they should be able to view the data. Missing 'View All' is rarely the single point of failure.
B
The report folder is not shared with the user's role
Even with full object-level permissions, users cannot access reports if the report folder permissions have not been explicitly granted. Providing access to the folder is a prerequisite for viewing any report stored within it, representing a common administrative oversight in managing secure reporting environments.
C
The user is assigned a Standard User profile
Why it fails: Standard User profiles provide sufficient access to run reports by default. The issue is likely a specific sharing configuration rather than the base profile, as profile settings usually allow report execution unless specifically restricted by custom permission sets or administrative overrides applied at the organization level.
D
The report contains a filter on a hidden field
Why it fails: Report filters on hidden fields do not prevent the user from accessing the report; they simply result in the user seeing a subset of data that matches the filter criteria. The system would process the report and display the results rather than throwing a hard permission error.

Full breakdown with real-world context →

Question 5hardmultiple choice

Full question →

Refer to the exhibit. An administrator is reviewing a field configuration. Based on the provided metadata, what is the impact of the 'restricted_picklist' property being set to true?

Exhibit

{
  "field_name": "Service_Level__c",
  "type": "Picklist",
  "active": true,
  "formula": null,
  "required": false,
  "restricted_picklist": true
}

A
The field will only accept values defined in the picklist set.
When 'restricted_picklist' is true, Salesforce prevents any value from being saved that does not exist in the defined picklist set. This is enforced via API, UI, and Apex, ensuring data integrity by blocking invalid or misspelled entries that could otherwise bypass standard picklist validation.
B
The field will be hidden from all users unless they have a specific permission.
Why it fails: Restricting a picklist does not control field visibility. Field visibility is managed by Field-Level Security settings on the profile or permission set. This property only impacts the validation of the data entered, not who can see or interact with the field itself.
C
The field can only be updated by the system administrator.
Why it fails: The restricted picklist property governs data validation, not record-level security or field-level editability. Any user with 'Edit' access to the object and 'Edit' permission on the field can update the value, provided they select a valid option from the predefined list.
D
The field is converted to a global value set automatically.
Why it fails: Setting a picklist to restricted does not automatically convert it to a Global Value Set. While Global Value Sets can be restricted, the restricted attribute is a standalone property of the picklist field itself, not a trigger for changing the object's field architecture.

Full breakdown with real-world context →

Question 6mediummultiple choice

Full question →

Refer to the exhibit. A customer asks for a $750 refund. The Agent refuses to process the request despite the customer being eligible. What is the most likely cause for this behavior?

Exhibit

Agent Topic: Refund Policy
Configuration:
- Instructions: Use the RefundFlow to process requests.
- Data Sources: Knowledge Base, OrderHistory
- Guardrails: Maximum refund amount $500

A
The Knowledge Base is missing information about high-value refunds.
Why it fails: Knowledge Base articles provide information but do not override operational guardrails. Even if the article explains high-value refund policies, the Agent's configuration dictates the execution logic. If the guardrail is set to $500, the Agent will continue to enforce that limit regardless of the content in Knowledge.
B
The RefundFlow has a hardcoded limit of $500.
Why it fails: While the Flow might have its own internal logic, the exhibit explicitly highlights the Agent Topic guardrail configuration. In Agentforce, the topic-level guardrails act as an overarching control mechanism. Even if the Flow allows for higher amounts, the Agent will stop the transaction based on the guardrail settings.
C
The Agent is adhering to the configured guardrail limit.
The agent is functioning as designed by enforcing the $500 guardrail configured in the Topic. Guardrails are critical for AI governance, ensuring agents do not execute actions that exceed company policy. The agent successfully recognized the input amount and applied the constraint, preventing a policy violation.
D
The Agent is lacking the correct permission to update OrderHistory.
Why it fails: Permissions issues would typically result in an error message or a generic failure notice rather than a refusal based on the amount. The context of the request specifically points to the $750 value, which directly contradicts the $500 guardrail limit defined in the agent's configuration settings.

Full breakdown with real-world context →

Question 7hardmultiple choice

Full question →

Refer to the exhibit. An administrator is analyzing data consistency. Which Salesforce reporting feature uses this logic to display only records where the Opportunity stage is Closed Won?

Exhibit

{
  "field": "StageName",
  "operator": "equals",
  "value": "Closed Won",
  "scope": "all_time"
}

A
Report Filter
Report filters are the primary way to limit report results. By specifying the field (StageName), the operator (equals), and the value (Closed Won), the report runtime will exclude all records that do not match these criteria, providing a clean set of closed-won opportunities.
B
Sharing Rule
Why it fails: Sharing rules are used to open up record access across the organization, not to filter records within a report. Using a sharing rule here would be a misconfiguration of security settings and would not achieve the objective of refining the visual report output.
C
Validation Rule
Why it fails: Validation rules are used to enforce data entry standards when a user saves a record. They cannot be used to filter or view data in a report. Applying a validation rule to 'Closed Won' would prevent saving rather than filtering records for analysis.
D
Public Group
Why it fails: Public groups are containers for users, roles, or subordinates used primarily for security and sharing settings. They have no function in filtering or querying data records and are completely unrelated to the logic shown in the exhibit, which pertains to report filtering.

Full breakdown with real-world context →

Question 8hardmultiple choice

Full question →

Refer to the exhibit. An agent attempts to trigger an order lookup, but it fails with the provided error. What is the most likely cause of this 403 error?

Exhibit

Error: Action execution failed. Cause: 'Flow name Order_Lookup_Flow not found or unauthorized'. Status: 403 Forbidden.

A
The flow is currently inactive.
Why it fails: If a flow were inactive, the error would typically be a 'Flow Not Found' or a specific runtime error indicating that the flow cannot be invoked, not a 403 Forbidden. The 403 status code is explicitly related to permission restrictions, not the activation status of the flow.
B
The agent's user profile lacks execution permissions for the Flow.
The 403 Forbidden error indicates an authorization failure. For an agent to invoke a flow, the user profile associated with the agent must have the 'Run Flow' permission. Without this explicit authorization, the platform blocks the agent from initiating the requested process, resulting in the observed error.
C
The flow has an invalid input parameter.
Why it fails: An invalid input parameter would typically trigger a validation error or a runtime exception rather than a 403 Forbidden status. The 403 error code is a security-related response indicating that the platform has denied access to the object, not that the object's input data was malformed.
D
The Agentforce platform is experiencing a service outage.
Why it fails: A service outage would typically result in a 5xx series error code (e.g., 503 Service Unavailable). A 403 Forbidden error is specifically tied to access control and permission configurations within the environment, confirming that the agent is authenticated but lacks the right to perform the action.

Full breakdown with real-world context →

Question 9hardmultiple choice

Full question →

Refer to the exhibit. An administrator is trying to run a report, but the CLI debug output indicates it stopped at 2,000 rows. What is the cause of this limitation?

Exhibit

CLI Output: 
DEBUG: Row 1023: Account Name = 'Global Tech'
DEBUG: Row 1024: Account Name = 'Delta Corp'
ERROR: Report limit reached: 2000 rows. Execution stopped.

A
The user's license has a reporting limit
Why it fails: Report row limits are a system-wide platform constraint for the reporting UI, not a function of the user's license type. Every user is subject to the same display constraints regardless of their role or license, ensuring consistent system performance across the entire Salesforce organization during report execution.
B
The report exceeds the 2,000-row display limit
Salesforce restricts the number of records shown in the browser to 2,000 to maintain performance. If a report requires more than this, users must export the full dataset to a file (like CSV or Excel) to view every record, as the UI does not support displaying larger result sets.
C
The organization has reached its total data storage limit
Why it fails: Data storage limits refer to the total size of records in the database, not the number of rows a report can display. Even if an organization has minimal data, the report UI limit remains at 2,000 rows to ensure that individual report rendering remains fast and responsive.
D
The report type is corrupted
Why it fails: A corrupted report type would result in a structural error or inability to run the report, rather than a specific '2,000 row' limit notification. This message is a standard system response to a query returning more records than the interface is configured to display in the browser.

Full breakdown with real-world context →

Question 10hardmultiple choice

Full question →

Refer to the exhibit. A support agent receives a new case with Priority 'High'. The case remains open for 30 hours without an update. How should the administrator ensure the support manager is notified after 24 hours?

Exhibit

Case Assignment Rule: Criteria -> Priority Equals High, Escalation Rule: Criteria -> Case Age > 24 hours, Entitlement Process: Criteria -> Service Level = Gold.

A
Use the Assignment Rule.
Why it fails: Assignment Rules are only triggered upon the creation or manual update of a case. They cannot evaluate the passage of time or trigger actions based on how long a case has been open. They are meant for initial routing and load balancing of incoming work requests to agents.
B
Use the Entitlement Process.
Why it fails: Entitlement processes track milestones, such as first response time or resolution time, based on service contracts. While they can perform actions upon milestone completion or violation, Escalation Rules are the standard tool specifically intended for time-based oversight of open cases that have exceeded set threshold durations.
C
Use the Escalation Rule.
Escalation Rules are the native Salesforce feature for handling cases that have not been addressed within a specific timeframe. By defining an entry criteria that looks for high-priority cases and setting the escalation time to 24 hours, the system ensures management is notified when the case remains open.
D
Use a Workflow Rule.
Why it fails: Workflow rules do not support time-dependent actions based on the duration of a case record existing in the system in the same flexible manner as Escalation Rules. While time-dependent workflow actions exist, Escalation Rules are purpose-built for service scenarios and offer superior management of case status queues.

Full breakdown with real-world context →

Question 11mediummultiple choice

Full question →

Refer to the exhibit. A user reports that they cannot update an Opportunity. Based on the debug log, what is the most likely cause?

Exhibit

CLI Output: 16:45:01.001 USER_DEBUG [12]|DEBUG|Validation Error: System.DmlException: Update failed. First exception on row 0; first error: FIELD_CUSTOM_VALIDATION_EXCEPTION, Validation rule error message.

A
The user lacks object-level update permissions.
Why it fails: If the user lacked object-level permissions, the error would typically indicate an 'Insufficient Privileges' exception, not a 'FIELD_CUSTOM_VALIDATION_EXCEPTION'. The latter specifically indicates that the record reached the database, but was rejected due to logic configured within a validation rule, not because of the user's base object permissions.
B
A custom validation rule is preventing the update.
The error code 'FIELD_CUSTOM_VALIDATION_EXCEPTION' is the standard system exception thrown when a custom validation rule fails. This confirms that the record data provided by the user did not meet the criteria defined in one of the validation rules, causing the system to block the save operation for that record.
C
The field is read-only on the page layout.
Why it fails: Page layout settings are enforced at the UI level for standard users. If a field were simply read-only on the page, the user wouldn't be able to edit it in the first place, and no validation exception would occur. This error points to back-end logic, not interface configuration constraints.
D
The user does not have Field-Level Security.
Why it fails: If the user lacked field-level security, the field would be hidden from them entirely, and they would not be able to input data into it. An update exception like this implies that the data was provided and the system attempted to process it, but ultimately rejected the input value.

Full breakdown with real-world context →

Question 12hardmultiple choice

Full question →

A user receives the error shown in the exhibit when trying to export a specific report. What should the administrator check first?

Exhibit

Error: Insufficient privileges: You do not have the level of access necessary to perform the operation you requested. Please contact the owner of the record or your administrator if access is necessary.

A
The user's password expiration policy.
Why it fails: Password expiration policies would prevent the user from logging into the system entirely, not just from exporting a specific report. If the user is logged in and can navigate to the report, the authentication is fine, and the issue is restricted to the authorization level.
B
The sharing permissions on the report folder.
Access to reports is governed by the folder in which they are stored. If a user does not have at least 'Viewer' access to the folder, they will be blocked from accessing the report content, regardless of their object-level permissions, making this the most logical first check.
C
The user's daily data export limit.
Why it fails: Salesforce does not impose a generic 'daily export limit' that would trigger this specific 'Insufficient Privileges' error message. This message is clearly tied to record or folder access permissions, not to resource usage limits which usually trigger different error types or system notifications.
D
The Apex trigger execution limits.
Why it fails: Apex trigger limits do not prevent report exports. Reports are query-based and do not fire DML triggers on read. This error is strictly about the user's security profile and permissions to see the report, not about the backend code execution or resource exhaustion on the platform.

Full breakdown with real-world context →

These SF-Admin practice questions are part of Courseiva's free Salesforce certification practice question bank. Courseiva provides original exam-style SF-Admin questions with detailed explanations, topic-based practice, mock exams, readiness tracking, and study analytics.

Refer to the Exhibit Practice Questions

How to approach refer to the exhibit practice questions

Quick answer

Related SF-Admin topic practice pages

Sales and Marketing Applications practice questions

Agentforce AI practice questions

Data and Analytics Management practice questions

Object Manager and Lightning App Builder practice questions

Productivity and Collaboration practice questions

Configuration and Setup practice questions

Automation practice questions

Service and Support Applications practice questions

SF-Admin fundamentals practice questions

SF-Admin scenario practice questions

SF-Admin troubleshooting practice questions

Practice scenarios

Refer to the exhibit. A user reports that their account is locked and they cannot log in. Based on the JSON configuration, what must the administrator do to restore access?

Exhibit

Refer to the exhibit. A user with the 'Sales User' profile has 'View All' permissions on the Opportunity object, but the Org-Wide Default is set to 'Private'. What is the effective access for this user?

Exhibit

Refer to the exhibit. A user cannot access a report, despite having 'Read' access to the underlying object. What is the most likely cause?

Exhibit

Refer to the exhibit. An administrator is reviewing a field configuration. Based on the provided metadata, what is the impact of the 'restricted_picklist' property being set to true?

Exhibit

Refer to the exhibit. A customer asks for a $750 refund. The Agent refuses to process the request despite the customer being eligible. What is the most likely cause for this behavior?

Exhibit

Refer to the exhibit. An administrator is analyzing data consistency. Which Salesforce reporting feature uses this logic to display only records where the Opportunity stage is Closed Won?

Exhibit

Refer to the exhibit. An agent attempts to trigger an order lookup, but it fails with the provided error. What is the most likely cause of this 403 error?

Exhibit

Refer to the exhibit. An administrator is trying to run a report, but the CLI debug output indicates it stopped at 2,000 rows. What is the cause of this limitation?

Exhibit

Refer to the exhibit. A support agent receives a new case with Priority 'High'. The case remains open for 30 hours without an update. How should the administrator ensure the support manager is notified after 24 hours?

Exhibit

Refer to the exhibit. A user reports that they cannot update an Opportunity. Based on the debug log, what is the most likely cause?

Exhibit

A user receives the error shown in the exhibit when trying to export a specific report. What should the administrator check first?

Exhibit