AZ-400 Configure processes and communications Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Azure Boards: Agile project management and work tracking

  Why this is correct

  Azure Boards provides the work-tracking backbone for Agile teams, offering configurable backlogs, Kanban boards, and sprint planning views backed by work item types such as epics, features, user stories, and bugs. Its role is purely project management: it organizes work, tracks status, and supports sprint cadences, but it does not compile, test, or package code. Azure Boards also integrates with source control and CI/CD via repo commit and pull request links, but those integrations are external to its core function.

• ✓

  Azure Repos: Source code version control

  Why this is correct

  Azure Repos is the source control service within Azure DevOps, hosting Git repositories and Team Foundation Version Control (TFVC) for teams that require centralized versioning. It gives developers branch policies, pull request workflows, and build validation triggers, ensuring code changes are reviewed and verified before merging. Because it stores source code and protects the history, it is the correct answer for 'source code version control'—an activity that is entirely separate from work tracking or build execution.

• ✓

  Azure Pipelines: Continuous integration and delivery (CI/CD)

  Why this is correct

  Azure Pipelines is the CI/CD engine of Azure DevOps, enabling automated builds, test execution, and multi-stage deployments to targets such as Azure, on-premises environments, or any cloud. It supports both YAML-based pipeline definitions and classic editor pipelines, with agents running jobs in parallel and publishing artifacts, and it can be triggered by commits, pull requests, or schedules. This service automates the delivery loop, which is fundamentally different from managing sprint backlogs or storing source code.

• ✓

  Azure Artifacts: Package management for dependencies

  Why this is correct

  Azure Artifacts serves as the package management hub for Azure DevOps, allowing teams to create, host, and share software packages including NuGet, npm, Maven, Python, and Universal Packages. It provides private feeds with upstream sources so teams can mix internally built packages with public registries while maintaining controlled dependency versions. This function is essential for dependency governance and secure artifact propagation, and it does not overlap with work tracking, version control, or CI/CD execution.

• ✗

  Azure Boards: Source code version control

  Why it's wrong here

  This pairing is incorrect because Azure Boards has no facility for storing or versioning source code; its features are limited to work items, backlogs, boards, and sprint tracking. The Azure service that actually provides source code version control is Azure Repos, which hosts Git or TFVC repositories with branching, merging, and pull request review support. Equating Boards with version control is a common mix-up because Boards can link work items to commits and PRs, but those links merely reference repositories, not replace them.

• ✗

  Azure Pipelines: Agile project management

  Why it's wrong here

  This pairing is incorrect because Azure Pipelines is not a project management tool; it is a service for automating build, test, and release processes. Agile project management—including backlog creation, sprint planning, and work item tracking—is the exclusive domain of Azure Boards. While pipeline runs can update work item statuses or link to user stories, Azure Pipelines itself does not manage team capacity, prioritize work, or provide Kanban boards, so pairing it with 'Agile project management' is factually wrong.

Go deeper

Related to this question