An administrator is planning the size of a new vRealize Operations Manager (vROps) platform using the vROps sizing tool. The output of different configurations and sizing information from the tool…

Question

Exhibit

Options

• AHigh Availability
• BContinuous Availability
• CStretched Cluster
• DFault Tolerance

• A
  12% (4)
• B
  79% (26)
• C
  6% (2)
• D
  3% (1)

Explanation

Continuous Availability (CA) is the correct answer because the vROps sizing tool output for this configuration displays a unique topology that includes a witness node alongside primary and replica nodes - the hallmark of a CA deployment. CA provides zero RPO and zero RTO by maintaining a fully synchronized replica cluster, and its sizing output in the tool shows this multi-site, witness-inclusive node layout that distinguishes it from all other options.

Why the distractors are wrong:

• A (High Availability): HA in vROps simply adds a replica node to the primary node cluster for failover - its sizing output lacks a witness node and shows a simpler, single-site topology.
• C (Stretched Cluster): A stretched cluster is a vSAN/vSphere concept, not a named deployment configuration in the vROps sizing tool.
• D (Fault Tolerance): Fault Tolerance is a vSphere VM-level feature (vSphere FT), not a vROps platform deployment model - it doesn't appear as a sizing option in vROps at all.

Memory tip: Think CA = Continuous = Witness. The witness node is the visual giveaway in any sizing diagram - if you see a witness, you're looking at Continuous Availability. HA has no witness; CA always does.

No community discussion yet for this question.