A Cisco Unified Contact Center Enterprise solution is designed with geographic redundancy for the central controllers (with separate call routers and loggers). If Call Router Side A has device…

Question

Options

• AThe Call Router Side B stays active, while the Call Router Side A goes idle.
• BThe Call Router Side A stays active, while Call Router Side B goes idle.
• CThere is no ability to make ICM configuration changes.
• DBoth sides go out of service for small period of time, Call Router Side A goes active, and Call
• EThe system operates as it did prior to failure.

• A
  26% (8)
• B
  55% (17)
• D
  13% (4)
• E
  6% (2)

Explanation

In Cisco UCCE's duplex architecture, the private network NIC is the direct interconnect between Side A and Side B used for synchronization. When it fails, each side must rely on its own state to determine authority. Because Side A holds device majority, it asserts itself as the active router and Side B yields - making B correct. The private network link is also required for the Logger pair to synchronize ICM configuration changes; with that link severed, no configuration writes can complete, making C correct.

Why the distractors are wrong:

• A inverts the outcome - the side with device majority wins, not loses.
• D describes a brief dual-outage followed by a failover, which describes a heartbeat timeout scenario, not a private NIC failure with an established majority.
• E is wrong because the inability to make configuration changes is a real operational impact, so the system is not functioning as it did before.

Memory tip: Think "majority rules, but configs freeze." The side holding device majority survives any split-brain event and stays active - but the lost private link kills Logger sync, so no ICM configuration changes are possible until connectivity is restored.

No community discussion yet for this question.