AZ400-Q: deploy shared infrastructure before consumers
Two services depend on a shared identity/API infrastructure update. The services must not deploy against the new contract until the shared change succeeds. How should the pipeline express this?
- A) Run all deployments in random order.
- B) Let each service retry forever.
- C) Model the shared deployment as an explicit prerequisite stage/job and gate dependent services on its successful completion. ✓
- D) Put the dependency in a README.
Answer: C. Explicit dependency graph ordering makes the release behavior visible and prevents consumers from racing their prerequisite.
Why not the others: Random/retry/document-only approaches do not enforce dependency order.
Related
deployment-automation · deployment-environment · pipeline-yaml