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

Question 1

Your team uses GitHub and wants to implement a policy that requires all pull requests to have a successful status check from a GitHub Actions workflow that runs unit tests. Additionally, the policy should require that the PR author is not allowed to merge their own PR. The repository is for a critical application and the main branch is protected. You need to configure the branch protection rules. Which combination of settings should you use?

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

Accepted Answer

Enable 'Require pull request reviews before merging' with 1 approval, and enable 'Require status checks to pass before merging' with the unit test check required.. It combines two essential protections: requiring at least one approval prevents the PR author from merging their own PR (since the author cannot self-approve), and requiring the unit test status check to pass ensures that only code with successful automated tests can be merged into the protected main branch. This directly satisfies both policy requirements.

Answer

Enable 'Require pull request reviews before merging' with 2 approvals, and enable 'Allow force pushes'.

Answer

Enable 'Require pull request reviews before merging' with 1 approval from a specific team, and disable 'Require status checks'.

Answer

Enable 'Require code owner review' and 'Require status checks to pass before merging'.

Question 2

You are designing a process to manage work item tracking in Azure Boards. Your team uses a custom process based on the Agile template. You need to ensure that when a bug is resolved, the associated user story is automatically moved to the 'Done' state. Which TWO approaches can you use to achieve this?

Accepted Answer

Set up an 'Automate' level rule on the user story to move to 'Done' when all child bugs are resolved.. Option A is correct because Azure Boards process rules support an 'Automate' action level that can trigger state transitions on a work item based on conditions involving its child links, so a rule on the user story can move it to 'Done' when all child bugs reach a resolved state. Option C is correct because you can configure a work item type rule (via the process customization rules engine) that fires when a linked bug is resolved and automatically transitions the parent user story to 'Done', which is exactly the required behavior. Option B is incorrect because 'View' rules only control field visibility and read-only behavior, not state transitions. Option D is technically possible with Power Automate but is not one of the two intended in-process Azure Boards approaches, and it requires external automation rather than native process rules. Option E is incorrect because service hooks are outbound event notifications for integrations (e.g., to a webhook), not a mechanism for updating work item state within Azure Boards.

Answer

Modify the 'View' rule on the user story to automatically transition when child bugs are resolved.

Answer

Create a Power Automate flow triggered when a bug state changes to 'Resolved', then update the parent user story.

Answer

Use service hooks to call a custom webhook that updates the user story.

Question 3

You are an Azure DevOps administrator for a project that uses an Agile process. The product owner wants to ensure that every new feature work item automatically includes a predefined set of acceptance criteria and is assigned to the correct area path based on the team. You need to configure the project to meet these requirements with minimal manual effort. (Choose two.)

Accepted Answer

Configure a rule on the Feature work item type that sets the Area Path based on the team's default area.. To automatically include predefined acceptance criteria and assign the correct area path, you should use custom rules. Rules can set field values on creation, ensuring that every new Feature work item gets the checklist and the correct area path based on team defaults. Work item templates and custom fields do not provide this level of automation.

Answer

Create a work item template that includes the acceptance criteria and area path, and make it available to the team.

Answer

Add a custom field to the Feature work item type and set a default value for acceptance criteria.

Answer

Use a work item template that includes the acceptance criteria and set it as the default for the team.

Question 4

Your team uses Azure Boards with a custom Inherited process. You need to ensure that when a Bug work item is moved to the 'Resolved' state, the 'Resolved By' field is automatically populated with the user who made the change, and the 'Resolved Date' field is set to the current date. Which configuration should you implement?

Accepted Answer

Configure a rule that copies the value from the 'Changed By' field to 'Resolved By' and from the 'Changed Date' field to 'Resolved Date' when the state changes to Resolved.. The correct approach is to use a custom rule that copies the system fields 'Changed By' and 'Changed Date' to the custom fields when the state changes to Resolved. This leverages built-in system fields that are automatically updated, ensuring the fields are populated with the correct user and date without manual intervention.

Answer

Create a custom rule that sets the 'Resolved By' field to the current user and the 'Resolved Date' field to the current date when the state changes to Resolved.

Answer

Modify the Bug work item type to add a custom control that automatically captures the user and date upon state change.

Answer

Use a work item template that pre-fills the 'Resolved By' and 'Resolved Date' fields, and instruct users to apply it when resolving bugs.

Question 5

You are setting up a new Azure DevOps project for a team that follows Scrum. The team wants to ensure that all work items of type 'Task' are automatically assigned to the person who creates them and have a default priority of 2. Which configuration should you use?

Accepted Answer

Use a custom rule that copies the value from the 'Created By' field to 'Assigned To' and sets 'Priority' to 2 when a Task is created.. The correct solution is to use a custom rule that copies the 'Created By' field to 'Assigned To' and sets 'Priority' to 2 upon creation. This leverages the system field 'Created By' which is automatically populated, ensuring the task is assigned to the creator, and sets the default priority as required.

Answer

Create a work item template that sets the assignee to the current user and priority to 2, and instruct the team to use it when creating tasks.

Answer

Configure a custom rule on the Task work item type that sets the Assigned To field to the current user and Priority to 2 when a Task is created.

Answer

Modify the process to set the default value of the Assigned To field to the current user and the Priority field to 2.

Question 6

Your team uses Azure Boards to track work. You need to ensure that when a work item is assigned to a team member, that member receives an email notification. Which Azure DevOps feature should you configure?

Accepted Answer

Notification settings under Project Settings > Notifications.. Notification settings in Azure DevOps allow users to subscribe to events like work item assignment. By default, users may receive notifications for assignments if they are the assignee, but administrators can enforce or customize these rules. Service hooks are for external integrations, team configuration is for organization, and CLI is for automation, not native email notifications.

Answer

Team configuration under Project Settings > Teams.

Answer

Azure DevOps CLI with az boards work-item update command.

Answer

Service hooks under Project Settings > Service hooks.

Question 7

You are configuring Azure Pipelines for a project that uses multiple teams. Each team has its own set of work items and code repositories. You need to ensure that when a build pipeline fails, a bug work item is automatically created and assigned to the team that owns the code. The assignment should be based on the area path of the build. What should you do?

Accepted Answer

Configure a build completion trigger that creates a work item using the 'Create work item on failure' option in the pipeline's options.. The 'Create work item on failure' option in Azure Pipelines is designed to automatically create a bug work item when a build fails. It allows configuration of the work item type, area path, and assignee, and can use the build's area path to route to the correct team. Other methods require custom code or misapply features, making them less efficient and more error-prone.

Answer

Use a multi-stage pipeline with a stage that runs a script to create a bug work item via the Azure DevOps REST API.

Answer

Create a service hook that triggers on build failure and uses a custom Azure Function to create a bug with the area path set to the build's area.

Answer

Set up a branch policy that requires a work item link on every commit, which will automatically create a bug on failure.

Question 8

Your organization uses Azure DevOps and wants to enforce a consistent naming convention for work item titles across all teams. You need to ensure that all new work items of type 'User Story' have a title that starts with '[Feature]'. What should you implement?

Accepted Answer

Implement a custom rule using the Azure DevOps REST API and a service hook to validate and correct titles.. Azure DevOps does not have built-in pattern validation for work item titles. To enforce a naming convention, you must use a service hook to trigger on work item creation and a custom script to validate and correct the title via the REST API. Queries, required field rules, and templates do not enforce compliance. This custom approach ensures all new User Stories adhere to the convention.

Answer

Use a work item template that prepopulates the title with '[Feature]'.

Answer

Create a work item query that lists User Stories with incorrect titles.

Answer

Configure a required field rule in the process customization to validate the title field.

Question 9

A team uses Azure Boards and wants to ensure that work items moved to the 'Done' state require a completed code review. What should they configure?

Accepted Answer

Add a work item rule in the process template to require a code review for the 'Done' transition.. Azure Boards allows you to define work item rules within the process template that enforce specific conditions on state transitions. By adding a rule to the 'Done' transition that requires a completed code review (e.g., via a custom field or check), you ensure work items cannot be moved to 'Done' without meeting that prerequisite. This is done through the inherited process customization in Azure DevOps, where you can add rules to the work item type's state transition.

Answer

Modify the work item type definition to add a custom field for code review status.

Answer

Use a tag to mark work items as code-reviewed before moving to 'Done'.

Answer

Configure branch policies in Azure Repos to require pull request approvals.

Question 10

During a sprint review, stakeholders complain that they don't receive notifications about completed work items. The team uses Azure Boards with a custom notification subscription. What is the most likely cause?

Accepted Answer

The subscription's 'Deliver to' filter excludes stakeholders.. The most likely cause is that the custom notification subscription's 'Deliver to' filter is configured to exclude stakeholders. In Azure Boards, notification subscriptions can have filters that restrict delivery to specific groups or roles, and if stakeholders are not included in the filter, they will not receive notifications even if the subscription is active. This directly addresses the complaint that stakeholders are not getting notified about completed work items.

Answer

Email notifications are disabled at the organization level.

Answer

The subscription is set to deliver only to the team members.

Answer

The subscription was automatically disabled after the first notification.

Question 11

A multinational company uses Azure DevOps with a single project. The project has multiple teams in different time zones. They want to customize the process to reflect different working days for each team. What is the recommended approach?

Accepted Answer

Use the same process and configure working days in the team settings for each team.. Azure DevOps allows each team to have its own working days configured in team settings, independent of the process template. This enables teams in different time zones to define their own non-working days without modifying the shared process, which would affect all teams using that process.

Answer

Create a custom process for each time zone and assign teams accordingly.

Answer

Use the same process but create separate areas for each team, then configure working days per area path.

Answer

Use the same process and configure capacity planning for each team to account for time off.

Question 12

An organization uses Azure DevOps and wants to implement a change management process where all changes to the main branch require approval from a change advisory board (CAB). The CAB members are not part of the development team. How should they configure this?

Accepted Answer

Create a new branch policy on main that requires a minimum number of reviewers from a separate CAB group.. Azure DevOps branch policies allow you to enforce a minimum number of reviewers from a specific security group (e.g., a CAB group) on pull requests targeting the main branch. This ensures that every change to main requires explicit approval from CAB members, who are separate from the development team, without relying on manual processes or altering team membership.

Answer

Set branch permissions to restrict push to main and only allow CAB to approve via manual process.

Answer

Use a service hook to notify CAB when a PR is created, and rely on manual approval.

Answer

Add the CAB as members of the development team and require team review.

Question 13

Which TWO actions help improve communication and collaboration in a distributed Azure DevOps team?

Accepted Answer

Maintain a shared wiki with project documentation and decisions.. A shared wiki (e.g., Azure DevOps Wiki) provides a single source of truth for project documentation and decisions, accessible asynchronously—critical for distributed teams. Additionally, scheduling daily stand-up meetings at a time that works for all time zones ensures regular synchronous alignment and promotes collaboration. Multiple chat channels can fragment discussions, long email threads are hard to follow, and avoiding PR comments removes a key asynchronous review/discussion mechanism.

Answer

Use multiple chat channels for each topic to organize discussions.

Answer

Use long email threads for decision-making to ensure full documentation.

Answer

Avoid using pull request comments to reduce noise.

Question 14

Which THREE steps are essential when customizing an Azure DevOps process?

Accepted Answer

Add custom fields to work item types.. Customizing work item types by adding custom fields is a fundamental step in tailoring Azure DevOps processes to capture project-specific data. This is done through the inherited process model, which allows you to extend system processes without modifying the base definitions, ensuring upgrades and maintenance remain supported.

Answer

Use Hosted XML process model to customize.

Answer

Directly modify the 'Agile' system process.

Question 15

You are the Azure DevOps administrator for a large enterprise with multiple projects using the Scrum process. The organization has recently adopted a new compliance policy requiring that all work items of type 'Epic' must be approved by a compliance officer before they can be moved to the 'Committed' state. The compliance officers are external to the development teams and should not have direct access to modify work items. You need to implement this requirement with minimal administrative overhead. The current process has the following states for Epics: New, Proposed, Committed, In Progress, Done. The desired flow is: from 'Proposed' to 'Committed', a compliance officer must approve the transition. Compliance officers are part of a security group named 'Compliance Officers'. They should be able to approve the transition without having to edit the work item directly. What should you do?

Accepted Answer

In the process template for Epic, add a work item rule on the transition from 'Proposed' to 'Committed' that requires approval from a member of the 'Compliance Officers' group.. Azure DevOps process templates allow you to add work item rules on state transitions. By adding a rule on the 'Proposed' to 'Committed' transition for the Epic work item type that requires approval from a member of the 'Compliance Officers' group, you enforce the compliance policy without granting those officers direct edit permissions. This leverages built-in approval gates within the work item tracking system, minimizing administrative overhead.

Answer

Use a service hook to send an email to the compliance officers when an Epic is moved to 'Proposed', and rely on them to manually approve the transition.

Answer

Modify the Epic work item type to add a field 'Compliance Approval' and set the compliance officer as a required reviewer in the field settings.

Answer

Configure a branch policy on the main branch that requires approval from the 'Compliance Officers' group for pull requests.