A company runs a classic release pipeline with three stages, manual approvals and shared variable groups. Which migration plan carries the least production risk?
Show answer and explanation
Answer: D
YAML stages correspond closely to classic release stages. Environments keep their approval and check configuration, and variable groups link the same way, so the new pipeline inherits existing controls. Validating in a non-production environment first, then cutting over, limits risk. Deleting and rebuilding in production is risky, dropping release orchestration loses approvals, and staying classic forever blocks versioned pipeline definitions.
Why the other options are wrong
- A. Rewriting the release directly in production on the day of change gives no rehearsal, so any mistake lands on live customers with no tested fallback.
- B. Dropping the deployment stages and their approvals removes the controls that owners and auditors expect, so this is not a safe migration path.
- C. Keeping classic indefinitely avoids migration risk but leaves deployments outside source control and blocks the versioned, reviewable pipeline definitions the team wants.