Your release must reach the secondary region only after the primary region has stayed healthy for five minutes. Which workflow layout enforces that order?
Show answer and explanation
Answer: C
In GitHub Actions, the needs keyword expresses ordering between jobs. Making the verification job depend on the primary deployment and making the secondary deployment depend on verification forms a chain. The verification job probes the primary region for the full five minutes and exits non-zero on failure, which prevents the dependent secondary job from running. Parallel jobs and matrices start together, and scheduled workflows run on timers without any gate between regions.
Why the other options are wrong
- A. Concurrent jobs have no ordering, so the secondary region would be deployed before primary health is known. A later check cannot prevent a deployment that has already started.
- B. A matrix launches its legs together, so the secondary deployment would not wait for the primary to prove healthy. Failing legs do not halt the others by design.
- D. Timed workflows run at fixed clock times and never inspect the state of the primary region. Nothing links the secondary release to a health result.