Select Two (Multi-Select) Questions

Native multi-tenant ERP synchronization for spare parts inventory

Why wrong: Incorrect. Inventory management is handled by supply chain/ERP systems, not entitlement management.

Automatic generation of outbound invoices for billing

Why wrong: Incorrect. Invoicing requires Salesforce Billing or CPQ, not standard Service Cloud entitlements.

Automatically close the Salesforce org

Why wrong: Incorrect. This is not a valid system action.

Delete the parent Account record

Why wrong: Incorrect. Milestones cannot delete parent account records.

Downgrade the user's license

Why wrong: Incorrect. License modifications cannot be tied to milestone triggers.

Changes to an active process automatically update all historical closed cases.

Why wrong: Incorrect. Historical closed cases are never retroactively altered by process updates.

Milestone types cannot be changed once created, even in draft processes.

Why wrong: Incorrect. Draft processes can be modified freely.

Draft versions can be activated while active versions have open cases without restriction.

Why wrong: Incorrect. Activation rules apply specific version control constraints.

Entitlement Templates applied globally to Leads

Why wrong: Incorrect. Leads do not receive entitlements; entitlements are for Accounts, Contacts, or Contracts related to Cases.

Entitlement Process Assignment Rules in Omni-Channel

Why wrong: Incorrect. Omni-Channel handles routing, not entitlement assignment.

Check that the Debug Log level for Workflow is set to Maximum.

Why wrong: Flows are debugged via Flow Debugger, not workflow log levels.

Verify that external API endpoints are configured for native queue routing.

Why wrong: Native queue routing does not require external API endpoints.

Case Team members were not assigned read permissions on the escalation queue.

Why wrong: Queue permissions do not directly prevent escalation rule execution.

The case was created via Email-to-Case, which bypasses escalation rules entirely.

Why wrong: Email-to-Case cases are fully eligible for escalation rules.

Total closed cases count for the shift

Why wrong: Closed counts are historical performance metrics.

Agent average handle time for the past month

Why wrong: Handle time over a month is historical reporting, not a real-time queue backlog metric.

Average agent login duration

Why wrong: Login duration is tracked in agent reports, not queue backlog views.

Maximum Queue Capacity limit

Why wrong: Capacity limits are configured in Routing Configurations, not presence statuses.

Associated Service Channels

Why wrong: Service channel association is configured when mapping channels, though status applies across channels depending on configuration. Note: Status Type and Status Name are the primary mandatory definitions.

Default Skill Requirement list

Why wrong: Skills are managed via routing rules or flows, not presence statuses.

Embed a Lightning Flow on the utility bar to prompt agents for manual keyword entry.

Why wrong: Manual keyword entry prompts defeat the purpose of automated contextual search in the Lightning Knowledge component.

Set up Omni-Channel Skills-Based Routing to push relevant articles directly to agent work tabs.

Why wrong: Skills-Based Routing routes work items (like cases) to agents based on skills, not articles.

Create a custom Salesforce Console Navigation rule to open articles in primary tabs instead of subtabs.

Why wrong: Console navigation rules control tab behavior, not article search relevance.

Pre-installed Email-to-Case Agent software

Why wrong: Escalation rules do not require Email-to-Case agents to function.

A mandatory Omni-Channel Routing Configuration

Why wrong: Omni-Channel is not required to run standard Case Escalation Rules.

Dashboard-to-Case

Why wrong: Dashboard-to-Case does not exist.

Chatter-to-Case

Why wrong: Chatter-to-Case is not a standard feature name.

Report-to-Case

Why wrong: Report-to-Case does not exist.

Chatter post frequency limits for external users.

Why wrong: Chatter limits do not impact Email-to-Case ingestion.

The number of active Case Assignment Rules in the recycle bin.

Why wrong: Items in the recycle bin do not affect live email processing.

By assigning a macro to the Case feed.

Why wrong: Incorrect. Macros execute pre-built steps but are not the primary native binding mechanism for entitlements.

Through Lead conversion mapping rules.

Why wrong: Incorrect. Leads do not convert into entitlements.

Via Campaign influence reports.

Why wrong: Incorrect. Campaigns track marketing efforts, not entitlements.

Automatic decryption of customer hard drives via email attachment processing.

Why wrong: Salesforce cannot decrypt external customer hard drives.

Native quarantine of malware attachments directly inside standard Case record page layouts without third-party tools.

Why wrong: Advanced malware quarantine typically requires third-party email security gateways or advanced cloud security tools, not native case layout quarantine.

Sharing rules automatically bypass all profile-level Field-Level Security restrictions.

Why wrong: Incorrect. Sharing rules govern record access, whereas Field-Level Security governs field visibility.

Sharing rules execute synchronously in real-time before record creation triggers.

Why wrong: Incorrect. Sharing rule recalculation is processed asynchronously by the sharing rule evaluation engine.

The case priority must be set to High.

Why wrong: Incorrect. Entitlements apply regardless of priority unless specific milestone criteria filter them.

The user must have the 'Manage Entitlement Processes' permission.

Why wrong: Incorrect. Users need read access, but not administrative configuration permissions to receive entitlements.

The case must be assigned to a queue with a public group membership.

Why wrong: Incorrect. Queue assignment does not affect entitlement lookup.

Automatically route unassigned work items to queue members.

Why wrong: Queues handle unassigned work routing, not case teams.

Define agent shift schedules and availability capacity.

Why wrong: Omni-Channel Supervisor handles shift schedules and agent capacity.

Restrict case visibility exclusively to external portal users.

Why wrong: Case teams manage internal collaboration access, not portal visibility restriction.

Rely exclusively on synchronous REST callouts for all high-volume batch data loads.

Why wrong: Incorrect. High-volume data loads should use the Bulk API asynchronously, not synchronous REST callouts.

Hardcode authentication tokens directly in Apex trigger classes for speed.

Why wrong: Incorrect. Hardcoding credentials is a security risk and violates best practices.

Disable all organization-wide sharing defaults during API data loads.

Why wrong: Incorrect. OWD settings cannot be disabled and must remain configured to enforce security.

Multiple Case Assignment Rules can be active simultaneously to handle different channels.

Why wrong: Only one assignment rule can be active at a time for cases.

Assignment rules execute after Apex triggers and record-triggered flows run.

Why wrong: Standard assignment rules run after inserts/updates in the standard order of execution, typically after triggers in certain contexts, but flow execution order can vary.

Inactive assignment rule entries are automatically deleted after 90 days.

Why wrong: Salesforce never automatically deletes inactive rule entries.

Configure Cases as master objects in a master-detail relationship with Accounts.

Why wrong: Incorrect. Cases cannot be master objects in a master-detail relationship with Accounts (Accounts are standard parents).ຮ

Avoid establishing any relationships between Cases and other objects to maximize storage limits.

Why wrong: Incorrect. Relationships are fundamental to Service Cloud data modeling and do not meaningfully impact storage limits.

Delete all historical Assets automatically whenever a parent Account is modified.

Why wrong: Incorrect. Assets should be retained for historical warranty tracking, not deleted on account updates.