500-440 · Question #65
Which two options are required for the private link in the Cisco Contact Center Enterprise solution? (Choose two.)
The correct answer is A. path diversity B. Layer 3 quality of service prioritization and queuing. Path diversity (A) is required to ensure redundancy on the private WAN link between CCE sites - if one physical path fails, an alternate route keeps the Central Controller connected to Peripheral Gateways, preventing a complete outage. Layer 3 QoS prioritization and queuing (B)…
Question
Which two options are required for the private link in the Cisco Contact Center Enterprise solution? (Choose two.)
Options
- Apath diversity
- BLayer 3 quality of service prioritization and queuing
- Cmax of 1500 ms round trip time latency tolerance
- Dvariable layer subnet masking
How the community answered
(39 responses)- A77% (30)
- C15% (6)
- D8% (3)
Explanation
Path diversity (A) is required to ensure redundancy on the private WAN link between CCE sites - if one physical path fails, an alternate route keeps the Central Controller connected to Peripheral Gateways, preventing a complete outage. Layer 3 QoS prioritization and queuing (B) is mandatory because CCE signaling and real-time data must be prioritized over competing traffic on the WAN to maintain predictable latency and prevent call-handling failures.
C is wrong because 1,500 ms RTT is far too permissive - Cisco CCE design guides specify a maximum of 80 ms one-way (≈160 ms RTT) for the private link; 1,500 ms would make real-time call control unusable. D is wrong because Variable Length Subnet Masking (VLSM) is a general IP addressing technique, not a CCE private link requirement - it has no bearing on link design for this solution.
Memory tip: Think "PQ for Private link" - Path diversity (redundancy) and QoS (quality) are the two pillars. The latency trap (C) is there to catch anyone who confuses CCE's strict ~160 ms RTT limit with a much looser number, so always remember: contact center links must be tight, not tolerant.
Topics
Community Discussion
No community discussion yet for this question.