Cloud and GreenLake Consumption Models
What this domain tests
Cloud and GreenLake Consumption Models tests whether you can structure and compare pay-per-use, committed, and managed offerings. Know the commercial mechanics: metering, minimum commitment, term, buffer capacity, burst, and what is included in a GreenLake service.
Core rules
- GreenLake is metered consumption with a committed term and a minimum; it is not a conventional lease.
- Buffer capacity absorbs growth; burst allows temporary overage, usually at a defined rate.
- Services include compute, block storage, backup and recovery, and private cloud, each with its own scope.
- GreenLake does not remove the need for support and lifecycle services; confirm what is bundled.
- Compare total cash flow, accounting treatment, refresh, and operations, not just the monthly rate.
Worked example
A customer needs 100 TB of block storage with 20 percent annual growth and wants to avoid a capital purchase. Reason: propose GreenLake block storage with a three-year term, a committed capacity that covers the expected year-one usage, and buffer for growth. Model monthly metering against a capex purchase plus three years of support, power, and refresh. If the customer's usage is flat and low, the minimum commitment may make capex cheaper; say so.
Traps
Calling GreenLake a lease; ignoring the minimum commitment and early-termination terms; comparing a monthly rate to an unloaded hardware price; assuming every workload is eligible; forgetting support and services in the comparison.