To meet a requirement for protection against data loss in the event of a physical rack failure, an administrator is deploying a vRealize Operation cluster in a Continuous Availability configuration…

Question

Options

• ASecondary Replica node
• BRemote Collector node
• CPrimary Replica node
• DPrimary node
• EWitness node
• FSecondary node

• B
  4% (2)
• C
  94% (49)
• F
  2% (1)

Explanation

In a vRealize Operations Continuous Availability (CA) configuration, the cluster is designed to survive a complete rack failure by distributing three specific node types across separate physical racks: the Primary node (D), Primary Replica node (C), and Witness node (E). The Primary and Primary Replica mirror each other's data in real time, so if the rack containing one fails, the other can take over without data loss. The Witness node acts as a tiebreaker to prevent a split-brain scenario when the Primary and Primary Replica lose communication with each other.

Why the distractors are wrong:

• (A) Secondary Replica node - Not a valid vROps node type; this term doesn't exist in the product.
• (B) Remote Collector node - Used to collect metrics across WAN links or DMZs, but is not part of the CA cluster topology itself.
• (F) Secondary node - Secondary (Data) nodes exist in standard multi-node clusters for analytics scaling, but CA specifically requires the Primary/Primary Replica/Witness triad.

Memory tip: Think "P-P-W" - Primary, Primary Replica, Witness - like three legs of a stool across three racks. Remove one leg (rack failure) and the stool still stands; the Witness is the deciding vote so the remaining nodes know who's in charge.

No community discussion yet for this question.