500-440 · Question #64
Which three WAN/MAN configurations are valid in the Cisco Unified Contact Center Enterprise clustering over the WAN deployment model? (Choose three.)
The correct answer is A. A highly available visible network WAN/MAN/DWDM and a dedicated private network WAN. C. A highly available MPLS WAN shared by the visible and private networks where the private D. A highly available DWDM/CWDM network shared by the visible and private networks with a sub-. UCCE Clustering over the WAN - Valid WAN/MAN Configurations Options A, C, and D are correct because Cisco UCCE Clustering over the WAN (CoW) requires that the private network (which carries inter-cluster SQL replication and heartbeat traffic) have sub-millisecond latency and…
Question
Which three WAN/MAN configurations are valid in the Cisco Unified Contact Center Enterprise clustering over the WAN deployment model? (Choose three.)
Options
- AA highly available visible network WAN/MAN/DWDM and a dedicated private network WAN.
- BA highly available MPLS WAN shared by the visible and private networks with a 2 second
- CA highly available MPLS WAN shared by the visible and private networks where the private
- DA highly available DWDM/CWDM network shared by the visible and private networks with a sub-
- EAll traffic is converged on a single MPLS network by using appropriate QoS markings and
- FA highly available DWDM/CWDM network shared by the visible and private networks with 1500
How the community answered
(28 responses)- A82% (23)
- B11% (3)
- E4% (1)
- F4% (1)
Explanation
UCCE Clustering over the WAN - Valid WAN/MAN Configurations
Options A, C, and D are correct because Cisco UCCE Clustering over the WAN (CoW) requires that the private network (which carries inter-cluster SQL replication and heartbeat traffic) have sub-millisecond latency and high availability. Option A works because it uses a dedicated private WAN, physically separating that sensitive traffic. Options C and D are valid because MPLS (C) and DWDM/CWDM (D) can share both visible and private traffic - provided the private network traffic still meets its strict, near-zero latency threshold (the truncated options imply compliant latency guarantees).
Why the distractors fail:
- B is invalid because a 2-second latency on the shared MPLS WAN grossly exceeds what the private network allows - database replication would break.
- E is invalid because converging all traffic onto a single MPLS network with only QoS doesn't guarantee the sub-millisecond latency isolation the private network demands; QoS alone is insufficient.
- F is invalid because 1500 ms (implied by the truncated text) is also far too high for private network communication.
Memory tip: Think "the private network is picky - it needs its own lane or a proven fast-lane (DWDM/MPLS with sub-ms guarantee). Any answer suggesting high latency (2s, 1500ms) or no lane separation (single converged MPLS + QoS only) is a trap."
Topics
Community Discussion
No community discussion yet for this question.