When should the advanced sizing guide be used instead of the basic sizing guide in the vRealize Operations Manager (vROps) online Sizing tool?

Question

Options

• AWhen vROps High Availability or Continuous Availability features are going to be enabled
• BWhen the monitored environment will have more than 16 vSphere clusters
• CWhen additional management packs are going to be implemented
• DWhen the vROps analytics nodes will be distributed across more than one physical data center

• B
  3% (1)
• C
  90% (28)
• D
  6% (2)

Explanation

Option C is correct because management packs extend vROps beyond its default vSphere monitoring to cover additional solutions (NSX, vSAN, third-party products, etc.), each contributing extra objects, metrics, and collection overhead that the basic sizing guide doesn't account for - the advanced guide includes inputs for these additional data sources to produce an accurate capacity recommendation.

Option A is wrong because High Availability and Continuous Availability are standard deployment topology options handled within the basic sizing workflow. Option B is wrong because the number of vSphere clusters is a straightforward numeric input the basic guide accepts without needing the advanced path. Option D is wrong because distributing analytics nodes across physical data centers is a network/topology concern, not a driver for switching sizing guides.

Memory tip: Think "packs = more metrics = advanced math." Any time you add a management pack, you're adding an entirely new product's worth of data, so the sizing calculation must get more advanced to stay accurate.

No community discussion yet for this question.