AZ400-Q: migrate a Classic release pipeline
A Classic release pipeline uses UI approvals, variables, and deployment tasks. The team wants YAML delivery but finds no one-click export. What is the correct approach?
- A) Assume the UI configuration automatically becomes YAML at runtime.
- B) Copy only the artifact name into a new YAML file.
- C) Recreate stages, variables, environments/checks, triggers, identities, and tasks deliberately in YAML, then validate parallel behavior before cutover. ✓
- D) Delete the Classic release pipeline before designing its replacement.
Answer: C. Classic release migration is a controlled redesign/translation of behavior and controls, not merely an export operation.
Why not the others: Automatic conversion/copying one field loses critical configuration. Early deletion removes the comparison and rollback path.