An administrator has been tasked with configuring vRealize Operations cost drivers to assign a different cost per GB for different storage tiers. Which steps should the administrator complete to…

Question

Options

• AUse a vSphere tag category, assign different tag values for that category to the different tiers in the
• BCreate a custom group in vRealize Operations for each of the storage tiers, and then assign a cost
• CAssign different costs per GB to each of the storage types discovered by vRealize Operations.
• DUse a vRealize Operations tag with different tag values manually configured for each datastore or

• A
  73% (16)
• B
  5% (1)
• C
  14% (3)
• D
  9% (2)

Explanation

Option A is correct because vRealize Operations cost drivers are designed to consume vSphere tag categories and their values to differentiate pricing - an administrator creates a tag category (e.g., "StorageTier"), assigns values like "Gold," "Silver," and "Bronze" to the appropriate datastores in vSphere, then maps a distinct cost per GB to each tag value within vROps cost configuration. Option B is wrong because custom groups in vROps are used for policy and organization purposes, not for directly binding cost-per-GB rates to storage tiers. Option C is misleading because vROps "storage types" refer to protocol/technology classifications (NFS, VMFS, vSAN) discovered automatically - these don't map to business-defined performance tiers. Option D is wrong because vROps-native tags require manual per-datastore configuration and lack the structured category/value hierarchy that vSphere tags provide, making them impractical and unsupported for this use case.

Memory tip: Think "vSphere Tags = Tier Pricing Bridge" - vROps doesn't invent its own tier labels; it borrows the tag category structure you already defined in vSphere to attach dollar values to storage tiers.

No community discussion yet for this question.