AZ400-Q: order dependent deployments

A release changes a database schema and an application that requires the new schema. The team must prevent the application deployment from running when schema migration fails. Which design is best?

  • A) Put migration in an earlier stage/job and make the application deployment explicitly depend on its successful completion. ✓
  • B) Run migration and application deployment in parallel to reduce release time.
  • C) Add a longer timeout to the application deployment.
  • D) Run the application deployment first; it will retry until the schema exists.

Answer: A. Express the dependency in the pipeline graph and gate later work on success. This creates a visible, auditable ordering rule.

Why not the others: Parallel execution races. A timeout does not order work. Retrying against an incompatible schema is not a reliable deployment strategy.

jobs-steps · pipeline-yaml · deployment-automation