AZ-400 - Design and Implement Processes and Communications (13% of the exam) - Section 1.3

Configure collaboration and communication, including wikis, release documentation, webhooks, and integration between Azure Boards, GitHub, and Microsoft Teams.

Configure Azure DevOps wikis with Mermaid syntax diagrams, publish release documentation, and set up service hooks and webhooks to push pipeline events to external systems. Recognise when to use Microsoft Teams integration versus direct Azure Boards and GitHub integration to route notifications and approvals to the right team channels.

Azure DevOps wikiMermaid syntaxservice hooks and webhooksMicrosoft Teams integrationAzure Boards and GitHub integration

Practice question for this objective

Free sampleDesign and Implement Processes and Communicationsmedium

A team wants every change to a work item's state in "Azure DevOps" to post a payload to an internal incident-tracking service at a fixed HTTPS endpoint, with no extra software installed in Azure DevOps. Which Azure DevOps feature should they configure to deliver that payload on the event?

AA pipeline service connection that authenticates to the incident service and runs a script step to forward the work item change after each build completes.
BA branch policy with a status check that calls the incident service whenever a pull request updates a linked work item's state during the review.
CA service hook subscription using the web hooks consumer, filtered to the work item updated event, posting a JSON payload to the incident service endpoint. Correct
DA Microsoft Teams channel connector that mirrors work item updates and relays each notification onward to the incident service over its inbound webhook.

Use an Azure DevOps service hook with the web hooks consumer to push event payloads to an external HTTPS endpoint. Service hooks let Azure DevOps react to events such as work item updated and call out to other services. The generic web hooks consumer posts a JSON payload to a specified HTTPS endpoint, so no agent or installed integration is needed to forward the event.

Why A is wrong: A service connection forwards data only when a pipeline runs, so it is tempting for outbound calls but it cannot fire on a work item state change that happens outside any pipeline.

Why B is wrong: A branch policy status check reacts to pull requests, which makes it look event-driven, but it does not trigger on a standalone work item state change and is scoped to a branch.

Why C is correct: A service hook subscription with the web hooks consumer fires on the chosen Azure DevOps event and posts a JSON payload to any HTTPS endpoint, which matches the requirement without installing anything.

Why D is wrong: A Teams connector surfaces updates inside a channel and is tempting because it uses a webhook, but it targets Teams rather than delivering a payload straight to the incident service.

See more AZ-400 practice questions, answers explained.

Exam traps in Design and Implement Processes and Communications

Answers that look right on this material and are not. Each one is a distractor from a different question in the AZ-400 bank for this domain.

The text "#1453" in the commit message, so GitHub's own issue cross-reference passes the number through to the linked Azure Boards work item.
Why it is wrong: The plain "#1453" form is GitHub's issue reference and is tempting, but it points at a GitHub issue and is not interpreted by Azure Boards as a work item mention.
Configure a service hook subscription with the web hooks consumer that posts the raw build event JSON to the channel's email address for the engineers to read.
Why it is wrong: Posting raw event JSON to a channel email is tempting because service hooks fire on build events, but the message is unformatted and email-to-channel is a clumsier path than the dedicated app.
The "Azure Pipelines" app for Microsoft Teams, which forwards repository pull request and board assignment events to channels.
Why it is wrong: It is tempting because it is a sibling first-party app, but the Azure Pipelines app handles pipeline run and approval events, not pull request creation or work item assignment, so it cannot deliver either notification.

Examworthy is not affiliated with or endorsed by Microsoft. Original, blueprint-aligned practice material only.