Terrible question! If its azure classic pipelines then its a task group, if its a YAML based pipeline then its YAML pipelines. Not sure which one to go for really
A is the answer.
https://learn.microsoft.com/en-us/azure/devops/pipelines/library/task-groups?view=azure-devops
A task group allows you to encapsulate a sequence of tasks, already defined in a build or a release pipeline, into a single reusable task that can be added to a build or release pipeline, just like any other task. You can choose to extract the parameters from the encapsulated tasks as configuration variables, and abstract the rest of the task information.
The new task group is automatically added to the task catalog, ready to be added to other release and build pipelines. Task groups are stored at the project level, and are not accessible outside the project scope.
Task groups are a way to standardize and centrally manage deployment steps for all your applications. When you include a task group in your definitions, and then make a change centrally to the task group, the change is automatically reflected in all the definitions that use the task group. There is no need to change each one individually.
A YAML template is the best approach. YAML templates allow you to define reusable pipeline logic, including specific tasks, and reference them across multiple pipelines
Ans is C: YAML template
Why not the other options?
A. Task Group: Task groups are useful for grouping tasks within the Classic UI pipelines but are not as flexible or reusable as YAML templates in the context of YAML pipelines.
B. JSON Template: Azure DevOps pipelines are defined using YAML, not JSON, so JSON templates are not applicable here.
D. PowerShell Task: A PowerShell task can perform a series of actions, but it is not a reusable template for defining a sequence of pipeline tasks. It's better suited for specific scripted actions within a pipeline.
Therefore, creating a YAML template is the most effective solution to ensure that all new pipelines in Project1 execute the specified tasks.
A task group in Azure DevOps is a collection of tasks that can be reused across multiple pipelines. You can create a task group that contains the three specific tasks that you need to execute during pipeline execution, and then reference that task group in all new pipelines in Project1. This way, you can ensure that the three specific tasks are executed in all new pipelines without having to manually add them to each pipeline.
Answer: A. a task group
To ensure that all new pipelines in Project1 execute three specific tasks during pipeline execution, you can create a task group.
A task group is a collection of tasks that you define as a single entity. You can reuse the task group in multiple pipelines to save time and effort in defining and updating the same set of tasks repeatedly. When you update a task group, all pipelines that reference it are automatically updated with the latest changes.
Therefore, by creating a task group with the three specific tasks, you can ensure that any new pipeline that references the task group will execute those tasks during pipeline execution.
upvoted 3 times
...
This section is not available anymore. Please use the main Exam Page.AZ-400 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
mrg998
Highly Voted 2 years, 3 months agoxRiot007
1 year, 9 months agozellck
Highly Voted 1 year, 11 months agoswk2az400
Most Recent 5 months, 2 weeks agoGooldmember
6 months agoMattt
7 months agokarthikwarrior
11 months agovsvaid
1 year, 4 months agoFirdous586
1 year, 6 months agoMadbo
2 years ago