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 AZ-400 Exam - Topic 3 Question 105 Discussion

Posted by Antonio on Sep 07, 2024 at 01:52 AM

SIMULATION

Task 8

You need to ensure that the https://contoso.com/statushook webhook is called every time a repository named az40038443478acr 1 receives a new version of an image named dotnetapp

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.


Get Premium AZ-400 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
30 comments · newest first
JA
James 11 months ago
I thought webhooks only worked for specific events, not every version.
AI
Aide 11 months ago
Yup, that's how webhooks work!
WA
Wai 11 months ago
Wait, does it really trigger for every new image version?
SH
Sherell 12 months ago
Totally agree, it's super easy to do.
KR
Kris 12 months ago
Just set up a webhook for the repo!
CE
Cecily 1 year ago
I’m a bit confused about the exact syntax for the webhook URL. I hope it’s similar to what we practiced in the labs.
HY
Hyman 1 year ago
I feel like there might be some permissions we need to check for the webhook to work correctly. I hope I don't forget that part!
HE
Heike 1 year ago
I remember practicing a similar question where we had to configure a webhook for a different repository. I think it involved using a specific API call.
TY
Ty 1 year ago
I think we need to set up a webhook in the repository settings, but I'm not entirely sure how to link it to the specific image version.
AN
Annelle 1 year ago
I'm a bit confused by the wording of the question. What exactly do they mean by "ensure the webhook is called"? Do I need to set up the webhook itself, or just the trigger to call it? I'll have to read through it carefully and make sure I understand all the requirements.
AL
Alisha 1 year ago
I've done something similar before, so I think I've got a good strategy. I'll need to look into Azure Container Registry webhooks and how to configure them to trigger on specific image updates. Shouldn't be too hard, just need to pay attention to the details.
AD
Adelina 1 year ago
Okay, let's see. I think I need to set up some kind of trigger or event that will call the webhook whenever a new version of the dotnetapp image is pushed to the az40038443478acr 1 repository. But I'm not sure of the exact details.
RE
Rebbecca 1 year ago
Hmm, this looks like a tricky one. I'll need to think through the steps carefully to ensure I cover all the requirements.
BU
Bulah 2 years ago
This is a pretty straightforward task. I'm just going to copy-paste the solution and hope for the best. What could go wrong?
VI
Vicente 2 years ago
↳ replying to Bulah
If you encounter any issues, don't hesitate to ask for help or clarification.
DE
Desmond 2 years ago
↳ replying to Bulah
It's always a good idea to double-check your work before assuming it's all set.
JA
Jame 2 years ago
↳ replying to Bulah
Don't forget to test the webhook to ensure it's working correctly.
BR
Brice 2 years ago
↳ replying to Bulah
Make sure to carefully follow the steps in the solution provided.
RU
Ruth 2 years ago
I bet the guy who came up with 'az40038443478acr 1' as a repository name is the same one who designed the keyboard layout.
JA
Janessa 2 years ago
↳ replying to Ruth
I can't even imagine typing that out every time I need to access it.
MO
Mozell 2 years ago
↳ replying to Ruth
I know right, it's like they just smashed their keyboard to come up with it.
FA
Fannie 2 years ago
↳ replying to Ruth
Haha, that repository name is a mouthful!
EL
Elsa 2 years ago
Yes, we can create a pipeline trigger on image updates to call the webhook.
JE
Jesusa 2 years ago
I believe we need to use Azure DevOps pipelines for this.
CO
Corazon 2 years ago
I agree, setting up webhooks can be tricky.
RY
Ryan 2 years ago
I think this task is challenging.
CO
Colene 2 years ago
Hmm, I'm not sure about the image name 'dotnetapp'. Shouldn't it be more specific, like 'myapp:v1.0' or something?
RA
Rashad 2 years ago
The solution looks good, but I have a question about the URL. Is it case-sensitive? I don't want to mess this up.
MA
Marguerita 2 years ago
↳ replying to Rashad
Don't worry, the URL is case-sensitive. Just double check the casing when setting it up.
RO
Rodrigo 2 years ago
↳ replying to Rashad
Yes, the URL is case-sensitive. Make sure to use the correct casing for 'contoso.com/statushook'.
0/2000 characters

Save Cancel