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

Question 1

You are designing a communication strategy for your DevOps team. They use Microsoft Teams for collaboration. You need to automatically notify the team when a release to production fails. Which Azure DevOps integration should you use?

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

Configure a notification subscription in Azure DevOps to send a Teams webhook. Azure DevOps notification subscriptions can be configured to send alerts to a Teams channel via an incoming webhook. This allows automatic, real-time notifications to the DevOps team when a release to production fails, directly within their collaboration platform.

Answer

Set up an email subscription to the DevOps team

Answer

Create a service hook to call a custom API

Answer

Publish a Wiki page with deployment status

Question 2

Your organization uses GitHub for code and GitHub Actions for CI/CD. You want to enforce that all workflows include a 'codeql-analysis' job for security scanning. What is the best approach?

Accepted Answer

Use GitHub's required workflows feature to mandate specific workflows. GitHub's required workflows feature allows organization owners to enforce that specific workflows (like a CodeQL analysis) run on all repositories in the organization, ensuring consistent security scanning without relying on templates or manual setup. This is the only approach that centrally mandates the workflow's presence and execution across all repositories, even if developers create new workflows or modify existing ones.

Answer

Create a workflow template and add it to the organization's workflow templates directory

Answer

Use branch protection rules to require a status check named 'codeql-analysis'

Answer

Create a custom GitHub Action that runs CodeQL and require it in all workflows

Question 3

Your team uses Azure Boards with a Kanban board. You want to limit the number of work items in the 'In Progress' column to prevent bottlenecks. What should you configure?

Accepted Answer

Column limits on the Kanban board. Column limits on the Kanban board directly enforce work-in-progress (WIP) constraints by capping the number of work items allowed in a specific column, such as 'In Progress'. This prevents bottlenecks by signaling the team to complete existing work before pulling new items, aligning with Lean and Kanban principles. Azure Boards supports this configuration through the board settings, where you can set a maximum limit per column.

Answer

Branch policies

Answer

Backlog level settings

Answer

Work item rules

Question 4

Which TWO actions should you take to ensure that your Azure DevOps pipeline securely manages secrets?

Accepted Answer

Use Azure Key Vault variable groups. Azure Key Vault variable groups securely store and manage secrets outside the pipeline definition, with access control and auditing. Option D is correct because secret variables set in the pipeline UI or variable groups are masked in logs and not exposed in the YAML file. Option B is incorrect: enabling script access to the system token and printing secrets in logs is a security risk. Option C is incorrect: storing secrets directly in the YAML pipeline file exposes them in the repository. Option E is incorrect: storing secrets as plain text in the repository is insecure.

Answer

Enable 'Allow scripts to access the system token' and print secrets in logs for debugging

Answer

Store secrets directly in the YAML pipeline file

Answer

Store secrets as plain text in the repository

Question 5

Which THREE practices are recommended for managing technical debt in a DevOps environment?

Accepted Answer

Allocate time for refactoring in each iteration. Options A, C, and D are correct because managing technical debt in a DevOps environment requires proactive and automated quality practices. Allocating time for refactoring each iteration (A) prevents debt accumulation. Automating unit and integration tests (C) ensures early detection of regressions and quality issues. Integrating static code analysis into the CI pipeline (D) provides continuous feedback on code quality and debt indicators. Option B is incorrect because deferring unit tests increases technical debt by delaying detection. Option E is incorrect because ignoring low-priority code smells allows debt to grow, which should be tracked and addressed systematically.

Answer

Defer unit tests until after deployment

Answer

Ignore low-priority code smells

Question 6

Which TWO approaches can you use to enforce consistent commit message conventions across your GitHub repositories?

Accepted Answer

Use a GitHub Action to validate commit messages on push. GitHub Actions can be configured with a workflow that triggers on `push` events to validate commit messages against a regex pattern, rejecting non-conforming commits. Option D is correct because repository rulesets (or branch protection rules) allow you to define required commit message patterns that must match before a push is accepted, enforced server-side. Both approaches enforce conventions consistently across all contributors.

Answer

Add a .gitattributes file

Answer

Set the default branch to main

Answer

Set up an issue template

Question 7

Refer to the exhibit. You have this YAML pipeline in an Azure Repos repository. What is the expected behavior when a pull request is created from a feature branch to the main branch?

Accepted Answer

The pipeline does not run automatically on the PR; it must be triggered manually or via branch policy.. The YAML pipeline shown does not include a `pr` trigger, and the `trigger` block only applies to CI (continuous integration) builds on branch pushes, not pull requests. Without a `pr` trigger, Azure Pipelines does not automatically run on pull request creation; it must be triggered manually or via a branch policy configured in the repository settings.

Answer

The pipeline runs twice: once on PR creation and once on merge.

Answer

The pipeline runs automatically on the PR to main, triggered by the pr trigger.

Answer

The pipeline runs when the PR is merged to main, triggered by the trigger block.

Question 8

Your team uses GitHub Flow for feature development. A developer commits directly to the main branch without creating a pull request. Which practice should you enforce to ensure code quality and prevent direct commits?

Accepted Answer

Configure branch protection rules on the main branch to require pull request reviews before merging.. Branch protection rules prevent direct commits to the main branch and require pull requests with reviews. Option A is incorrect because manual sign-off is not enforceable. Option C is incorrect because a .gitignore file does not block commits or enforce branch policies. Option D is incorrect because a CODEOWNERS file alone does not block direct commits.

Answer

Require a manual sign-off from a team lead after each commit.

Answer

Set up a .gitignore file to prevent certain file types from being committed.

Answer

Add a CODEOWNERS file that automatically assigns reviewers to any changes.

Question 9

Your team uses Azure Boards to manage work items. They want to automatically update the status of a work item to 'Resolved' when a pull request that contains the work item ID is merged. Which feature should you configure?

Accepted Answer

Enable the 'Automatically update work item status' setting in the repository's pull request configuration.. Azure Repos provides a setting in the repository's pull request configuration to automatically update linked work items to a specified state (e.g., 'Resolved') when a pull request is merged. This setting automatically updates work items that are linked via the work item ID in the pull request description. Option B is incorrect because it requires manual effort, which is not automatic. Option C is incorrect because branch policies for linked work items only enforce linking, not automatic status updates. Option D is incorrect because although service hooks can be used to call REST APIs, Azure DevOps already provides a built-in mechanism for this scenario, making it unnecessary to create custom hooks.

Answer

Instruct developers to manually update the work item after merging.

Answer

Set up a branch policy that requires linked work items.

Answer

Create a service hook to call Azure DevOps REST API on pull request merge.

Question 10

Your team wants to implement a policy that requires all pull requests to have at least one approval from a member of the 'Senior Developers' group before merging. Which mechanism should you use?

Accepted Answer

Create a branch policy on the target branch that requires a minimum number of reviewers from the 'Senior Developers' group.. Azure Repos branch policies allow you to enforce required reviewers on pull requests. By creating a branch policy on the target branch that requires a minimum number of reviewers from the 'Senior Developers' group, you ensure that no pull request can be completed without at least one approval from that group. This directly meets the requirement without relying on file-level ownership or external scripts.

Answer

Add a CODEOWNERS file that designates 'Senior Developers' as owners of all files.

Answer

Configure the pull request dashboard to display required reviewers.

Answer

Set up a build validation policy that runs a script to check approvals.

Question 11

Your company uses Microsoft Teams for collaboration. You want to send notifications to a Teams channel whenever a build pipeline in Azure Pipelines fails. Which approach should you use?

Accepted Answer

Install the Azure Pipelines app for Microsoft Teams and subscribe the channel to pipeline notifications.. The Azure Pipelines app for Microsoft Teams provides built-in integration to subscribe to pipeline events and send notifications to channels. Option A is incorrect because email subscriptions are separate. Option B is incorrect because webhooks require custom configuration. Option D is incorrect because the Teams connector is deprecated in favor of the app.

Answer

Configure an email subscription in Azure DevOps to send alerts to the Teams channel email address.

Answer

Set up a webhook in Azure DevOps to post to the Teams channel's incoming webhook URL.

Answer

Use the 'Post to a Microsoft Teams channel' task in the pipeline.

Question 12

Your team uses trunk-based development with short-lived feature branches. You notice that code reviews often delay merging because reviewers are not available. What is the best way to reduce review latency while maintaining quality?

Accepted Answer

Encourage pair programming or mob programming to review code in real-time.. Pair programming or mob programming allows code to be reviewed in real-time during development, reducing the need for asynchronous pull request reviews and thus decreasing review latency while maintaining quality. Option A is incorrect because enabling auto-merge does not address reviewer availability; it still requires a review to be completed. Option B is incorrect because requiring only one reviewer may reduce review depth and quality. Option C is incorrect because creating a separate review team can introduce new bottlenecks and does not solve the issue of reviewer unavailability.

Answer

Enable auto-merge for pull requests that have passed all checks.

Answer

Require only one reviewer instead of two.

Answer

Create a separate review team that only handles pull requests.

Question 13

Your organization wants to enforce that all commits to the main branch are signed using GPG or S/MIME. Which GitHub feature should you enable?

Accepted Answer

Configure a branch protection rule that requires signed commits.. GitHub branch protection rules include a 'Require signed commits' setting that enforces all commits pushed to the protected branch must be signed with a verified GPG or S/MIME key. This ensures commit integrity and non-repudiation directly at the repository level, without requiring external scripts or API calls.

Answer

Use the GitHub API to check commit signatures after push.

Answer

Enable the 'Include administrators' setting in branch protection.

Answer

Require SSH key authentication for all users.

Question 14

Your team uses Azure Pipelines to deploy a web app. They want to automatically roll back the deployment if the post-deployment smoke tests fail. What is the recommended approach?

Accepted Answer

Use a deployment gate with a monitoring tool that automatically initiates a rollback if health check fails.. Azure Pipelines supports deployment gates that can integrate with monitoring tools (e.g., Azure Monitor, Application Insights) to evaluate health metrics after deployment. If the gate detects a failure (e.g., a smoke test health check fails), it can automatically trigger a rollback to the previous stable version, ensuring zero manual intervention and faster recovery.

Answer

Define an approval gate that requires manual sign-off after deployment.

Answer

Set up a manual intervention step in the pipeline to decide rollback.

Answer

Configure a release variable that toggles between deployment slots.

Question 15

Your team uses GitHub Issues for tracking bugs and features. They want to automatically assign issues to the person who created the pull request that closes the issue. Which GitHub Actions workflow trigger and action should you use?

Accepted Answer

Use the 'issues' event with 'closed' type and an action that assigns the issue to the PR author.. The 'issues' event with 'closed' type triggers a workflow when an issue is closed, and the 'actions/github-script' action can be used to assign the issue to the pull request author by querying the pull request that closed the issue. Option A is incorrect because the 'pull_request' event does not directly close issues; closing an issue is done via a commit or pull request merge. Option C is incorrect because the 'push' event is not related to issue closure. Option D is incorrect because the 'schedule' event is time-based and does not respond to issue closures.

Answer

Use the 'pull_request' event and the 'actions/assign' action to assign the issue.

Answer

Use the 'push' event and call the GitHub API to assign the issue.

Answer

Use the 'schedule' event to periodically check for closed issues and assign them.