Understand cloud service models, regions and availability zones, elasticity, resilience, and how security responsibilities change as services become more managed.
Cloud computing provides on-demand infrastructure and managed services through APIs. The architectural value is not simply renting servers; it is the ability to automate capacity, use managed control planes and design for failure.
IaaS leaves more operating responsibility with the customer. Managed databases and object storage shift more infrastructure operation to the provider, but data classification, identity, configuration and application security remain customer responsibilities.
A region is a geographic service area. Availability zones are isolated locations within a region designed so workloads can spread across failure domains. Multi-AZ design improves availability only when application, data and traffic paths are actually distributed.
Scalability is the ability to handle more load by adding capacity or changing architecture. Elasticity is the ability to add and remove capacity in response to demand. Both require observability and safe automation.
Traditional datacenter expansion often requires capital expenditure before capacity is used. Cloud commonly shifts more infrastructure spending toward operational expenditure tied to consumed services.
OpEx-style consumption can improve flexibility, but on-demand capacity is not automatically cheaper. Rightsizing, shutdown discipline, architecture choices and data-transfer patterns still determine cost.
IaaS, PaaS and SaaS describe how operating responsibility is divided. Public, private, hybrid and multi-cloud describe where services are delivered and how environments are combined.
Public cloud uses shared provider infrastructure exposed as cloud services. Private cloud dedicates a cloud operating model to one organization. Hybrid connects private/on-premises environments with public cloud. Multi-cloud deliberately uses services from more than one cloud provider. None of these labels automatically makes an architecture secure, resilient or inexpensive.
EC2-like VM: provider secures facilities/hypervisor; customer patches guest OS and application.
Managed object storage: provider operates storage platform; customer controls data, encryption choices, public access and IAM.Goal: Classify responsibilities for a VM, managed database and object storage service.
cat > /tmp/cloud-responsibility.csv <<'EOF'
layer,vm,managed_db,object_storage
physical_datacenter,provider,provider,provider
hypervisor,provider,provider,provider
guest_os,customer,provider,provider
application,customer,customer,customer
data_classification,customer,customer,customer
iam_policy,customer,customer,customer
EOFcolumn -s, -t /tmp/cloud-responsibility.csv 2>/dev/null || cat /tmp/cloud-responsibility.csvChoose one row and explain why responsibility changes between service models.Security reviews often fail because teams do not explicitly map responsibility for patching, identity, encryption, backups and logging.
Map provider-neutral Region/AZ concepts to the AWS control plane without creating resources.
aws sts get-caller-identityaws ec2 describe-regions --all-regions --query 'Regions[].RegionName' --output tableaws ec2 describe-availability-zones --query 'AvailabilityZones[].{Zone:ZoneName,State:State}' --output tableOpen each answer only after you have tried to answer the question yourself.
The provider operates more infrastructure layers, while the customer still owns responsibilities such as identity, data and secure configuration.
To reduce exposure to a single-zone failure when the workload is actually distributed across them.
Automatically or operationally adding and removing capacity as demand changes.
Hybrid cloud, because the architecture combines private/on-premises infrastructure with public-cloud services.
Progress is saved in this browser immediately. When you sign in to My Learning, it can also sync across devices.
Attempt the core lab and knowledge checks before marking the module complete.