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

Question 1

Your team uses Azure Boards to track work items. They want to automatically update the state of a work item when a pull request is merged in Azure Repos. What should you configure?

Accepted Answer

Define a branch policy to link work items and set automatic state transition.. Option B is correct because Azure Repos branch policies allow you to require linked work items for pull requests and automatically transition the state of a linked work item (e.g., from 'Active' to 'Resolved') upon merge. This is configured in the branch policy settings under 'Automatically update work items' with a state transition rule, directly integrating Azure Boards with pull request completion.

Answer

Configure a work item template.

Answer

Create a service hook subscription.

Answer

Set pipeline variables in the YAML file.

Question 2

A development team wants to ensure that all code changes are reviewed by at least two senior developers before merging into the main branch. They use Azure Repos. What should they configure?

Accepted Answer

Configure a branch policy requiring a minimum number of reviewers.. Option C is correct because Azure Repos branch policies allow you to enforce a minimum number of reviewers on pull requests. By setting the 'Minimum number of reviewers' policy to 2, the team ensures that at least two senior developers must approve any code change before it can be merged into the main branch. This directly meets the requirement without involving build validation, release pipelines, or external function calls.

Answer

Enable the build validation policy on the branch.

Answer

Set up a release pipeline with gated deployments.

Answer

Add a status check policy using Azure Functions.

Question 3

Your team uses Azure DevOps and wants to implement a change management process where all production releases must be approved by a change advisory board (CAB) after the build is complete but before deployment. The approval must be recorded in the pipeline. What is the best approach?

Accepted Answer

Create a release pipeline with a pre-deployment approval gate for the production stage.. Option D is correct because a release pipeline with a pre-deployment approval gate for the production stage enforces that a designated approver (or group, such as the CAB) must approve the release before deployment begins. The approval is recorded in the pipeline's audit trail, satisfying the requirement for documented change management. This approach aligns with Azure DevOps release management best practices for gating production deployments.

Answer

Configure a branch policy requiring CAB member approval on pull requests.

Answer

Add a manual intervention task in the YAML pipeline.

Answer

Set up a service hook to send an email to the CAB and wait for a reply.

Question 4

Drag and drop the steps to configure a static route on a Cisco IOS router into the correct order.

Question 5

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

Question 6

Match each Azure DevOps service to its primary function.

Question 7

Match each Azure Test Plans concept to its definition.

Question 8

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.. Option C is correct because 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 9

Your Azure DevOps environment uses Microsoft Entra ID for authentication. You need to ensure that users from a partner organization can access only a specific Azure Boards project without being added to your tenant as guests. What should you do?

Accepted Answer

Invite the partner users as Microsoft Entra B2B guests and assign them to the project.. Option B is correct because Microsoft Entra B2B collaboration allows you to invite external users as guests, granting them access to specific resources like an Azure Boards project without fully adding them to your tenant. This meets the requirement of restricting access to only that project while avoiding permanent guest accounts in your directory.

Answer

Issue OAuth 2.0 tokens to the partner users.

Answer

Configure Microsoft Entra ID identity protection to allow the partner IP range.

Answer

Create service principals for the partner users.

Question 10

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 11

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.. Option C is correct because Azure DevOps Wiki provides a persistent, searchable record of decisions and status. Option A is wrong because daily standups require synchronous attendance. Option B is wrong because email threads are hard to search and not integrated. Option D is wrong because Slack huddles are real-time. Option E is wrong because meeting recordings are passive and not searchable.

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 12

Refer to the exhibit. The JSON above shows a branch policy configuration for the main branch in Azure Repos. A developer pushes a third commit to an existing pull request after two reviewers have already approved. What happens?

Accepted Answer

The approvals are dismissed because require_last_push_approval is true.. Option B is correct because require_last_push_approval is true, so after the new push, previous approvals are dismissed, requiring re-approval. Option A is wrong because require_last_push_approval overrides dismiss_stale_reviews. Option C is wrong because allowed merge types are squash and rebase, but that doesn't affect approval. Option D is wrong because the pull request can still be updated.

Answer

The existing approvals remain valid because dismiss_stale_reviews is false.

Answer

The pull request is automatically merged because allowed merge types include squash.

Answer

The pull request is blocked because the merge type is not allowed.

Question 13

Your team uses Azure Repos and wants to enforce that every commit message includes a work item ID. Which policy should you configure?

Accepted Answer

Branch policy to require linked work items.. Option C is correct because Azure Repos branch policies include a 'Require linked work items' setting that enforces every commit in a pull request to be associated with a work item. This ensures commit messages reference a work item ID, as the policy blocks pull requests without linked work items, directly meeting the requirement.

Answer

Repository settings to restrict file paths.

Answer

Branch policy to require a minimum comment length.

Answer

Pre-push Git hook.

Question 14

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.. Option B is correct because 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 15

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.. Option C is correct because parallel jobs allow multiple builds to run concurrently, reducing queue time. Option A is wrong because changing the agent specification does not increase concurrency. Option B is wrong because Microsoft-hosted agents incur additional cost. Option D is wrong because reducing pipeline steps may not be feasible and doesn't address concurrency.

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.