AZ400-Q: migrate a Classic pipeline safely
A team is moving from a Classic Azure Pipelines build definition to YAML. Its current pipeline uses UI variables, a nightly schedule, and a production service connection. Which action is essential before retiring the Classic pipeline?
- A) Export YAML, delete the Classic pipeline immediately, and rely on default project settings.
- B) Recreate and review variables, triggers, permissions/service connections, environments/checks, and retention; run the YAML pipeline in parallel and compare behavior. ✓
- C) Copy only the build tasks into a YAML file; UI settings are automatically inherited.
- D) Convert the pipeline to a GitHub Actions workflow, which automatically preserves Azure DevOps approvals.
Answer: B. A pipeline definition includes more than its visible tasks. Migration must deliberately account for surrounding configuration and validate behavior before cutover.
Why not the others: Export is a starting point, not an assurance. UI settings and approval/security configuration do not automatically become equivalent YAML. Moving platforms adds another migration boundary.