Independent preparation · CLF-C02
Concept preparation. Implementation, architecture design and troubleshooting are outside the stated target tasks. This collection covers selected topics, not the full exam.
Read the explanation, predict a changed scenario, run an experiment and explain the outcome. Return to a topic after a gap. These local exercises supplement study; they do not replace experience using the real services.
A company needs a server. In 2005 that meant a purchase order, a four-week lead time, a rack, and a machine sized for the busiest day of the year — which sat idle the other 364. Every constraint that shaped how software was built came from that fact.
ExploreYour application runs in one building. That building has one power feed, one cooling system, and one set of network cables. Everything AWS does about resilience is a response to the fact that buildings fail.
ExploreA company put customer records in S3 and the records leaked. AWS was not breached. The bucket was configured to allow public reads. Knowing exactly where the line sits between AWS’s job and yours is the difference between a secure account and a news story.
ExploreThe most common first AWS bill shock is not compute. It is a NAT Gateway nobody remembers creating, charging by the hour and again by the gigabyte, in three Availability Zones.
ExploreChoose an answer to see explanations for every option. Revisit any question without a timer or login.
Shared responsibility
Cloud concepts
Cloud concepts
Billing and pricing
Security and compliance