Feature flags plus a tiny traffic slice will validate a payments change before citywide enablement. Which deployment strategy does this describe?
Select an answer to reveal the explanation.
Short Explanation
Flags let you hide a feature; a tiny traffic slice lets a few real payments prove it — together that is canary thinking. Validate small, then flip the flag wider. That is not "everyone on day one" or "patch every box with the flag welded off."
Full Explanation
Canary releases validate new behavior with limited real traffic; feature flags often complement that pattern by controlling which users see the change without redeploying. Citywide day-one enablement and fleet-wide in-place changes without progressive exposure increase risk. Blue-green may still use flags, but the defining control here is the limited traffic validation path.