A customer wants to collect data from 120,000 objects and given the vRealize Operations sizing guide: (See exhibit.) Assuming the customer has no requirements for continuous availability or high…

Question

Exhibit

Options

• A3 Extra Large Nodes
• B6 Large Nodes
• C12 Large Nodes
• D8 Medium Nodes

• A
  2% (1)
• B
  14% (6)
• C
  7% (3)
• D
  76% (32)

Explanation

Option D (8 Medium Nodes) is correct because vROps sizing guides specify that Medium nodes each support approximately 15,000 objects, and 8 × 15,000 = exactly 120,000 - precisely meeting the requirement without over-provisioning. Since the customer has no HA or continuous availability requirement, there is no need to add witness or replica nodes, making a straightforward 8-node Medium cluster the most efficient fit.

Why the distractors are wrong:

• A (3 Extra Large): Extra Large nodes are intended for much larger environments or HA-aware deployments; 3 XL nodes would under-provision or mismatch the sizing tier for this exact object count.
• B (6 Large): Large nodes support more objects per node than needed here, so 6 of them would over-provision the environment unnecessarily and typically align with HA cluster topologies.
• C (12 Large): Twelve Large nodes would dramatically over-provision the environment - roughly double or more what is required - adding unnecessary cost and complexity.

Memory tip: Use the phrase "Match the Math, Skip the HA tax." For non-HA deployments, pick the node size whose capacity multiplied by the node count equals your object count exactly - here, 8 × 15K (Medium) = 120K, with no extra nodes for redundancy overhead.

No community discussion yet for this question.