AZ-400 Question 215
Select 2Your organization currently uses a classic pipeline to build and deploy a containerized Node.js application in Azure DevOps. They want to move the pipeline definition into source control and leverage YAML for versioning and enhanced flexibility. Which two steps should you include in your plan to successfully migrate from the classic pipeline to a YAML-based pipeline?
- A
Export each classic pipeline task to YAML, then manually consolidate them into a single YAML file and commit it to the repository.
- B
Use the 'Apply YAML Conversion Wizard' to automatically convert all classic pipeline tasks at once with no further manual adjustments.
- C
Create a new pipeline in Azure DevOps by selecting the YAML file from the repository and configure triggers within the YAML file.
- D
Retain the legacy classic pipeline for building the Docker image and reference it from within the new YAML pipeline.
Show answer and explanation
Correct answers: A, C
Explanation
To migrate from a classic pipeline to YAML in Azure DevOps, you typically export or re-create tasks in YAML format, commit the YAML file into your repository, and then set up a new pipeline that references this file. While Azure DevOps lets you view partial YAML for certain tasks, you usually need to consolidate them manually into one file. Full details and best practices are outlined in the official documentation at https://learn.microsoft.com/azure/devops/pipelines/migrate/from-classic-pipelines-to-yaml.
- A. Correct.
Correct. Azure DevOps does not offer a one-click export of the entire classic pipeline, but you can view YAML snippets for each task. You then manually assemble those snippets into a single YAML file. This is a common practice for migrating tasks to a new YAML pipeline.
- B. Incorrect.
Incorrect. There is no automatic 'Apply YAML Conversion Wizard' that converts the entire pipeline into a perfect YAML equivalent without further manual work. Azure DevOps provides a 'View YAML' feature for certain tasks, but it does not automatically rebuild the entire pipeline as a single YAML file.
- C. Correct.
Correct. After creating and committing the YAML definition to your repository, you can create a new pipeline in Azure DevOps by selecting that YAML file. This approach ensures that your pipeline is fully defined in code and allows you to configure triggers directly in the YAML file.
- D. Incorrect.
Incorrect. Once you move to a YAML pipeline, the recommended approach is to migrate relevant tasks and decommission the classic pipeline. Retaining the classic pipeline for build steps and referencing it in the new YAML pipeline is generally not recommended, as it undermines the benefits of a fully YAML-based approach.