Requester: Juniper platform lead. Data: original test resources and an independent local account. Deliverable: a declarative storage stack, buffered work, notification fan-out, protected database recovery, error alarm, fictional DNS record, and a checked architecture handoff.
Juniper needs a small service platform whose storage, messaging, database, monitoring, and routing choices fit its recovery plan. 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.