AZ-400 Service Hooks Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  First, navigate to Project Settings and select Service Hooks. Then, create a new subscription choosing the Build completed event and Microsoft Teams as the service. Finally, configure the webhook URL and test the subscription.

  Why this is correct

  This is the correct sequence because Azure DevOps requires you to navigate to Project Settings and select Service Hooks to reach the subscription management area. From there, you create a new subscription, choose the Build completed event as your trigger and Microsoft Teams as the service consumer. Finally, you configure the webhook URL for the Teams channel and test the subscription to verify that the payload is delivered successfully. This order aligns with the wizard-based flow and ensures the subscription exists before testing the connection.

• ✗

  First, create a new subscription choosing the Build completed event and Microsoft Teams. Then, navigate to Project Settings and select Service Hooks. Finally, configure the webhook URL and test the subscription.

  Why it's wrong here

  This order bypasses the necessary navigation step; you cannot create a service hook subscription without first opening the Service Hooks page in Project Settings. The subscription creation wizard is reached from that hub, and the Build completed event and Microsoft Teams service are selected during the creation flow. Starting with subscription creation leaves no context for where to define the event or service, so the first step must be navigating to the Service Hooks hub.

• ✗

  First, configure the webhook URL and test the subscription. Then, navigate to Project Settings and select Service Hooks. Finally, create a new subscription for the Build completed event.

  Why it's wrong here

  This sequence incorrectly front-loads the webhook configuration and testing. In Azure DevOps, a service hook subscription must exist before you can configure its webhook payload and validate delivery. Without first navigating to Project Settings > Service Hooks and creating a subscription, there is no endpoint to configure or test. The proper order is to create the subscription first, then paste the webhook URL and run a test.

• ✗

  First, choose Microsoft Teams as the service and paste the webhook URL. Then, navigate to Project Settings and select Service Hooks. Finally, create a new subscription for the Build completed event.

  Why it's wrong here

  This sequence wrongly omits the initial navigation and merges the service selection and webhook URL entry into a preliminary step. In Azure DevOps, you must first open Service Hooks from Project Settings; only then can you create a subscription, choose Microsoft Teams as the service, and provide the webhook URL as part of the action configuration. Pasting the webhook URL before the subscription exists is premature and not a valid first step.

Go deeper

Related to this question