Which three methods ensure that Cisco Unified Contact Center Enterprise route requests that experience unexpected scripting conditions are counted as default-routed rather than errors in call type…

Question

Options

• ATest your scripts to ensure that all routing logic is correct.
• BConfigure default labels for each dialed number using the Configuration Manager.
• CInclude a Termination node with Termination type of default label for all scripts in which there is some unexpected input.
• DIn all routing scripts, account for failure by creating a path for calls that encounter unexpected conditions.
• EConfigure default labels for each skill group using the Configuration Manager.
• FIn all routing scripts, account for failure by triggering one of the congestion control features to handle the call.

• A
  4% (2)
• B
  76% (37)
• E
  14% (7)
• F
  6% (3)

Explanation

In Cisco UCCE, when a call hits an unexpected scripting condition, the system needs a valid routing target to send the call to - and how that routing is configured determines whether the call is logged as default-routed (intentional fallback) or an error in call type reports. Option B ensures every Dialed Number (DN) has a fallback label configured at the system level, so calls with no script path still reach a destination. Option C places an explicit Termination node (type: default label) inside scripts, catching unexpected branches before they become errors. Option D adds logic within the script itself to route calls that hit unexpected conditions down a known failure path, preventing unhandled exceptions.

Why the distractors are wrong:

• A is good practice but doesn't guarantee unexpected conditions won't occur in production - testing reduces bugs, it doesn't eliminate the need for fallback routing.
• E is incorrect because default labels are configured per Dialed Number, not per skill group; skill groups don't have default labels in this context.
• F is wrong because congestion control features are designed for high-load scenarios, not for handling unexpected scripting errors - triggering them inappropriately would distort reporting further.

Memory tip: Think B-C-D as three defensive layers - system-level (B: DN default label), script-level exit node (C: Termination node), and script-level logic (D: failure path) - each catching what the previous layer might miss.

No community discussion yet for this question.