AZ-400 Matching — 10 Questions

Question 1

Match each Azure DevOps security concept to its purpose.

Accepted Answer

Azure Active Directory: Used for identity and access management, including authentication to Azure DevOps.. Azure AD manages user identities; PATs authenticate scripts; Service Principals authenticate automated services; Security Groups manage user permissions. Common confusions include mixing the roles of Azure AD and Service Principals, or PATs with Security Groups.

Answer

Azure Active Directory: Used to authenticate automated pipelines to Azure resources.

Answer

Personal Access Token (PAT): Used to manage permissions for groups of users.

Question 2

Match each Azure Repos policy to its enforcement.

Accepted Answer

Require a minimum number of reviewers: At least two reviewers must approve the pull request before it can be completed.. The correct matches are A, B, C, D. Policy A requires at least two reviewers. Policy B requires linked work items. Policy C requires a successful build. Policy D limits merge types. Policies E and F are incorrect because they swap the descriptions: E describes merge types but is labeled as reviewer count, and F describes reviewer count but is labeled as work item linking.

Answer

Require a minimum number of reviewers: Specify which merge strategies are allowed, such as squash merge or rebase.

Answer

Check for linked work items: At least two reviewers must approve the pull request before it can be completed.

Question 3

Match each Azure DevOps extension type to its example.

Accepted Answer

Build task: NuGet Tool Installer. In this matching exercise, the correct pairs are: Build task → NuGet Tool Installer, Dashboard widget → Sprint Burndown, and Service hook → Notify Slack on build completion. The distractors incorrectly assign Sprint Burndown as a build task and NuGet Tool Installer as a dashboard widget, testing your ability to distinguish between extension types based on their purpose. Build tasks execute during pipeline runs, dashboard widgets display information on dashboards, and service hooks trigger external actions on events.

Answer

Build task: Sprint Burndown

Answer

Dashboard widget: NuGet Tool Installer

Question 4

Match each Azure Pipeline concept to its definition.

Accepted Answer

Pipeline: A collection of stages that defines the CI/CD process.. The correct matches are: A: Pipeline → 'A collection of stages that defines the CI/CD process' (correct); B: Stage → 'A logical boundary in the pipeline used to group jobs' (correct); C: Job → 'A unit of work that runs on an agent' (correct); D: Task → 'A single operation to perform in a job' (correct). E is incorrect because Pipeline is not a logical boundary; that definition belongs to Stage. F is incorrect because Stage is not a collection of stages; that definition belongs to Pipeline. The most common confusion is swapping the definitions of Pipeline and Stage.

Answer

Pipeline: A logical boundary in the pipeline used to group jobs.

Answer

Stage: A collection of stages that defines the CI/CD process.

Question 5

Match each Git branching strategy to its description.

Accepted Answer

Git Flow: Uses develop and master branches with release branches.. Git branching strategies vary in complexity. Git Flow uses long-lived branches (develop, release), GitHub Flow is simple with feature branches to main, GitLab Flow adds environment branches, and trunk-based development centers on frequent commits to main. Common confusions involve swapping descriptions between Git Flow and GitHub Flow.

Answer

Git Flow: Uses only main branch and feature branches.

Answer

GitHub Flow: Uses develop and release branches.

Question 6

Match each YAML pipeline trigger to its behavior.

Accepted Answer

CI trigger: Triggers a pipeline when a push occurs on the specified branch. In Azure Pipelines YAML, each trigger type has a distinct purpose: CI for push events, PR for pull requests, Schedules for cron-based runs, and Pipeline for cross-pipeline dependencies. Common confusions mix the behaviors of CI/PR or PR/Pipeline triggers.

Answer

CI trigger: Triggers a pipeline when a pull request is opened

Answer

PR trigger: Triggers a pipeline on completion of another pipeline

Question 7

Match each Azure Artifacts feed type to its description.

Accepted Answer

Project-scoped feed: A feed scoped to a specific project within an organization, accessible by members of that project.. In Azure Artifacts, project-scoped feeds are limited to a specific project, organization-scoped feeds are available to the entire org, and public feeds allow anonymous access. Common confusions arise from swapping the scope of project and org feeds, or misstating public feed authentication requirements.

Answer

Project-scoped feed: A feed scoped to the entire organization, accessible by all members.

Answer

Organization-scoped feed: A feed scoped to a specific project, accessible by project members.

Answer

Public feed: A feed that requires authentication from external users.

Question 8

Match each Azure DevOps service to its primary function.

Accepted Answer

Azure Boards: Agile project management and work tracking. The correct matches are: Azure Boards for agile planning, Azure Repos for version control, Azure Pipelines for CI/CD, and Azure Artifacts for package management. Common confusions include swapping Boards with Repos or Pipelines.

Answer

Azure Boards: Source code version control

Answer

Azure Pipelines: Agile project management

Question 9

Match each Azure Monitor feature to its use case.

Accepted Answer

Log Analytics: Collects and queries log data from Azure resources.. The correct matches are Log Analytics for log collection and querying, Application Insights for live web application monitoring, and Azure Monitor Metrics for numeric performance data. The distractors swap the definitions of Log Analytics and Application Insights.

Answer

Log Analytics: Monitors live web applications.

Answer

Application Insights: Collects and queries log data.

Question 10

Match each Azure Test Plans concept to its definition.

Accepted Answer

Test Plan: A container for test suites and test cases that specifies test settings and test configurations.. In Azure Test Plans, a Test Plan is a container for test suites and test cases with settings. A Test Suite groups test cases. A Test Case has steps and expected results. A Test Run is an execution of test cases. A Test Point is a test case with a specific configuration.

Answer

Test Suite: A set of steps and expected results to validate a feature.

Answer

Test Case: A collection of test cases grouped together for execution.