Cyber Monday 2024! 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 3 Question 105 Discussion

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

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

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:

Bulah
2 months 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?
upvoted 0 times
Vicente
1 months ago
If you encounter any issues, don't hesitate to ask for help or clarification.
upvoted 0 times
...
Desmond
1 months ago
It's always a good idea to double-check your work before assuming it's all set.
upvoted 0 times
...
Jame
1 months ago
Don't forget to test the webhook to ensure it's working correctly.
upvoted 0 times
...
Brice
2 months ago
Make sure to carefully follow the steps in the solution provided.
upvoted 0 times
...
...
Ruth
2 months ago
I bet the guy who came up with 'az40038443478acr 1' as a repository name is the same one who designed the keyboard layout.
upvoted 0 times
Janessa
1 months ago
I can't even imagine typing that out every time I need to access it.
upvoted 0 times
...
Mozell
1 months ago
I know right, it's like they just smashed their keyboard to come up with it.
upvoted 0 times
...
Fannie
2 months ago
Haha, that repository name is a mouthful!
upvoted 0 times
...
...
Elsa
2 months ago
Yes, we can create a pipeline trigger on image updates to call the webhook.
upvoted 0 times
...
Jesusa
3 months ago
I believe we need to use Azure DevOps pipelines for this.
upvoted 0 times
...
Corazon
3 months ago
I agree, setting up webhooks can be tricky.
upvoted 0 times
...
Ryan
3 months ago
I think this task is challenging.
upvoted 0 times
...
Colene
3 months ago
Hmm, I'm not sure about the image name 'dotnetapp'. Shouldn't it be more specific, like 'myapp:v1.0' or something?
upvoted 0 times
...
Rashad
3 months 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.
upvoted 0 times
Marguerita
3 months ago
Don't worry, the URL is case-sensitive. Just double check the casing when setting it up.
upvoted 0 times
...
Rodrigo
3 months ago
Yes, the URL is case-sensitive. Make sure to use the correct casing for 'contoso.com/statushook'.
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