AZ-400 Configure processes and communications Practice Test 3 — 15 Questions

Question 1

Drag and drop the steps to set up a self-hosted Azure DevOps agent on a Windows VM into the correct order.

Accepted Answer

First create a PAT, then download the agent, then run config.cmd to configure and register, then start the agent as a service.. The correct order to set up a self-hosted Azure DevOps agent on a Windows VM is: create a Personal Access Token (PAT) first, then download the agent package, then run config.cmd to configure and register the agent with Azure DevOps, and finally start the agent as a service. Option A reflects this sequence correctly. Other options either place download before PAT creation or start the agent before configuration, which would fail.

Answer

First download the agent, then create a PAT, then run config.cmd, then start the agent as a service.

Answer

First create a PAT, then run config.cmd, then download the agent, then start the agent as a service.

Answer

First create a PAT, then download the agent, then start the agent as a service, then run config.cmd.

Question 2

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 3

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.

Question 4

Your team uses GitHub Issues to track work. You want to enforce that all new issues include a specific set of labels based on the issue type (bug, feature, task). What is the most efficient way to achieve this?

Accepted Answer

Create YAML-based issue forms in the .github/ISSUE_TEMPLATE folder.. GitHub issue forms, defined as YAML files in the .github/ISSUE_TEMPLATE folder, allow you to create structured templates that can enforce required fields, including mandatory label assignments. When a user submits an issue via a form, the labels specified in the template are automatically applied, ensuring consistency without manual intervention or additional automation.

Answer

Configure branch protection rules to require label assignments.

Answer

Use a CODEOWNERS file to auto-assign labels.

Answer

Set up a repository ruleset to restrict label modifications.

Question 5

Your team follows trunk-based development. The main branch should always be deployable. Which two practices must you implement? (Choose two.)

Accepted Answer

Use feature flags to manage incomplete work.. In trunk-based development, the main branch must always be deployable. Feature flags (B) allow incomplete or work-in-progress code to be merged into the main branch without affecting production behavior, because the new functionality is toggled off until ready. Keeping branches short-lived (C) (typically less than a day) minimizes merge conflicts and ensures that changes are integrated quickly, reducing the risk of long-lived divergence that could break the main branch.

Answer

Require manual approval for every pull request.

Answer

Create release branches for each deployment.

Answer

Use long-lived feature branches for each feature.

Question 6

You are designing a communication strategy for a large Azure DevOps migration. The team is distributed across multiple time zones. Which approach best supports asynchronous collaboration?

Accepted Answer

Maintain a wiki in Azure DevOps with status and decisions.. Maintaining a wiki in Azure DevOps provides a persistent, searchable, and asynchronous record of status and decisions, which is ideal for distributed teams across time zones. Option A is wrong because Slack huddles are real-time and require synchronous participation. Option C is wrong because email threads can be hard to search and lack integration with Azure DevOps. Option D is wrong because daily standup meetings at a fixed time require synchronous attendance. Option E is wrong because recording meetings is passive and not easily searchable; the information is not structured for quick reference.

Answer

Use Slack huddles for quick sync-ups.

Answer

Use email threads for status updates.

Answer

Schedule daily standup meetings at a fixed time.

Answer

Record all team meetings and share links.

Question 7

Your organization uses GitHub Copilot for pull request summaries. However, some developers report that the summaries are inaccurate. What should you do to improve the quality of Copilot-generated pull request summaries?

Accepted Answer

Ask developers to write clear, structured PR titles and descriptions.. GitHub Copilot for pull request summaries relies on the PR title and description as primary input to generate accurate summaries. Clear, structured titles and descriptions provide better context for the AI model, reducing ambiguity and improving summary quality. Detailed commit messages (Option A) are not directly used by Copilot for PR summaries, as it focuses on the PR-level metadata.

Answer

Encourage developers to write more detailed commit messages.

Answer

Disable Copilot for pull requests and use manual summaries.

Answer

Provide a link to a documentation wiki in the PR description.

Question 8

Your Azure DevOps pipeline uses a self-hosted agent pool. You notice that builds are queuing for a long time. What is the most effective way to reduce queue times without incurring additional costs?

Accepted Answer

Allocate more parallel jobs to the agent pool.. Allocating more parallel jobs to the self-hosted agent pool allows multiple pipelines or jobs to run concurrently, directly reducing queue times. This is achieved by adjusting the parallelism setting in the agent pool's properties, which does not incur additional costs as you are already paying for the self-hosted infrastructure.

Answer

Reduce the number of steps in the pipeline.

Answer

Increase the agent specification (e.g., from DS2 to DS4).

Answer

Switch to Microsoft-hosted agents to get more parallelism.

Question 9

Your team uses Azure Boards with a custom process. Which two features allow you to customize the work item types? (Choose two.)

Accepted Answer

Create an inherited process from the default process.. In Azure Boards, customization of work item types is only possible through an inherited process. You must create an inherited process from a default process (e.g., Agile, Scrum, CMMI) to enable any modifications. This ensures the default process remains unaltered and supports upgrade compatibility.

Answer

Configure rules to create new work item types.

Answer

Use team settings to define new work item types.

Answer

Modify the default process directly.

Question 10

Refer to the exhibit. You are migrating repository policies from Azure Repos to GitHub. The JSON shows a branch protection rule you plan to apply to the main branch. A developer pushes a hotfix directly to main without a pull request. What happens?

Accepted Answer

The push succeeds because no push restriction is defined.. The branch protection rule includes required status checks and lockBranch (set to false), but it does not require pull requests before merging. In GitHub, direct pushes to a branch are only blocked if 'Require a pull request before merging' is enabled. Since that is not present here, the developer can push directly to main without a pull request, and the push succeeds. Options A and B are incorrect because required status checks and enforceAdmins do not block direct pushes; they only affect pull request merges. Option D is incorrect because lockBranch set to false allows modifications.

Answer

The push is blocked because required status checks are not met.

Answer

The push is blocked because enforceAdmins is true.

Answer

The push is rejected because lockBranch is false.

Question 11

Your team uses GitHub Actions for CI/CD. You need to ensure that secrets used in workflows are automatically rotated every 90 days. What is the best approach?

Accepted Answer

Use a script that calls the GitHub API to update the secret and run it in a scheduled workflow.. It uses the GitHub API within a scheduled workflow to programmatically rotate secrets, ensuring automation without manual intervention. This approach directly addresses the requirement for automatic rotation every 90 days by generating new secret values and updating the repository or organization secrets via the API.

Answer

Use OpenID Connect (OIDC) to authenticate.

Answer

Manually update the secrets every 90 days.

Answer

Store secrets as environment secrets and configure expiration.

Question 12

Your team uses Azure DevOps with a Git repository. You want to enforce that all pull requests to main must have at least one reviewer from the 'security' group. Which two configurations are required? (Choose two.)

Accepted Answer

Add the security group as a required reviewer for the main branch policy.. You can add the security group as a required reviewer in the branch policy. Option D is correct because setting the minimum number of reviewers to 1 ensures at least one reviewer is required. Option A is incorrect because automatic reviewers are not the same as required reviewers; they only suggest reviewers but do not enforce mandatory review. Option C is incorrect because a repository policy applies to all branches, not just main, and does not enforce required reviewers for pull requests; a branch policy is needed. Option E is incorrect because a branch protection rule is a GitHub feature, not available in Azure Repos.

Answer

Configure automatic reviewers for the security group.

Answer

Create a repository policy for the main branch.

Answer

Configure a branch protection rule in GitHub.

Question 13

Your organization uses GitHub Enterprise and wants to enforce that all repositories have a specific issue template. What is the most scalable way to achieve this?

Accepted Answer

Create a global issue template in the organization settings.. GitHub Enterprise allows organization owners to create a global issue template by placing a `.github/ISSUE_TEMPLATE/` directory in the `.github` repository. This template is automatically applied to all repositories within the organization, ensuring consistency without manual intervention per repo. This is the most scalable approach as it centralizes enforcement at the organization level.

Answer

Use a script to periodically check and add templates.

Answer

Create a repository template and require all new repos to use it.

Answer

Configure a CODEOWNERS file in each repository.

Question 14

Your team uses Azure Test Plans. You need to ensure that testers can easily see which test cases are blocked by a known bug. What should you do?

Accepted Answer

Link test cases to the bug and create a query for linked items.. Azure Test Plans allows test cases to be linked directly to bugs via work item linking. By creating a query for linked items (e.g., a shared query that returns all test cases linked to a specific bug), testers can instantly see which test cases are blocked by that known bug. This provides a dynamic, filterable view without duplicating or reorganizing test artifacts.

Answer

Configure the test plan to show only failed tests.

Answer

Create a test suite for each bug.

Answer

Copy the test case and mark it as blocked.

Question 15

Your team uses GitHub Issues for work tracking. You want to automate the creation of a new issue when a build pipeline fails in Azure Pipelines. Which action should you implement in the YAML pipeline?

Accepted Answer

Use a PowerShell task to call the GitHub Issues API.. Azure Pipelines does not natively support creating GitHub Issues directly from a YAML pipeline. Instead, you must use a PowerShell task (or a script task) to call the GitHub Issues API (POST /repos/{owner}/{repo}/issues) with an authentication token to create the issue when the build fails. This approach gives you full control over the issue content and is the standard way to integrate with GitHub Issues from Azure Pipelines.

Answer

Add a GitHub Action that triggers on pipeline completion.

Answer

Configure a Service Hook in Azure DevOps to GitHub Issues.

Answer

Add a task to create a work item in Azure Boards.