Cloud Concepts Review Quiz

Learning outcomes

By the end of this lesson, the learner can:

1. Explain cloud value in practical terms.
2. Distinguish between agility, scalability, and elasticity.
3. Explain Regions, Availability Zones, and edge locations at a high level.
4. Distinguish deployment models from service models.
5. Explain the shared responsibility model and how it divides ownership between AWS and the customer. AWS's cloud-overview pages frame cloud value around variable expense, agility, elasticity, and global reach, while AWS's infrastructure docs define Regions and Availability Zones and AWS's deployment-model docs define cloud, on-premises/private cloud, and hybrid models. (AWS Documentation)

---

Module 5.1 review snapshot

So far, Module 5.1 has covered four main ideas:

• Cloud value: AWS highlights advantages such as trading fixed expense for variable expense, increasing speed and agility, stopping capacity guessing, and going global in minutes. (AWS Documentation)
• Agility, scalability, and elasticity: agility is speed of provisioning and change, scalability is the ability to grow capacity, and elasticity is adjusting capacity up and down with demand. AWS's cloud-advantages page explicitly describes quick provisioning and scaling up and down as needed. (AWS Documentation)
• Global infrastructure: AWS says Regions are separate geographic areas, Availability Zones are isolated locations within a Region, and multi-AZ deployment is a best practice for availability. AWS also currently states the AWS Cloud spans 123 Availability Zones within 39 Geographic Regions, with more planned. (AWS Documentation)
• Deployment models and service models: AWS defines cloud, private cloud/on-premises, and hybrid deployment models, while service-model thinking helps explain how much of the stack you manage yourself. AWS says cloud-based apps are fully deployed in the cloud, on-premises/private cloud runs locally, and hybrid connects cloud resources with non-cloud resources such as on-premises systems. (AWS Documentation)
• Well-Architected Framework: 6 pillars; Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimization, and Sustainability, for evaluating and improving cloud architectures.
• Cloud Adoption Framework (CAF): 6 perspectives; Business, People, Governance, Platform, Security, and Operations, for planning cloud migration.
• Migration strategies (6 Rs): Rehost, Replatform, Repurchase, Refactor, Retire, and Retain.
• Design principles: Design for failure, decouple components, implement elasticity, think parallel, use disposable resources, and automate everything.

A simple summary is:

This module is about why cloud is valuable, where workloads run, how much is managed for you, who is responsible for what, how to build well-architected systems, how to plan a migration, and which design principles guide cloud architecture. (AWS Documentation)

---

Mixed cloud concepts review quiz

Reflection questions

---

Answer key

A1: B. AWS's cloud-advantages page says cloud computing lets you trade fixed expense for variable expense and pay only when you consume computing resources. (AWS Documentation)

A2: A. AWS says cloud computing increases speed and agility by reducing the time to make resources available from weeks to minutes. (AWS Documentation)

A3: B. Scalability means the system can handle growth by increasing capacity. AWS's cloud-advantages page describes accessing as much or as little capacity as needed. (AWS Documentation)

A4: Scalability means a system can grow to handle more load, while elasticity means capacity can grow and shrink with actual demand. AWS explicitly says cloud computing lets you scale up and down as required. (AWS Documentation)

A5: B. AWS says each Region is a separate geographic area. (AWS Documentation)

A6: A. AWS says Availability Zones are isolated locations within each Region. (AWS Documentation)

A7: Because AWS says it is a best practice to deploy applications in multiple Availability Zones so the application remains available even if one Availability Zone fails. (AWS Documentation)

A8: B. AWS says each Region is designed to be isolated from the other Regions for fault tolerance and stability. (AWS Documentation)

A9: B. At a high level, an edge location is a place closer to users for delivery and lower latency. AWS includes edge locations and CloudFront POPs as part of its broader global infrastructure. (Amazon Web Services, Inc.)

A10: A Region is the larger isolated AWS geographic area, while an Availability Zone is one of the separate isolated locations inside that Region. AWS says Regions are separate geographic areas and AZs are isolated locations within each Region. (AWS Documentation)

A11: B. AWS says a cloud-based application is fully deployed in the cloud and all parts of the application run in the cloud. (AWS Documentation)

A12: B. AWS says hybrid deployment connects cloud-based resources with existing resources that are not located in the cloud, most commonly on-premises infrastructure. (AWS Documentation)

A13: A deployment model asks where the workload runs, such as cloud, on-premises/private cloud, or hybrid. A service model asks how much of the stack you manage versus how much is managed for you. AWS explicitly defines the deployment models, and the service-model explanation is the course's framing built on those managed-vs-lower-level distinctions. (AWS Documentation)

A14: B. IaaS is the more infrastructure-control side of cloud usage. This is the mental model used in the course.

A15: C. AWS Marketplace buyer guidance describes SaaS products as software you subscribe to and access in the software seller's environment. (AWS Documentation)

A16: IaaS gives you more direct control over infrastructure building blocks, while PaaS gives you a more managed platform so you can focus more on the application. This is the framing used in the course.

A17: C. Shared responsibility means AWS handles the cloud infrastructure, while the customer still owns what they build and configure in it. This is the course's framing of the model.

A18: A. EC2. EC2 leaves more operational responsibility with the customer than more managed services such as DynamoDB, Fargate, or managed databases. This is consistent with the service-role comparisons used throughout the course.

A19: B. Reliability. The Reliability pillar ensures workloads perform correctly, recover from failures, and can scale to meet demand.

A20: C. People. The People perspective covers organizational change management, training, skills development, and evolving roles.

A21: B. Rehost. Rehosting ("lift and shift") means moving an application as-is to the cloud without any code modifications.

A22: B. Decouple components (loose coupling). Separating services so they can fail independently without cascading failures.

A23: C. 6. The 6 pillars are: Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimization, and Sustainability.

A24: Example: AWS manages the physical infrastructure and foundational cloud platform operations; the customer manages things like permissions, data design, network exposure choices, or application configuration. This is the shared-responsibility framing used in the course.

A25: Hybrid deployment. AWS explicitly defines hybrid as connecting cloud-based resources with non-cloud resources such as on-premises infrastructure. (AWS Documentation)

A26: It is definitely scalability. It is not fully elasticity unless the system can also shrink capacity when demand drops. AWS's cloud-advantages page explicitly mentions scaling up and down as required. (AWS Documentation)

A27:

1. Deployment model = where the workload lives. Service model = how managed the stack is.
2. Scalable = can grow. Elastic = grows and shrinks as needed.

---

Module 5.1 wrap-up

At this point, a learner should be able to say:

• cloud value includes variable expense, agility, elasticity, and global reach
• Regions are separate geographic areas, and Availability Zones are isolated locations inside Regions
• cloud, private/on-premises, and hybrid are deployment models
• IaaS, PaaS, and SaaS are service-model ways of thinking
• AWS manages the cloud, while the customer still owns what they build and configure in it
• the Well-Architected Framework has 6 pillars for evaluating cloud architectures
• the Cloud Adoption Framework has 6 perspectives for planning cloud migration
• the 6 Rs provide a decision framework for migration strategies
• cloud design principles (design for failure, loose coupling, etc.) guide every architecture decision. (AWS Documentation)

Next lesson

Unit 5, Module 5.2: Security and Access Review Lesson 5.5: IAM, Policies, MFA, and Least Privilege Review