AZ400-Q: avoid overlapping deployments
Two commits merge quickly. The second production deployment starts while the first is still running, causing conflicting changes. What should the workflow use?
- A) More repository tags.
- B) A longer test timeout.
- C) A public IP on the runner.
- D) A concurrency/serialization control scoped to the deployment environment, with a deliberate cancel-or-queue policy. ✓
Answer: D. Deployment concurrency prevents unsafe overlap and makes the behavior for superseded runs explicit.
Why not the others: Tags, timeout, and network addressing do not serialize deployment jobs.
Related
github-actions · pipeline-maintenance · deployment-environment