Every deploy to the city’s staging environment must prove the candidate build has not broken prior behavior before promotion. What pipeline gate fits?
Select an answer to reveal the explanation.
Short Explanation
Staging is the checkpoint before the highway—fail the safety inspection, stay in the lot. Hook the regression suite to every staging deploy and stop promotion on red. Yearly-only or “urgent chat” bypasses are how old bugs return.
Full Explanation
Every deploy to the city's staging environment must prove the candidate build has not broken prior behavior before promotion by triggering the automated regression suite on every staging deploy and blocking promotion when the suite fails. Regression gates tie municipal candidate artifacts to verified behavior in a lower environment, which is the core automated deployment-testing objective. Green infrastructure alone is not green application behavior.
Running regression only once a year during budget season regardless of deploys fails because defects ship for months between rare runs. Promoting on green CloudFormation status alone and skipping application regression fails conceptually by equating stack success with functional correctness. Allowing failed regression to promote if the change was marked urgent in chat fails by creating an urgency bypass that undermines the gate.
Exam caveat: flaky tests must be fixed or quarantined deliberately—silent retries that hide failures recreate the waive-via-chat problem. Operational check: fail a known regression assertion in staging, confirm promotion is blocked, repair, re-run green, and only then allow the higher-environment deploy stage.