5V0-35.21 · Question #22
A customer has multiple vCenter Servers in an East Coast datacenter (primary site) and one vCenter Server in each remote datacenter location (Chicago, Japan, and San Francisco). The following informat
The correct answer is B. Deploy vRealize Operations cluster in the primary site and a Remote Collector node in each. Option B is correct because Remote Collector nodes are specifically designed for high-latency, geographically distributed environments. They pre-process and forward monitoring data from remote vCenter instances back to the main cluster over WAN links - VMware supports up to 100ms
Question
A customer has multiple vCenter Servers in an East Coast datacenter (primary site) and one vCenter Server in each remote datacenter location (Chicago, Japan, and San Francisco). The following information is known:
- They want to monitor vCenter Server Instances in all these datacenter
locations from single product UI.
- Network latency between these datacenters is 50 milliseconds.
Which vRealize Operations cluster configuration is valid?
Options
- ADeploy vRealize Operations cluster in the primary site and Data nodes in each remote site.
- BDeploy vRealize Operations cluster in the primary site and a Remote Collector node in each
- CDeploy vRealize Operations cluster in the primary site and a Witness node in each remote site.
- DDeploy vRealize Operations cluster in the primary site and a Primary Replica node in each remote
How the community answered
(24 responses)- A4% (1)
- B83% (20)
- C8% (2)
- D4% (1)
Explanation
Option B is correct because Remote Collector nodes are specifically designed for high-latency, geographically distributed environments. They pre-process and forward monitoring data from remote vCenter instances back to the main cluster over WAN links - VMware supports up to 100ms latency for Remote Collectors, making 50ms perfectly acceptable. This allows a single vRealize Operations UI (the primary cluster) to monitor all sites.
Why the distractors fail:
- A (Data nodes in remote sites): Data nodes are analytics cluster members that require very low latency (<5ms) to the primary node to participate in distributed computation. Placing them across a 50ms WAN link would cause cluster instability.
- C (Witness nodes in remote sites): Witness nodes exist solely to provide a tiebreaker vote in stretched cluster split-brain scenarios - they do not collect or process monitoring data from remote vCenters.
- D (Primary Replica nodes in remote sites): A Primary Replica provides HA failover for the primary node within a single cluster. Like Data nodes, it requires low-latency LAN connectivity, not a 50ms WAN link.
Memory tip: Match the word "remote" - remote datacenters get Remote Collector nodes. Everything else (Data, Witness, Primary Replica) belongs on the same LAN as the primary cluster. If latency is mentioned in the question, Remote Collectors are almost always the answer.
Topics
Community Discussion
No community discussion yet for this question.