Memory hook: Buy an outcome, not a rack.
Must remember
Cloud provides configurable IT resources through managed service interfaces. Its business value can include faster experimentation, elastic capacity and access to global services. Benefits are not automatic: skills, integration, governance, migration cost and organizational resistance can slow transformation. Measure outcomes such as time to launch or customer experience, not only server count.
IaaS leaves more OS/application responsibility to the customer; PaaS manages more platform operations; SaaS provides a finished application. Shared responsibility changes with the model, but customers still manage appropriate identities, data use and configuration.
A public cloud is provider-operated; private cloud serves a dedicated organization; hybrid connects on-premises/private and public environments; multicloud uses more than one cloud. Open source makes source code available under a license; an open standard supports interoperability. Neither guarantees zero migration cost or identical service behavior.
Regions are geographic areas, zones separate failure domains within a region, and edge locations bring selected services closer to users. DNS resolves names; IP addresses identify network endpoints. Latency measures delay; bandwidth measures carrying capacity. Global reach does not override data-residency obligations.
Choose under exam pressure
| Requirement | Choice and reason |
|---|---|
| Need full OS customization | IaaS/VMs. |
| Need an already-built business application | SaaS. |
| Connect existing data center and public cloud | Hybrid architecture. |
Traps
- Cloud can reduce waste but does not guarantee a lower bill.
- Multicloud and hybrid describe different dimensions.
Active recall
1. What does elasticity mean?
Capacity can adjust with demand.
2. Why consider organizational change?
Cloud tools alone do not change slow approvals, skills gaps or ownership.
3. Latency versus bandwidth?
Delay versus transfer capacity.
4. Does SaaS remove all customer responsibility?
No; identity, configuration and lawful data use remain important.
5. Why use open standards?
To improve interoperability and reduce unnecessary dependence on one implementation.