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

• ABoth sides go out of service for small period of time, Call Router Side A goes active, and Call
• BBoth sides go in service for small period of time, Call Router Side A goes active after negotiations
• CThere is no ability to make ICM configuration changes at Side B
• DThe Call Router Side A stays active, while Call Router Side B goes idle
• EThe Call Router Side B stays active, while the Call Router Side A goes idle

• A
  18% (11)
• B
  10% (6)
• C
  69% (42)
• E
  3% (2)

Explanation

In UCCE duplex architecture, the private network NIC is the direct inter-side communication link between Side A and Side B. When this NIC fails on Side A, each side can no longer directly "see" the other - a split-brain scenario. Since Side A holds device majority (the tiebreaker), it wins and remains active while Side B goes idle, making D correct. Because ICM configuration changes can only be processed by the active Logger/side, and Side B is now idle, no configuration changes can be made at Side B - making C correct.

Why the distractors are wrong:

• A & B: Neither side goes out of service during this event; device majority immediately resolves the split-brain without a service interruption or negotiation period.
• E: This is the opposite of what happens - Side A wins due to device majority and stays active; Side B is the one that goes idle.

Memory tip: Think of "device majority" as an election already decided before the failure. Whoever holds majority never gives up the active role just because the private link breaks - they stay in charge, and the loser can't do anything, including accepting config changes.

No community discussion yet for this question.