Academy/VMware Cloud Operations 8.x Professional (2V0-32.24)/Capacity Planning & What-If Scenario Modeling
This lab targets VCF 9.0

Capacity Planning & What-If Scenario Modeling

VCF 9.0Intermediatevcp-foundation⏱ 105 min

Objectives

  • Model cluster growth, analyze capacity exhaustion timeline, and recommend infrastructure expansion using what-if scenarios.

Prerequisites

VCF lab environment deployed and operational

Lab Environment

VCF 9.0 lab environment with VCF Operations 9.0; UI paths in this lab follow VCF Operations 9.0. The 2V0-32.24 Cloud Operations 8.x exam itself targets vRealize Operations 8.6, vRealize Log Insight 8.8 and vRealize Suite Lifecycle Manager 8.8, so map any 8.x exam detail accordingly.

Tasks

Task 1 Capacity Planning & What-If Scenario Modeling

Model cluster growth, analyze capacity exhaustion timeline, and recommend infrastructure expansion using what-if scenarios.

Step 1

Analyse the current capacity state.

  • In VCF Operations click Assess under Capacity in the left menu and open the data center that holds the prod cluster (or open the prod cluster itself and use its Capacity tab)
  • Capture: total capacity, used, free, growth rate, time remaining (the capacity engine projects from history; Reserved Capacity and the HA buffer reduce the usable figure)
  • Example result: 400 GB total, 200 GB free, 10 GB/week growth, 20 weeks remaining
Step 2

Scenario 1 - Do nothing (baseline).

  • Projected exhaustion: 200 GB / 10 GB per week = week 20 from today
  • Risk: the cluster crosses 80% used (320 GB of 400 GB, i.e. 120 GB more) at 120 GB / 10 GB per week = week 12
  • Business impact: procurement lead time is 8 weeks, so order hardware by week 4 to land it before the 80% threshold, and by week 12 at the latest to land it before exhaustion
Step 3

Scenario 2 - Add two hosts (300 GB memory in total). Model it in Capacity > Plan > What-If Analysis > New > Infrastructure Planning: Hyperconverged, adding two hosts of the prod host profile.

  • New capacity: 400 GB + 300 GB = 700 GB
  • New free: 200 GB + 300 GB = 500 GB
  • Time remaining: 500 GB / 10 GB per week = week 50 from today
  • Cost: 2 hosts x USD 80K = USD 160K capital
  • Conclusion: extends the runway to about week 50 (roughly a year) and fits the business planning cycle
Step 4

Scenario 3 - VM consolidation (reduce demand by 30 GB). Model it in What-If Analysis > New > Workload Planning: Hyperconverged, choosing Remove workloads and selecting the 20 candidate VMs from the Reclaim tab under Capacity > Optimize (idle VMs; oversized VMs are on the Rightsize tab).

  • New free: 200 GB + 30 GB = 230 GB
  • Growth also slows slightly once the idle VMs are gone: assume 9.5 GB per week
  • Time remaining: 230 GB / 9.5 GB per week = about week 24 from today
  • Cost: no capital; about 15 hours of ops time to migrate or retire the VMs
  • Conclusion: buys roughly a month, not enough on its own
Step 5

Scenario 4 - Hybrid (one host plus consolidation). Combine the two scenarios in What-If Analysis (one host added, 20 VMs removed) and compare the projections side by side.

  • Add one host (150 GB): 400 GB + 150 GB = 550 GB
  • Consolidate 20 VMs: 30 GB reduction
  • New free: 350 GB + 30 GB = 380 GB
  • Time remaining: 380 GB / 9.5 GB per week = week 40 from today
  • Cost: 1 host (USD 80K) plus 15 hours of ops time
  • Conclusion: the best balance of capital and effort
Step 6

Present to Finance and leadership. Build a what-if comparison dashboard (Infrastructure Operations > Dashboards & Reports).

  • Chart: time remaining in weeks for each scenario
  • Table: scenario name, cost, effort, timeline impact
  • Recommendation: "Scenario 4 - Hybrid (one host plus consolidation). Extends capacity to about week 40 (roughly nine months) for USD 80K and 15 hours of ops time."
Step 7

Implement the recommended scenario.

  • Commit the Scenario 4 What-If scenario (Capacity > Plan > Committed Scenarios) so the capacity engine reserves the planned demand
  • Raise the change request: "Procure one host (150 GB memory) for the prod cluster"
  • Schedule the VM consolidation (move 20 VMs to the test cluster) and run the reclaim actions from Automation Central if they are deletions or power-offs
  • Validate afterwards: re-open Capacity > Assess and confirm time remaining matches the Scenario 4 projection

Validation Gate

Check: Verify lab completion

Expected: Lab exercise completed successfully

Common Errors

Capacity forecast based on linear growth when actual growth is seasonal
Fix: VCF Operations capacity forecasting uses historical data to project future utilization. If workloads are seasonal (retail: Q4 spike, healthcare: flu season), linear projection underestimates peaks. Use what-if scenarios: model peak periods separately and set procurement triggers based on peak projections, not average.
What-if scenarios not accounting for HA overhead
Fix: A what-if scenario that adds 50 VMs must also account for N+1 HA capacity. If the cluster currently uses 75% capacity with N+1 reserved, adding 50 VMs that consume 10% capacity puts the cluster at 85% — above the 80% recommended threshold for HA + headroom. Include HA overhead in every capacity scenario.
Not setting procurement lead time triggers
Fix: Capacity forecast showing 'will exceed 80% in 90 days' is useless if hardware procurement takes 120 days. Set alert triggers at: current utilization + growth rate × (procurement lead time + buffer). This ensures alerts fire early enough to procure and install hardware before capacity is exhausted.

Final Validation

Lab completed successfully

✓ All steps completed → No errors observed

Cleanup / Restore

• Revert to snapshot if needed

Design Reflection (VCDX)

Capacity planning is a VCDX design component. Panelists test whether your design includes growth projections, procurement triggers, and seasonal capacity modeling.

⚠ Known Pitfalls

Using linear capacity projections for seasonal workloads — underestimates peak demand.
Setting capacity alerts without accounting for hardware procurement lead time — alerts fire too late to act.
Was this page useful?
Type to search. ↑ ↓ to move, Enter to open, Esc to close.