500-440 · Question #13
In a Cisco Unified Contact Center Enterprise deployment with geographically redundant central controllers, a new site is added with two new Admin Workstations as the only AWs at the site. Which…
The correct answer is A. 1 - Primary Distributor AW, 1 - Secondary Distributor AW. Option A is correct because a new geographically remote site needs its own Distributor AWs - machines that maintain a local copy of the database - rather than Client AWs, which depend on a Distributor for data. With two AWs and no existing distributor at the site, configuring…
Question
In a Cisco Unified Contact Center Enterprise deployment with geographically redundant central controllers, a new site is added with two new Admin Workstations as the only AWs at the site. Which option is the recommended configuration (AW type) for these two machines?
Options
- A1 - Primary Distributor AW, 1 - Secondary Distributor AW
- B1 - Primary Distributor AW, 1 - Client AW
- C1 - Secondary Distributor AW, 1 - Client AW
- D2 - Client AWs
- E2 - Secondary Distributor AWs
- F1 - Primary Client AW, 1 - Secondary Client AW
How the community answered
(63 responses)- A84% (53)
- B2% (1)
- C2% (1)
- D3% (2)
- F10% (6)
Explanation
Option A is correct because a new geographically remote site needs its own Distributor AWs - machines that maintain a local copy of the database - rather than Client AWs, which depend on a Distributor for data. With two AWs and no existing distributor at the site, configuring one as Primary and one as Secondary Distributor provides both local database access and local redundancy, matching the same redundancy philosophy applied to the central controllers themselves.
Why the distractors fail:
- B & C pair a Distributor with a Client AW - the Client would lose its data source if the single local Distributor fails, giving no true redundancy.
- C also has no Primary Distributor, which breaks the Primary/Secondary sync relationship entirely (a Secondary cannot function without a Primary).
- D (2 Client AWs) is wrong because Client AWs require a reachable Distributor AW; with only clients at the site, all database traffic must cross the WAN to another site's distributor, defeating the purpose of a local site.
- E (2 Secondary Distributors) is invalid - two Secondaries have no Primary to sync from.
- F is a fabricated option; "Primary Client" and "Secondary Client" are not valid AW types in UCCE.
Memory tip: Mirror the pattern - just as geographically redundant central controllers come in Primary/Secondary pairs, a new geographically separated site always gets a Primary/Secondary Distributor pair. "New site = new distributor pair."
Topics
Community Discussion
No community discussion yet for this question.