Study guide
1.3 HPE GreenLake Basics: Cloud Platform, Workspaces & Consumption Model
HPE ATP - Storage Solutions HPE0-J81
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Orientation, Customer Requirements, HPE GreenLake & Portfolio
1.1 HPE0-J81 Exam Facts & the HPE ATP - Storage Solutions Certification Path 1.2 Assessing Storage Requirements, Workload Sizing & SLAs 1.3 HPE GreenLake Basics: Cloud Platform, Workspaces & Consumption Model 1.4 The HPE Storage Portfolio: Current Systems, Legacy Platforms & Positioning
2 Chapter 2: HPE Storage Tools, Reference Resources & Cloud Management
2.1 Assessment, Sizing & Configuration Tools: SAF, NinjaSTARS, Ninja Online & OCS 2.2 Compatibility & Reference Resources: SPOCK, QuickSpecs & HPE Support Center 2.3 Cloud Management & AIOps: Data Services Cloud Console, Data Ops Manager & HPE InfoSight
3 Chapter 3: Storage Topologies, Architectures & Implementation Models
3.1 Storage Topologies Compared: DAS, NAS, and SAN Architectures 3.2 Block, File, and Object Storage Implementations & Protocols 3.3 Converged, Hyperconverged (HCI) & Software-Defined Storage (SDS)
4 Chapter 4: Storage Fabrics, Connectivity & HPE GreenLake Services
4.1 SAN Fabric Design, Zoning & Multi-Protocol Storage Networking 4.2 Network Attached Storage Protocols, Shares & Permissions 4.3 HPE GreenLake Offerings for Storage and Data Protection
5 Chapter 5: HPE MSA Gen7 Storage: Hardware, Software & Data Protection
5.1 HPE MSA Gen7 Hardware: Models, Controllers, Drives & Expansion 5.2 HPE MSA Software: Virtual Storage, MSA-DP+, Automated Tiering & SSD Read Cache 5.3 HPE MSA Data Protection & Management: Snapshots, Volume Copy, Remote Snap & SMU v4
6 Chapter 6: HPE Alletra Storage MP B10000 & X10000
6.1 HPE Alletra Storage MP B10000 & X10000: Features and Positioning 6.2 HPE Alletra Storage MP Hardware: Controller Nodes, JBOFs, Switchless & Switched Systems 6.3 B10000 Resiliency & Data Services: All-Active Nodes, RAID 6, Data Reduction & Replication 6.4 Managing HPE Alletra Storage MP: Onboarding, Provisioning, Monitoring & Local Tools
7 Chapter 7: Data Protection Principles, Replication & Disaster Recovery
7.1 Fundamentals of Data Protection: RPO, RTO & Resiliency Architectures 7.2 Storage Snapshots, Clones & Replication Strategies 7.3 Disaster Recovery Planning, Business Continuity & Immutability
8 Chapter 8: HPE StoreOnce, Tape, GreenLake Backup and Recovery & Zerto
8.1 HPE StoreOnce Systems, Catalyst & Cloud Bank Storage 8.2 HPE Tape Solutions: LTO Technology, MSL Libraries & the Offline Air Gap 8.3 HPE GreenLake for Backup and Recovery: Architecture, Policies & Ransomware Protection 8.4 HPE Zerto Software: Continuous Data Protection, Disaster Recovery & Cyber Resilience
1.3 HPE GreenLake Basics: Cloud Platform, Workspaces & Consumption Model
Key Takeaways Explain This Topic AI
HPE GreenLake combines a cloud management platform (the GreenLake cloud console) with optional as-a-service consumption contracts for on-premises infrastructure.
A GreenLake workspace holds users and roles, the device inventory, subscriptions and the services (such as Data Services Cloud Console) that the organization uses.
Cloud management is separate from the payment model: a customer can buy an array outright and still manage it from Data Services Cloud Console.
With GreenLake Flex Solutions, the customer pays a reserved-capacity fee for the commitment plus metered pay-per-use fees for buffer capacity consumed above it, invoiced in arrears.
Only management traffic goes to the cloud; host I/O stays on the local SAN or LAN, so a WAN outage does not interrupt data access.
Last updated: October 2026
HPE GreenLake Basics
Quick Answer: HPE GreenLake is HPE's hybrid cloud platform. It delivers a cloud operating experience for infrastructure in customer data centers, colocation sites and edge locations. Two ideas matter for the exam. First, the GreenLake cloud console is a single place to manage users, devices, subscriptions and services such as Data Services Cloud Console (DSCC) . Second, GreenLake Flex Solutions contracts let customers consume infrastructure as a service: a committed reserved capacity plus on-site buffer capacity that is metered and billed only when used.
HPE's marketing name has shifted over time (HPE GreenLake edge-to-cloud platform, HPE GreenLake cloud, GreenLake). The exam objective uses "HPE GreenLake basics", so this guide uses that term.
Why customers look at GreenLake
Traditional storage purchasing forces a trade-off:
Buying outright (CapEx): the customer owns the hardware but has to size it for growth several years ahead. Capacity bought for year three sits idle in year one.
Public cloud: capacity is elastic, but some data must stay on premises for latency, data sovereignty or regulatory reasons, and moving large data sets out of a cloud costs egress fees.
GreenLake aims to give on-premises infrastructure the cloud's self-service operations and pay-per-use economics, while the data stays where the customer needs it.
The GreenLake cloud platform
The platform is a software-as-a-service console that HPE runs. Its main building blocks are:
Building block What it does Exam-relevant detail
Workspace The organization's container in GreenLake Users, devices, subscriptions and services all live in a workspace
Identity and access Users, roles and single sign-on Role-based access control decides who can manage which service
Devices Inventory of HPE hardware Devices are added (for example by serial number and product number) and then assigned to a service
Subscriptions Entitlements that license devices and services Device and service subscriptions are applied at the workspace level
Service catalog Cloud services to deploy in a region Examples include Data Services Cloud Console, Compute Ops Management and HPE Aruba Networking Central
For storage, the key service is Data Services Cloud Console (DSCC) . DSCC contains the data services used for HPE storage, including Data Ops Manager (onboarding, provisioning, monitoring and upgrading arrays), the block storage service for the Alletra Storage MP B10000, Backup and Recovery and Disaster Recovery . Chapter 2 covers DSCC in detail.
Control plane versus data plane
GreenLake separates management from data access:
The control plane (console, provisioning logic, analytics) runs in HPE's cloud.
The data plane stays on premises. Hosts read and write over the local Fibre Channel, iSCSI or NVMe network.
Arrays initiate outbound HTTPS connections to the cloud. No inbound firewall openings are needed for management.
If the internet link fails, local host I/O, caching, snapshots and replication continue. Only cloud-based administration and telemetry pause until the link returns.
Cloud management is not the same as a consumption contract
This is the most common source of confusion. How a system is managed and how it is paid for are separate decisions:
- Scenario Managed from the GreenLake cloud console? Payment model
- B10000 bought outright Yes; its software and support subscription enables DSCC management CapEx purchase
- B10000 under a GreenLake Flex Solutions contract Yes Reserved capacity plus metered usage
- MSA Gen7 bought outright No; MSA is managed locally with the Storage Management Utility CapEx purchase
- The consumption model: reserved capacity and buffer capacity
Under GreenLake Flex Solutions (formerly GreenLake Flex Capacity), HPE installs infrastructure on the customer site and meters its use:
Reserved capacity (the commitment). The customer commits to a baseline for the contract term and pays a monthly subscription fee, also called the reserved capacity fee, whether or not it is used.
Buffer capacity. HPE installs extra capacity on site that is ready to use immediately. Use above the commitment is metered and charged as a pay-per-use (variable or buffer capacity) fee.
Billing in arrears. Usage is measured during the month and invoiced afterward.
Capacity planning. HPE monitors consumption. When usage approaches the installed capacity, HPE and the customer plan more capacity before the buffer runs out. Installed capacity = reserved (committed) capacity + buffer capacity
- Monthly charge = reserved capacity fee + metered usage above the commitment
- + any fixed services in the contract
- Worked example
A customer commits to 400 TB and HPE installs a buffer above it. In a quiet month the customer uses 380 TB and pays the reserved fee for 400 TB. During a seasonal peak it uses 460 TB and pays the reserved fee plus 60 TB of metered usage. It does not pay for buffer capacity it does not use. Unit prices come from the contract; the exam tests the mechanism, not price lists.
Comparing acquisition models
- Attribute Outright purchase Fixed lease GreenLake Flex Solutions
- Upfront cost Full price on day one Fixed periodic payments Committed monthly fee plus metered use
- Pays for unused capacity Yes Yes Only up to the commitment
- Extra capacity on site Only if bought Only if leased Buffer capacity, billed when used
- Usage metering No No Yes
- Capacity planning Customer Customer HPE monitors and plans with the customer
- When GreenLake fits, and when it may not
GreenLake suits customers with uncertain or seasonal growth, a preference for operating expense, or data that must stay on premises. It is less attractive for a small, stable environment, for a site that cannot connect to the cloud at all, or for a customer that will not accept a minimum commitment and multi-year term. Some HPE products offer disconnected management options for isolated sites.
Common exam traps
"GreenLake is just a lease." A lease finances a fixed configuration. GreenLake meters use, keeps buffer capacity on site and adds cloud management.
"Buffer capacity is prepaid." It is installed with no charge until it is consumed above the commitment.
"Data flows through the cloud." Only management traffic and telemetry do. Host I/O stays local.
"Cloud management requires a consumption contract." It does not; an outright purchase can also be cloud managed.