In a Cisco Unified Communications Manager 8.0 cluster,how is database replication accomplished for run-time data?

Question

Options

• AReplication is through a master database from publisher to all active subscribers.
• BReplication is a mesh from subscriber to subscriber and subscriber to publisher.
• CReplication is a hybrid using both a hierarchical and mesh process.
• DReplication is a push from subscriber to publisher.

• A
  6% (2)
• B
  90% (28)
• C
  3% (1)

Explanation

In CUCM 8.0, run-time data (such as call state and device registration) uses mesh replication - each subscriber node replicates directly with every other subscriber and also back to the publisher, ensuring no single point of failure and faster convergence across the cluster.

Why the distractors are wrong:

• A is wrong because a pure publisher-to-subscriber (hierarchical) model describes configuration data replication, not run-time data - and it would create a bottleneck at the publisher.
• C is wrong because there is no hybrid model for this replication type; the mesh is the mechanism for run-time data specifically.
• D is wrong because subscribers do not push data to the publisher as a primary replication direction - that reverses the actual flow.

Memory tip: Think of run-time data (live call info) as needing to be everywhere fast - a mesh ensures every node talks to every other node directly, like a group chat rather than a phone tree. "Run-time = real-time = mesh."

No community discussion yet for this question.