Cloud Concepts: Value, Models, and Architecture Principles
What to know
The Cloud Concepts domain tests whether you understand why organizations move to the cloud and how to reason about trade-offs, not whether you can recite marketing slogans. Be able to explain the difference between capital expenditure and operational expenditure, the economics of elasticity (pay only for what you consume), and the shift from fixed capacity planning to on-demand provisioning. Know the service models clearly: IaaS gives you virtualized compute, storage, and networking; PaaS abstracts the operating system so you manage only applications and data; SaaS delivers a finished application. Know the deployment models (public, private, hybrid, and community) and when hybrid is the honest answer - data residency, legacy integration, or burst capacity.
Traps
Questions often describe a customer responsibility and ask which model it implies. The classic trap is assuming PaaS removes all security duties; you still own data, identities, and application code. Another trap is confusing high availability with fault tolerance and with disaster recovery: HA absorbs component failure with minimal interruption, fault tolerance continues with zero interruption at higher cost, and DR restores service after a regional loss. Also watch for "lift and shift" framed as cloud-native; re-architecting is a different migration strategy.
Architecture principles
Understand loose coupling, stateless design, horizontal scaling, and designing for failure. Recognize that elasticity is not the same as scalability: scalability handles growth, elasticity handles fluctuation.
Worked rule of thumb
If a workload needs to survive the loss of an entire region with a defined recovery time objective, the answer involves multi-region replication and a tested DR plan - not simply "use multiple availability zones." Zones protect against a data-center failure; regions protect against geographic failure. When an answer choice mentions only one zone or one region, check whether the scenario's scope exceeds it.
Study approach
Practice mapping a business requirement (cost reduction, compliance, speed to market) to the cloud characteristic that satisfies it, and be ready to name the trade-off you accept.