In the congestion control feature of Cisco Unified Contact Center Enterprise, which four options handle the calls that are to be throttled? (Choose four.)

Question

Options

• ATreat the call with Dialed Number Default Label.
• BQueue the call and play a message, then release the call.
• CTreat the call with System Default Label.
• DTerminate the call with a Dialog Fail or RouteEnd.
• ETransfer calls to an available IVR port.
• FSend a Release Message to the routing client.
• GOffer Courtesy Callback to the caller, then terminate the call.
• HTransfer the call to the Cisco Unified Communications Manager hunt group.

• A
  91% (51)
• B
  2% (1)
• G
  2% (1)
• H
  5% (3)

Explanation

When Cisco UCCE's congestion control feature throttles a call, it must act quickly at the routing layer before consuming full processing resources - which is why A, C, D, and F are correct. Using a Dialed Number Default Label (A) or System Default Label (C) immediately redirects the call to a pre-configured fallback destination without invoking full scripting logic. Terminating with Dialog Fail or RouteEnd (D) signals the routing client that the call cannot be processed, while sending a Release Message (F) instructs the routing client to disconnect the call at the signaling level - both are clean, low-overhead dispositions.

The distractors (B, E, G, H) are wrong because they describe resource-consuming actions that defeat the purpose of throttling: queuing + playing a message (B), transferring to IVR (E), or offering Courtesy Callback (G) all require system resources you're trying to protect, and transferring to a CUCM hunt group (H) is a routing action outside UCCE's congestion control scope.

Memory tip: Think of the four correct answers as "drop or redirect with minimal effort" - two use default labels to redirect fast (A, C), and two use signaling messages to drop cleanly (D, F). If an option requires the system to do work for the caller (queue, play audio, callback, transfer), it's not a congestion control mechanism.

No community discussion yet for this question.