AZ400-Q: reduce feature-release risk
A team must deploy code to production this week but expose a new checkout flow to 5% of users first. It wants to turn the feature off immediately without redeploying. What should it implement?
- A) A blue-green deployment only.
- B) A feature flag with targeted/progressive exposure, monitored by a rollback decision rule. ✓
- C) A longer production approval.
- D) A private endpoint for the checkout service.
Answer: B. A feature flag separates code deployment from feature exposure. Targeted rollout and telemetry allow the team to stop exposure quickly while retaining the deployed code.
Why not the others: Blue-green changes infrastructure traffic, not necessarily user-level feature exposure. Approval occurs before release. A private endpoint is networking, not release control.