An architect is designing a monitoring solution for a VMware SDDC, using vRealize Operations Manager (vROps). One of the key requirements is that the solution must ensure that no monitoring data is lo

Question

Options

• ADeploy vROps with a Continuous Availability configuration.
• BDeploy an additional vROps deployment as a standby.
• CDeploy vROps using a High Availability configuration.
• DDeploy and configure remote collector groups.

• A
  76% (25)
• B
  9% (3)
• C
  3% (1)
• D
  12% (4)

Explanation

Continuous Availability (CA) is the correct choice because it deploys vROps nodes across two separate failure domains (e.g., different racks), synchronously replicating all monitoring data so that if an entire rack fails, the surviving set of nodes continues operating with zero data loss. High Availability (option C) is tempting but incorrect - HA only creates a primary/replica pair without guaranteeing cross-rack placement, so a whole-rack failure could take down both nodes simultaneously. A standby deployment (option B) is not a native vROps feature and would inherently involve some data loss during the switchover window. Remote collector groups (option D) extend data collection reach into isolated environments but do nothing to protect the analytics cluster itself from a rack-level failure.

Memory tip: Think of it as a spectrum - HA handles a single node dying, CA handles a whole rack dying. The word "rack" in the question is your cue to go one level higher than HA, which points directly to Continuous Availability.

No community discussion yet for this question.