AZ-400 Question 52
Single answerYour team wants to integrate an external testing dashboard that needs to receive a notification whenever a build successfully completes in Azure DevOps. You have configured a service hook (webhook) in your Azure DevOps project to post to the dashboard's REST endpoint when the 'Build completed' event triggers. However, the external dashboard is not receiving any notifications. You have verified that the external dashboard is reachable from other webhooks. Which action should you take first to ensure the notifications are sent correctly from Azure DevOps?
- A
Configure an Agent Pool in Azure DevOps to include the dashboard's endpoint as a webhook target.
- B
Edit the service hook subscription to use the correct 'Build completed' event and verify the endpoint URL and filters match the dashboard� requirements.
- C
Grant the external dashboard contributor permissions in the Azure DevOps project security settings.
- D
Add a custom build step in your YAML pipeline to manually POST build status to the external dashboard� endpoint.
Show answer and explanation
Correct answer: B
Explanation
When troubleshooting Azure DevOps webhooks, the first step is to confirm that the service hook (in Project Settings → Service Hooks) is correctly configured for the intended event and the correct endpoint. If you have the correct event type and endpoint, Azure DevOps will automatically send the build completion payload to the external system. For more guidance, refer to Microsoft� documentation on Service Hooks and webhooks: https://learn.microsoft.com/azure/devops/service-hooks/services/webhooks.
- A. Incorrect.
Option 1 is incorrect. Agent Pools are used to manage the pool of build agents that run your pipelines, not to configure or manage webhooks. Ensuring a webhook is triggered does not involve adding endpoints to an Agent Pool.
- B. Correct.
Option 2 is correct. If the external system is not receiving notifications, it is critical to verify the webhook subscription setting. Specifically, you must ensure the event (Build completed) is correctly selected, that the endpoint is correct, and that any event filters are configured appropriately. This is the first place to look when troubleshooting a webhook issue.
- C. Incorrect.
Option 3 is incorrect. Giving contributor permissions to the external system in Azure DevOps does not address webhook notifications. Webhooks do not require changing project security roles unless you need specifically authenticated access, which is not the main issue here.
- D. Incorrect.
Option 4 is incorrect. Manually adding a POST request in your YAML pipeline duplicates the purpose of the service hook. While this might work as a workaround, it defeats the built-in webhook functionality and is not the recommended first step.