New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Microsoft AZ-400 Exam - 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:

0/2000 characters
Dorothy
3 months ago
I thought we needed to reference the issue number differently.
upvoted 0 times
...
Hildegarde
3 months ago
Wait, is it really that simple? Just AB#715?
upvoted 0 times
...
Lavonda
3 months ago
I disagree, I thought it was C with the URL.
upvoted 0 times
...
Solange
4 months ago
Yeah, D makes the most sense!
upvoted 0 times
...
Val
4 months ago
I think it's D, AB#715 is the right format.
upvoted 0 times
...
Paris
4 months ago
I’m leaning towards option D, "AB#715". I practiced a similar question where we had to format the commit message correctly for Azure integration.
upvoted 0 times
...
Nadine
4 months ago
I definitely recall that we need to reference the work item number directly, but I can't remember if it was with "AB#" or just the number itself.
upvoted 0 times
...
Raelene
4 months ago
I'm not entirely sure, but I feel like it might be option B with the equals sign. That seems familiar from a practice question.
upvoted 0 times
...
Justine
5 months ago
I think I remember something about using a specific format to link work items in Azure Boards. Was it something like "AB#"?
upvoted 0 times
...
Kenneth
5 months ago
I'm a little confused by this question. Do we need to include the full URL of the work item, or just the number? I want to make sure I get the right format in my commit message.
upvoted 0 times
...
Alesia
5 months ago
Okay, I've got this. The answer is D - we need to use the "AB#715" syntax to link the commit to the work item with ID 715. I've seen this used before when integrating GitHub and Azure Boards.
upvoted 0 times
...
Annette
5 months ago
Hmm, I'm a bit unsure about this one. I know we need to somehow reference the work item number, but I'm not sure if we use the @ symbol or the # symbol. I'll have to think this through carefully.
upvoted 0 times
...
Natalya
5 months ago
This looks like a straightforward question about linking GitHub commits to Azure Boards work items. I think the key is to find the right syntax to include in the commit message.
upvoted 0 times
...
Yolande
5 months ago
Okay, I've got this. Horizontal analysis is the technique for looking at the percentage changes in individual financial statement items from one period to the next. I'm confident that's the right answer here.
upvoted 0 times
...
Adelle
5 months ago
I feel like the Intelligent Proxy might be the right answer since it directly involved routing traffic correctly during our practice exams.
upvoted 0 times
...
Gracia
5 months ago
I'm not so sure... I feel like I came across something similar in practice questions. Wasn't Consumer-to-Contract a type of positive coupling?
upvoted 0 times
...
Shala
9 months ago
Ah, the old 'link the commit to the work item' trick. Good thing I've got my trusty GitHub cheat sheet handy. Option D is the way to go, folks!
upvoted 0 times
Dierdre
8 months ago
No need, just stick with AB#715 for now.
upvoted 0 times
...
Ozell
8 months ago
Should we also include the URL of the work item?
upvoted 0 times
...
Alfreda
8 months ago
Yeah, that's the right way to link the commit to the work item.
upvoted 0 times
...
Nan
9 months ago
I think we should include AB#715 in the commit comments.
upvoted 0 times
...
...
Reiko
10 months ago
I'm going with D all the way! Anything to avoid manually updating those work items. I mean, who has time for that when you've got code to write? *laughs*
upvoted 0 times
Colette
9 months ago
User 3: Definitely, D saves a lot of time and effort.
upvoted 0 times
...
Veronika
9 months ago
User 2: Yeah, I agree. It's so much easier than doing it manually.
upvoted 0 times
...
Mona
9 months ago
User 1: I think D is the way to go. It automatically updates the work item.
upvoted 0 times
...
...
Cherrie
10 months 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
Tu
9 months ago
User 3: Miss is correct, it should be AB#715.
upvoted 0 times
...
Miss
9 months ago
User 2: Nope, that's not it.
upvoted 0 times
...
Daniel
9 months ago
User 1: @714
upvoted 0 times
...
...
Luz
11 months 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
Corrina
9 months ago
User 2: Yeah, that's a smart move. It keeps everything connected and organized.
upvoted 0 times
...
Han
10 months ago
User 1: I think D is the way to go. It links the commit to the work item directly.
upvoted 0 times
...
...
Annice
11 months 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
Garry
10 months ago
Great, we're all on the same page with option D then. Let's make sure to use it for our commits.
upvoted 0 times
...
Elly
10 months ago
Definitely, it's important to keep everything organized with the work items.
upvoted 0 times
...
Mira
10 months ago
I think so too. GitHub makes it simple with the 'AB#' syntax.
upvoted 0 times
...
Chandra
10 months 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
11 months 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
11 months ago
I agree with Christiane. Including the URL of the work item will ensure it is updated automatically.
upvoted 0 times
...
Christiane
11 months ago
I think we should include the URL of the work item in the commit comments.
upvoted 0 times
...

Save Cancel