Hybrid IT
What this domain tests
Hybrid IT tests workload placement across on-premises, colocation, edge, and public cloud, and the operational model that connects them. The exam expects a defensible placement decision based on latency, data gravity, compliance, cost, and skills, not a slogan that everything goes to cloud.
Core rules
- Place latency-sensitive and data-heavy workloads close to users and data; place elastic, bursty, or experimental workloads where scale is cheap.
- Data gravity and egress fees often decide hybrid economics more than compute price.
- Regulatory and sovereignty requirements can force on-premises or in-country placement.
- Hybrid IT needs a common operating model: monitoring, identity, backup, and security across environments.
- HPE GreenLake can provide a private-cloud experience on customer premises or in a colo, with cloud-like consumption.
Worked example
A retailer runs ERP on-premises because of latency and integration, wants disaster recovery in a colo, and runs seasonal web front ends in public cloud. Reason: ERP stays close to the warehouse systems and avoids re-architecture; colo provides a second site without building one; public cloud absorbs seasonal peaks. GreenLake for private cloud standardizes the on-premises and colo operations. Moving ERP to public cloud would add latency and migration risk without addressing the seasonal peak.
Traps
Assuming public cloud is always cheaper; ignoring egress and integration costs; treating hybrid as two disconnected estates; forgetting skills and operations; placing regulated data without checking sovereignty.