A small team's release manager, who does not work in source control, needs to set up a simple deployment. The team has no requirement to version that pipeline definition alongside the code. Which authoring approach is appropriate?
Show answer and explanation
Answer: B
Classic pipelines are defined through a visual designer and are stored in the Azure DevOps service rather than in a repository. That suits a team that prefers visual authoring and does not need the definition versioned with the code. Microsoft recommends YAML for most new work because it is version controlled, reviewable and templatable. Classic definitions can build as well as release, and variables and secret variables work in both models.
Why the other options are wrong
- A. Classic is not the default for new projects. Microsoft recommends YAML for most new work because it can be version controlled and reviewed alongside the code.
- C. Classic pipelines can build as well as release, so limiting them to builds misstates what they support. The choice concerns authoring style and where definitions are stored.
- D. Variables and secret variables work in both YAML and classic pipelines, so a classic pipeline is not needed just to hold them.