Select Two (Multi-Select) Questions

Standard manual queue assignment via public group list views

Why it fails: Manual queue assignment relies on agents picking cases from list views, so it cannot evaluate customer tier, product line and language proficiency simultaneously. It is tempting because public group list views suit low-volume, evenly skilled teams where supervisors triage by eye rather than by automated criteria.

Salesforce CRM Content library access rules

Why it fails: CRM Content library access rules govern who may view or download files, not how cases are assigned. They are tempting because both features involve sharing and permissions, but content access rules would be the right choice when restricting sensitive documents to specific audiences, not routing work.

Campaign influence attribution models

Why it fails: Campaign influence attribution models allocate marketing credit across campaigns and contacts; they contain no case-routing engine. They are tempting because both involve records and analytics, but attribution models would be correct when reporting which campaigns generated pipeline or revenue, not assigning cases to agents.

Native multi-tenant ERP synchronization for spare parts inventory

Why it fails: Entitlement Management tracks service contracts, entitlements, and entitlement consumption; it holds no ERP integration for spare-parts inventory. Native ERP synchronisation is tempting because entitlement data often originates in ERP systems, but that connection requires external middleware, not native functionality.

Automatic generation of outbound invoices for billing

Why it fails: Entitlement Management governs what a customer is entitled to receive; it does not raise invoices. Billing automation is tempting because entitlements underpin chargeable service contracts, but invoice generation belongs to Billing or external financial systems, not this feature.

Automatically route unassigned work items to queue members.

Why it fails: Case Teams add named members who can collaborate on a case and see it in their list; they do not alter queue routing logic. It is tempting because teams resemble queues, but assignment rules and omni-channel routing govern unassigned work distribution, not team membership.

Define agent shift schedules and availability capacity.

Why it fails: Case Teams assemble users, contacts and roles onto a single case record; they carry no scheduling or capacity data. Shift schedules and availability capacity belong to Omni-Channel routing configurations and Skills-based routing, which would be the right answer when the requirement is workload distribution rather than case collaboration.

Restrict case visibility exclusively to external portal users.

Why it fails: Case Team membership grants internal users access to a case; it does not restrict visibility to external portal users, which sharing rules and org-wide defaults control. It is tempting because teams affect who sees a case, but external visibility is set through sharing configuration, not team roles.

Hardcode session tokens in custom metadata types for quick retrieval.

Why it fails: Storing session tokens in custom metadata exposes credentials to anyone with metadata access and cannot be rotated per user, breaking the security requirement. Metadata types are for deployable configuration, so they suit environment-specific settings, not secrets.

Execute all external integrations synchronously inside standard before-insert triggers.

Why it fails: Synchronous callouts inside before-insert triggers hold the database transaction open for the duration of the external REST round-trip, exhausting governor limits and locking records under load. Such triggers suit lightweight, in-transaction validation only; external billing calls belong in asynchronous, queueable or callout-enabled classes.

Routing messaging threads exclusively through legacy CTI adapters

Why it fails: Messaging for In-App and Web uses its own Omni-Channel messaging routing with MessagingSession records and enhanced channels; legacy CTI adapters handle telephony only and cannot route messaging threads. It tempts where existing CTI infrastructure is already deployed, but messaging requires Messaging Channel and routing configuration instead.

Requiring all customers to install a managed desktop client application

Why it fails: Messaging for In-App and Web runs through the customer's existing browser or mobile app via embedded SDKs, so no managed desktop client is installed. It is tempting because a managed desktop client suits agent-side softphone or CTI deployments, where a controlled workstation application is genuinely required.

Disabling all security tokens on Experience Cloud guest profiles

Why it fails: Disabling security tokens compromises guest profile security and violates platform best practices.

Configure Salesforce Files sync for all article attachments.

Why it fails: Files sync replicates files across devices and does not govern how Knowledge article attachments are surfaced to agents in the console. It is tempting because attachments matter, but the requirement is agent access to articles and their attachments via the Knowledge component, not desktop file synchronisation.

Set up Omni-Channel supervisor tabs for Knowledge authoring queues.

Why it fails: Omni-Channel supervisor tabs monitor agent workload and queue performance; they do not surface Knowledge articles to agents during case handling. It is tempting because supervisors oversee authoring queues, but the requirement is agent-facing article search and attachment within the console, not queue supervision.

Enable Salesforce CRM Content libraries for each article type.

Why it fails: CRM Content libraries are a separate document repository from Knowledge; enabling them per article type does not make articles searchable or attachable in the console. It is tempting because both store content, but the correct configuration is Knowledge-enabled article types and the Knowledge component on the console.

Campaign Hierarchy Rules

Why it fails: Campaign Hierarchy Rules belong to Campaign Management, controlling how campaign members roll up through a hierarchy, and never appear in Case Management setup. It is tempting because hierarchy rules are a real Salesforce automation feature, correct when the requirement concerns campaign reporting structure — but the stem asks about case configuration.

Opportunity Split Rules

Why it fails: Opportunity Split Rules allocate credit among opportunity team members and are configured within Opportunity settings, not Case Management. It is tempting because split rules are a genuine Sales Cloud feature, correct when the requirement concerns revenue credit sharing — but the stem asks specifically about case configuration.

Lead Conversion Rules

Why it fails: Lead Conversion Rules govern how leads convert into accounts, contacts and opportunities, and are configured in Lead settings, not Case Management. It is tempting because conversion automation is a genuine Service Cloud feature, correct when the requirement concerns lead qualification — but the stem asks specifically about case configuration.

Pre-installed Email-to-Case Agent software

Why it fails: Email-to-Case Agent is a desktop tool for retrieving email into Salesforce; escalation rules need no such software, only criteria, actions and a rule entry condition. It is tempting because Email-to-Case does feed cases into escalation-eligible queues, and would be correct when configuring email channel handling, not escalation rules.

A mandatory Omni-Channel Routing Configuration

Why it fails: Escalation rules require a case owner or queue, escalation criteria and escalation actions; Omni-Channel Routing Configuration governs work distribution to agents, not escalation timing or reassignment. It is tempting because Omni-Channel does drive case routing, and would be correct when configuring presence-based work assignment rather than escalation rules.

Subtabs can exist independently without a parent workspace tab.

Why it fails: Subtabs in the Lightning Service Console always require a parent workspace tab; they cannot exist independently, so this contradicts the navigation model. It tempts candidates because console apps do support multiple open records and tabs, but those are workspace tabs, not standalone subtabs detached from any parent.

Standard navigation replaces the entire browser window content.

Why it fails: Standard navigation swaps only the inner content area, leaving the console's tabs, utility bar and header intact; replacing the whole browser window describes a classic full-page navigation model. It tempts because standard navigation is a genuine Salesforce feature, but it is not the console behaviour this question asks about.

Console apps cannot include utility bars.

Why it fails: Console apps fully support utility bars, which provide tools like macros, notes and history within the console footer. The option tempts candidates who confuse console navigation with some restricted app type, yet utility bars are a standard, supported component of Lightning console apps and are commonly configured alongside them.

Overflow routing automatically bypasses all agent skill requirements on the secondary queue.

Why it fails: Overflow routing redirects work to a secondary queue when thresholds are breached; it does not strip skill requirements, and the secondary queue's own routing configuration still applies. Bypassing skills is tempting because overflow implies loosening constraints. Skill-based routing is used when every queue must honour its own skill criteria.

Overflow routing is only available when using external third-party CTI connectors.

Why it fails: Overflow routing is native Omni-Channel functionality configured on queues and service channels; it does not depend on external CTI connectors. The confusion arises because CTI integrations also handle routing, but they serve telephony systems outside Salesforce. Third-party CTI connectors are chosen when integrating an external phone platform.

Dashboard-to-Case

Why it fails: Dashboard-to-Case does not exist; dashboards are read-only visualisations of report data and cannot generate cases. It is tempting because dashboards surface metrics needing follow-up, but that follow-up is manual. Automatic case creation requires an inbound channel such as Email-to-Case or Web-to-Case, which capture external communications.

Chatter-to-Case

Why it fails: Chatter-to-Case is not a supported automatic conversion channel; Chatter posts and @mentions are internal collaboration, not inbound case sources. It is tempting because Chatter can reference cases, but it creates posts, not cases. Automatic case creation requires Email-to-Case or Web-to-Case, which ingest external customer messages.

Report-to-Case

Why it fails: Report-to-Case does not exist; reports query existing records and cannot themselves become cases. It is tempting because reports reveal issues needing action, but that action is manual. Automatic case creation depends on inbound channels such as Email-to-Case or Web-to-Case, which capture external communications directly.

Salesforce Content version history logs

Why it fails: Content version history records document revisions and sharing, not agent or case metrics. It is tempting because Content is standard and auditable, but it is designed for file versioning. Real-time agent performance belongs in standard reporting snapshots and the Service Console's real-time dashboards.

Entitlement process audit trails

Why it fails: Entitlement process audit trails log milestone and entitlement changes for compliance, not agent throughput or queue metrics. They are tempting because entitlements relate to service delivery, but they record process history rather than live operational performance. Real-time monitoring uses reports, dashboards and console metrics.

Chatter user profile activity feeds

Why it fails: Chatter feeds surface collaboration posts and mentions, not quantitative operational metrics. It is tempting because feeds update in real time, but they carry conversations rather than measurable agent performance data. Standard reports, dashboards and the Service Console's real-time views provide the required metrics.

Standard auto-response rules configured for marketing campaigns

Why it fails: Standard auto-response rules send automated replies to inbound email; they cannot scan for urgent keywords, set case priority or notify management. It is tempting because auto-response rules act on incoming email, but the requirement needs Email-to-Case with keyword-based assignment and escalation rules.

Salesforce CRM Content library version alerts

Why it fails: CRM Content library version alerts notify users when documents are updated; they do not parse inbound email text or create cases. It is tempting because Content supports service knowledge sharing, but keyword-driven case creation and management escalation need Email-to-Case and escalation rules.

Manual triage by unassigned queue members checking mailboxes hourly

Why it fails: Hourly manual triage cannot meet the immediate-notification requirement, since keyword detection and case creation would depend on human availability rather than automated parsing. It is tempting because unassigned queues do provide a fallback for routing unmatched emails, and manual review would be the choice when volumes are tiny and no automation budget exists.

Disable all standard validation rules to speed up API data integration speeds.

Why it fails: Disabling validation rules removes the very checks that prevent orphaned or mismatched Account and Contact references on Cases, directly undermining data integrity. It is tempting when API throughput matters, but validation rules should be tuned or bypassed selectively per integration user, not disabled globally.

Rely solely on user training without technical enforcement mechanisms.

Why it fails: Training alone leaves no technical enforcement, so agents can still create Cases with missing or mismatched Account and Contact links. It is tempting because it avoids configuration effort, but data integrity requires validation rules and required-field enforcement on the lookup relationships.

Convert all lookup relationships to text fields to bypass data model constraints.

Why it fails: Converting lookups to text fields destroys the relationship model, preventing Case association with Account and Contact records and breaking reporting and automation. It is tempting as a way to avoid validation friction, but lookups with validation rules are what enforce referential integrity.

Omni-Channel Supervisor real-time metrics dashboard.

Why it fails: Omni-Channel Supervisor metrics report agent presence, capacity and work-item routing in real time; they expose nothing about API callouts or ERP synchronisation errors. API failures are diagnosed through API Usage notifications and debug logs. Supervisor metrics are correct for live queue and agent performance monitoring.

Knowledge article version history.

Why it fails: Knowledge article version history tracks revisions to article content and publication state; it holds no record of inbound API requests or their error responses. ERP synchronisation failures are investigated with API Usage notifications and debug logs. Version history is correct when auditing Knowledge article changes.

Standard Case History related lists on individual records.

Why it fails: Case History related lists record field changes made to a Case record over time; they do not capture API request payloads, status codes or integration errors. API failures require API Usage notifications and debug logs. Case History is correct for auditing user edits to individual case fields.

Automatically close the Salesforce org

Why it fails: Milestone actions are limited to email alerts, field updates, and outbound messages; closing a Salesforce org is an org-wide administrative operation no milestone can invoke. It is tempting because milestones drive automation, but that automation cannot deactivate an entire org.

Delete the parent Account record

Why it fails: Milestone actions cannot delete records; deletion is a data-management operation governed by sharing and delete permissions. It is tempting because violations may signal a stale account, but the available actions are email alerts, field updates, and outbound messages only.

Downgrade the user's license

Why it fails: Milestone actions cannot modify user licences; licence assignment is a user-management task performed through profiles, permission sets, and setup. It is tempting because milestone violations concern entitlement, but the supported actions are notifications and record updates, not licence downgrades.

Salesforce automatically logs the user out of the console session.

Why it fails: Salesforce does not terminate console sessions at the tab limit; it blocks further tabs and displays a warning instead. Logging out is tempting because session termination is a genuine App Manager console setting, but it applies to idle-session timeouts, not to workspace tab thresholds.

All open subtabs are permanently deleted from the database.

Why it fails: Reaching the tab limit blocks new tabs from opening; it never deletes existing subtabs, which persist in the App Manager database regardless of console state. The option tempts because tab limits do govern workspace capacity, but they act as an opening restriction, not a destructive cleanup mechanism — deletion would require explicit administrative action.

Configure automatic tab closure timers based on user inactivity.

Why it fails: Console Navigation Rules determine tab and workspace opening behaviour, not inactivity-based closure timers. Automatic tab closure is a separate session or console setting, making this tempting because both concern tabs, yet the navigation rule engine exposes no such timer option.

Set automated background refresh intervals for open subtabs.

Why it fails: Console Navigation Rules govern which tabs, subtabs and workspaces open or focus for a user, not refresh scheduling. Background refresh intervals are configured elsewhere in App Manager, so this is tempting because refresh timing sounds like console behaviour, but it belongs to a different settings area.

Define color-coding rules for high-priority workspace tabs.

Why it fails: Console Navigation Rules control tab and workspace navigation behaviour, not visual styling. Colour-coding of tabs is configured through workspace or theme settings, so this is tempting because it references tabs, but the navigation rule configuration provides no colour-coding capability.

Exporting all interaction notes to external notepad applications

Why it fails: Exporting notes to external notepads forces agents to leave the console and re-key data, adding handling time rather than cutting it. It is tempting because external note tools genuinely help offline documentation or personal record-keeping, but the requirement is in-console case creation speed, which this actively undermines.

Manual entry of all case fields without default values or picklist dependencies

Why it fails: Manual entry of every field with no defaults or dependent picklists lengthens each call and invites errors, directly raising Average Handle Time. It is tempting because unrestricted manual entry suits one-off, highly variable cases, yet the scenario demands streamlined, repeatable phone case creation where automation is the point.

Requiring managerial sign-off for every inbound phone call log

Why it fails: Managerial sign-off on every inbound call log inserts an approval wait into each interaction, inflating handling time instead of reducing it. It is tempting because approval gates genuinely suit high-risk or compliance-sensitive transactions, but routine phone case logging is not such a scenario and the delay defeats the stated goal.

Sends automated customer satisfaction surveys.

Why it fails: Split View changes only how records and lists are displayed to agents; survey dispatch is handled by automation, flows or Feedback Management configuration. Sending satisfaction surveys is an automated process, unrelated to console pane layout.

Automatically deletes duplicate case records.

Why it fails: Split View is purely a layout arrangement showing list and detail panes side by side; it contains no deduplication logic, which runs through matching and duplicate rules. Automatic duplicate deletion belongs to data-quality configuration, not console presentation.

Translates incoming customer chat messages in real time.

Why it fails: Split View divides the console into list and record panes so agents work without losing context; it performs no language translation, which relies on translation services or Einstein features. Real-time chat translation is a separate capability, not a Split View benefit.