Which three node types make up the vRealize Operations Cluster? (Choose three.)

Question

Options

• ARemote Collector
• BCloud Connector
• CPrimary
• DWorker
• EData
• FSecondary

• A
  91% (42)
• B
  4% (2)
• D
  2% (1)
• F
  2% (1)

Explanation

A vRealize Operations cluster is built on three distinct node roles: Primary (C), Data (E), and Remote Collector (A). The Primary node is the first installed and serves as the cluster manager, running the UI, API, and analytics controller. Data nodes scale out the cluster by handling metric ingestion, storage, and analytics processing. Remote Collectors are lightweight, read-only nodes deployed at remote or DMZ sites to collect data without storing it, forwarding metrics back to the main cluster.

Why the distractors are wrong:

• Cloud Connector (B): This is a configuration concept/adapter for connecting vROps to cloud accounts (AWS, Azure), not a cluster node type.
• Worker (D): A term borrowed from Kubernetes/general distributed systems - not an official vROps node type.
• Secondary (F): This was used in much older vROps versions (pre-6.x) and has since been replaced by the "Data" node designation; it's a legacy term designed to trick candidates.

Memory tip: Think "P-D-R" - Primary Does Remote work. Primary runs the cluster, Data nodes crunch the numbers, and Remote Collectors gather data from afar. If an answer choice sounds like generic infrastructure jargon (Worker, Secondary) or a product feature rather than a node (Cloud Connector), eliminate it.

No community discussion yet for this question.