Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Microsoft Exam AZ-400 Topic 4 Question 100 Discussion

Actual exam question for Microsoft's AZ-400 exam
Question #: 100
Topic #: 4
[All AZ-400 Questions]

Youhave a GitHub repository that is integrated with Azure Boards Azure Boards has a work item that has the number 715.

You need to ensure that when you commit source code in GitHub, the work item is updated automatically. What should you include in the commit comments?

Show Suggested Answer Hide Answer
Suggested Answer: A

To ensure that the webhook at https://contoso.com/statushook is called every time the repository named az40038443478acr1 receives a new version of an image named dotnetapp, you can follow these steps to configure a webhook in Azure Container Registry:

Navigate to the Azure Container Registry:

Go to the Azure Portal.

Find and select your Azure Container Registry instance az40038443478acr1.

Create a New Webhook:

Under Services, select Webhooks.

Click on + Add to create a new webhook.

Fill in the form with the following information:

Webhook name: Enter a unique name for your webhook.

Service URI: Enter https://contoso.com/statushook.

Custom headers: (Optional) Add any headers you want to pass along with the POST request.

Trigger actions: Select Push to trigger the webhook on image push events.

Scope: Specify the scope as az40038443478acr1:dotnetapp to target the specific image.

Status: Set to Enabled.

Save the Webhook Configuration:

Review the information and click Create to save the webhook.

Once configured, the webhook will send a POST request to https://contoso.com/statushook whenever a new version of the dotnetapp image is pushed to the az40038443478acr1 repository in your Azure Container Registry1.

This setup will automate the notification process, ensuring that the specified webhook is called with each new image version, thus fulfilling the task requirements.


Contribute your Thoughts:

Cherrie
2 days ago
Ooh, this is a tricky one. Let me think... Ah, got it! Definitely D. Gotta love it when technology makes our lives easier, am I right? *winks*
upvoted 0 times
...
Luz
17 days ago
Whoa, hold up! I was about to go with C, but D makes way more sense. Linking the commit directly to the work item? Genius!
upvoted 0 times
...
Annice
21 days ago
Hmm, I think it's option D. GitHub automatically recognizes the 'AB#' syntax and links the commit to the work item. Gotta stay on top of those work items, am I right?
upvoted 0 times
Mira
2 days ago
I think so too. GitHub makes it simple with the 'AB#' syntax.
upvoted 0 times
...
Chandra
4 days ago
I agree, option D is the way to go. It's the easiest way to link the commit to the work item.
upvoted 0 times
...
...
Latrice
28 days ago
I'm not sure, but maybe we can also use AB#715 in the commit comments to update the work item.
upvoted 0 times
...
Margery
29 days ago
I agree with Christiane. Including the URL of the work item will ensure it is updated automatically.
upvoted 0 times
...
Christiane
1 months ago
I think we should include the URL of the work item in the commit comments.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77