An organisation is migrating classic editor build and release definitions to YAML pipelines in "Azure DevOps". Several classic definitions rely on task groups to share a sequence of tasks across definitions, and the team must decide how that reuse translates into YAML. Which two statements correctly describe task groups and their YAML equivalent? Select TWO.
- AA variable group is the YAML equivalent of a task group, because both bundle a named, reusable unit that pipelines reference, so the task sequence is preserved by moving it into a variable group.
- BA task group can be imported unchanged into a YAML pipeline by referencing its identifier in a resources block, so no rewrite of the shared tasks is needed during migration.
- CTask groups are a feature of the classic editor only and are not available in YAML pipelines, so a YAML pipeline cannot reference a task group to reuse a sequence of tasks. Correct
- DA step template referenced with the template keyword is the YAML mechanism that replaces a task group, letting the shared sequence of steps be defined once and included by every pipeline that needs it. Correct
Why A is wrong: This is tempting because both are shared, named library items, but a variable group only stores values, not tasks, so it cannot carry a sequence of build steps the way a task group did.
Why B is wrong: There is no resources construct that imports a classic task group into YAML; the shared tasks must be re-expressed as a YAML template, so claiming a no-rewrite import is incorrect.
Why C is correct: Task groups exist solely in the classic designer model and have no representation in YAML, so a YAML pipeline cannot consume a task group and the team must use a different reuse mechanism.
Why D is correct: A YAML step template captures a reusable sequence of steps that pipelines include with the template keyword, which is the direct equivalent of the reuse a classic task group provided.