For the past 12 hours, a vRealize Operations Cluster has exhibited erratic behavior, and the remote collectors appear to be the cause. The administrator has contacted VMware support, and they have…

Question

Options

• AFull-support bundle from the Primary nodes only
• BLight-support bundle from the Primary nodes only
• CFull-support bundle from all nodes
• DLight-support bundle from all nodes

• A
  10% (3)
• B
  83% (24)
• C
  3% (1)
• D
  3% (1)

Explanation

Option B is correct because the Primary node in a vRealize Operations cluster aggregates and stores logs related to remote collector communication and health, making it the most relevant source for diagnosing remote collector issues - no other nodes are needed. The "Light" bundle type is specifically designed to include only essential recent logs rather than the full diagnostic dataset, directly satisfying the bandwidth constraint of sending the minimum necessary information.

Why the distractors are wrong:

• A (Full, Primary only): The Primary node is the right source, but a Full bundle includes far more data than necessary, violating the bandwidth constraint.
• C (Full, all nodes): Doubles the problem - too much data AND from nodes not implicated in the issue.
• D (Light, all nodes): While Light bundles are appropriately sized, collecting from all nodes adds unnecessary data from uninvolved components; the Primary node alone holds the relevant remote collector logs.

Memory tip: Think "Least data, Primary source" - when bandwidth is tight, go Light; when remote collectors are suspect, the Primary node is their upstream hub and has what support needs. Light + Primary = minimum viable evidence.

No community discussion yet for this question.