Only builds that passed the municipal test environment’s automated suite should be eligible for later promotion. How is that eligibility usually expressed?
Select an answer to reveal the explanation.
Short Explanation
The gold sticker goes on after the inspection, not when the box is taped. qa-approved labels (aliases/tags) mark only suite-passing artifacts. Stamping approval at compile time is theater.
Full Explanation
Only builds that passed the municipal test environment's automated suite should be eligible for later promotion, usually expressed by applying a qa-approved label (or equivalent alias/tag) only to artifacts that passed that suite. Labels bind Domain 3 testing evidence to later release steps so production cannot casually select untested bytes. Chain of custody matters for city releases where auditors ask how a build earned production eligibility.
Labeling every build qa-approved at compile time before any environment tests run fails because the label then means nothing about staging results. Promoting unlabeled artifacts whenever a manager replies LGTM in chat fails conceptually as informal approval without artifact binding. Reusing failed-test artifacts by retagging them approved after business hours fails by laundering known-bad builds into the promotion channel.
Exam caveat: label mutation permissions must be restricted to the pipeline role that evaluates test results—humans retagging ad hoc breaks the model. Operational check: pass the staging automated suite, apply qa-approved to that digest or version only, configure prod deploy to require the label, and verify unlabeled or failed builds cannot promote.