Case Management practice questions

Salesforce restricts total file attachments on a case to 5 MB maximum.

Why it fails: Individual file limits on Salesforce are much higher (up to 2 GB depending on edition), but Email-to-Case has specific agent payload limits.

Maximum email size for Outlook integration is set to 25 MB.

Why it fails: This is an Email-to-Case architecture limitation, not an Outlook integration setting.

Salesforce Content storage limits have been reached for the organization.

Why it fails: Storage limits restrict total org file count/size, not individual incoming email payload size.

Web-to-Case

Why it fails: Web-to-Case generates cases from HTML form submissions on a website, not from email sent to a mailbox. It suits capturing structured web form enquiries. The requirement specifies inbound email to support@universalcontainers.com, which Email-to-Case handles by routing messages into Salesforce as cases.

Case Auto-Response Rules

Why it fails: Case Auto-Response Rules only send automated replies to senders once a case already exists; they do not create cases from inbound email. They suit notifying customers of case receipt. Email-to-Case is the feature that converts messages arriving at support@universalcontainers.com into cases automatically.

On-Demand Email-to-Case

Why it fails: While Email-to-Case is correct, On-Demand is a specific implementation of it, but Email-to-Case is the overarching feature.

Activity Settings

Why it fails: Activity settings control features like recurrence and reminders, not case-specific task rollup closing.

Process Automation Settings

Why it fails: Process automation settings manage workflow and process behaviors globally, not case support specifics.

Case Assignment Rules

Why it fails: Assignment rules handle initial ownership routing.

The escalation rule will throw an error because multiple entries matched the same case.

Why it fails: Cases can match different entries over their lifecycle, but only one active rule entry action set typically governs the active timer.

The case will continue to be evaluated strictly against Rule Entry 1 since it matched upon creation.

Why it fails: Escalation rules can re-evaluate upon modification if configured or naturally shift if criteria changes.

All escalation actions across both rule entries will execute simultaneously.

Why it fails: Escalation actions execute sequentially according to the matched criteria and timer.

Write an Apex trigger that modifies the Case Age field whenever a customer sends an email.

Why it fails: Modifying standard system-calculated fields like Case Age directly via Apex is either restricted or bad practice; Entitlement processes should be used.

Configure standard Case Escalation Rules with custom pause criteria fields.

Why it fails: Standard escalation rules do not support pause/resume criteria based on customer interaction.

Use Process Builder to pause the escalation rule timer using scheduled actions.

Why it fails: Process Builder scheduled actions cannot easily inspect and pause native escalation timers dynamically upon customer reply.

Milestone Elapsed Time

Why it fails: Milestone elapsed time is specific to Entitlement Management, not general case age.

Case Duration Metric

Why it fails: There is no standard field named Case Duration Metric.

Time to Resolution

Why it fails: Time to Resolution is not a default standard field name.

Set up Omni-Channel Skills to assign case teams.

Why it fails: Omni-Channel routes work based on skills, but does not assign case teams.

Use Web-to-Case HTML generator to embed case team member IDs.

Why it fails: Web-to-Case HTML forms cannot natively assign case teams.

Write a validation rule that requires a case team upon creation.

Why it fails: Validation rules enforce data entry requirements, they do not assign case teams.

Use the 'Auto-Send Email' macro checkbox in Setup.

Why it fails: There is no global auto-send checkbox for macros; instructions handle execution flow.

Select the 'Send' button instruction.

Why it fails: The instruction to execute a publisher action is 'Submit'.

Configure a workflow rule to trigger upon macro execution.

Why it fails: Workflow rules cannot detect macro executions directly.

Create a separate active Assignment Rule specifically for VIP customers.

Why it fails: Only one case assignment rule can be active at a time.

Use an escalation rule to pull VIP cases into the queue after 1 minute.

Why it fails: Escalation rules are for aging cases, not immediate initial routing.

Configure a validation rule to force VIP owner IDs.

Why it fails: Validation rules prevent saving; they cannot assign ownership.

Case Escalation Rules

Why it fails: Escalation rules act on time-based criteria after case creation, so they cannot fire immediately on a Critical severity case. It is tempting because escalations do notify and reassign, and they would be correct if the requirement were to escalate cases left unresolved beyond an age threshold.

Case Assignment Rules only

Why it fails: Case assignment rules only set the owner; they cannot send the email notification the requirement also demands. It is tempting because assignment rules do route cases to queues, and they would be correct if the requirement were solely to change the owner to the Executive Escalations queue.

Web-to-Case Auto-Response Rules

Why it fails: Auto-Response Rules only send a fixed acknowledgement email to the case submitter on web-generated cases; they cannot notify an arbitrary internal recipient or reassign the owner. They are tempting because they automate email on case creation, but only for Web-to-Case acknowledgements, not severity-triggered escalation.

At 5:00 PM on the following day

Why it fails: That would account for 12 business hours.

At 1:00 PM on the following day

Why it fails: That would be 24 elapsed calendar hours.

At 9:00 AM on the following day

Why it fails: That would account for 8 hours or a different calculation; 1 PM to 5 PM is 4 full business hours.

Case Auto-Response Rules

Why it fails: Auto-response rules send emails, they do not set incoming field origins.

Organization-Wide Defaults for Cases

Why it fails: OWD controls sharing visibility, not field creation defaults.

Case Object Default Field Values

Why it fails: Standard object field defaults apply generally, but Email-to-Case routing addresses have specific overrides.

Automatically execute batch Apex jobs across multiple orgs.

Why it fails: Macros are UI automation tools for agents, not backend batch Apex execution engines.

Modify user profiles and permission set assignments.

Why it fails: Macros cannot modify administrative security settings.

Web-to-Case automatically encrypts all submitted credit card information in transit.

Why it fails: Salesforce does not automatically redact or encrypt credit card numbers in Web-to-Case unless custom validation/redaction is built.

Web-to-Case forms require agents to manually click 'Submit' for each web visitor.

Why it fails: Web-to-Case is submitted by website visitors automatically without agent intervention.

Chatter post frequency limits for external users.

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

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

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

Configure separate active assignment rules for every single individual agent in the organization.

Why it fails: Creating individual assignment rules for every agent is inefficient; assignment rules route to queues or role/user groups.

Hardcode user record IDs directly inside all rule entry criteria definitions.

Why it fails: Hardcoding user IDs is an anti-pattern; queues or roles should be used instead for maintainability.

Queue member notification settings

Why it fails: Queue member notifications alert internal users, not customers.

Web-to-Case HTML generator settings

Why it fails: Web-to-Case HTML generator does not send auto-responses; rules do.

Enable Chatter Feed Tracking for the Case Team object.

Why it fails: Feed tracking is for collaboration and has no bearing on core record access or case team functionality.

Create a Sharing Rule based on Queue membership to grant record access.

Why it fails: Sharing rules cannot be based directly on queue membership to grant team-level access in this manner.

Assign the 'Manage Case Teams' permission to the queue members' profiles.

Why it fails: Queue members do not need administrative permissions to be part of a case team.

Build a custom Apex trigger on Case to query the Tier 1 Support Queue and update the OwnerId field.

Why it fails: A custom Apex trigger manually queries and sets OwnerId, circumventing the declarative assignment rules the requirement mandates. Triggers are the right tool when logic exceeds rule capabilities, such as cross-object lookups or complex calculations, not for standard queue routing.

Set up Email-to-Case to parse portal form submissions and route them via Case Escalation Rules.

Why it fails: Email-to-Case handles inbound email, not portal form submissions, and escalation rules act on time-based criteria rather than initial routing. It suits email-originated cases needing escalation. Web-to-Case with assignment rules routes portal cases to the Tier 1 queue.

Create a Record-Triggered Flow to assign incoming Web-to-Case records to the queue before assignment rules run.

Why it fails: Assignment rules only execute when cases are created by the web or via the API with the appropriate flag; a record-triggered flow setting OwnerId bypasses them entirely, so the active rules never fire. Flows suit complex field updates, not rule-driven queue routing.

Case Assignment Rules with complex formula criteria.

Why it fails: Assignment rules run once upon case creation and do not dynamically evaluate agent workloads in real-time queues.

Custom Escalation Rules with automatic ownership rotation.

Why it fails: Escalation rules handle time-based breaches, not real-time workload balancing.

Territory Management rules for Service Cloud.

Why it fails: Territory management is used for account and opportunity sales alignment, not real-time support case routing.