Requester: Cedar Operations lead. Why: a zone interruption must not remove the entire web tier. Starting data: an existing VPC, subnets, security group, and private PostgreSQL database. Deliverable: two-zone load balancing and scaling, HTTPS access, Multi-AZ database, a seven-day backup window, and a checked handoff decision.
Cedar Operations wants a two-zone web configuration with protected database recovery. You will work through one account, carrying every accepted change into the next step. The initial resources are a fictional company's starting configuration, not a blank cloud account. Your deliverable is the final account state and the checked decision at the end.
Inspect the named resources before changing them. Earlier work remains part of the requirements, so a later step must preserve it. Some steps use a prepared JSON or YAML file; read its contents and then verify the resulting configuration. Other steps ask for a recommendation supported by the evidence you've established. The final check includes previous requirements as well as the new one, which prevents a quick repair from undoing an earlier protection.