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 4 Question 102 Discussion

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

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:

Kayleigh
4 months ago
I hope the 'dotnetapp' image doesn't contain any garlic. That would be a real nightmare for the webhook!
upvoted 0 times
...
Emilio
4 months ago
This looks good. Just make sure the webhook is properly secured and authenticated to prevent any unauthorized access.
upvoted 0 times
Vince
3 months ago
I will ensure that the webhook is properly secured.
upvoted 0 times
...
Staci
3 months ago
Yes, security is important to prevent unauthorized access.
upvoted 0 times
...
Ciara
3 months ago
Make sure to set up proper authentication for the webhook.
upvoted 0 times
...
...
Jerry
4 months ago
Hmm, I'm a bit curious about the specifics of the 'dotnetapp' image. Is it a web application or a background service? That might affect the implementation a bit.
upvoted 0 times
Luann
3 months ago
It's a background service.
upvoted 0 times
...
Ricarda
3 months ago
It's a web application.
upvoted 0 times
...
...
Danica
4 months ago
I think we should test the webhook after setting it up to ensure it works as expected.
upvoted 0 times
...
Wendell
4 months ago
Yes, we also need to make sure the webhook is triggered on image updates.
upvoted 0 times
...
Chanel
4 months ago
I believe we need to configure the webhook URL and payload correctly.
upvoted 0 times
...
Fannie
5 months ago
Ah, I see. Calling the webhook for every new image version is a pretty standard requirement. This should be easy to implement.
upvoted 0 times
...
Jacob
5 months ago
I think this is a straightforward task. The solution provided should work just fine.
upvoted 0 times
Lemuel
4 months ago
I'll go ahead and configure the webhook for the repository and image as specified in the task.
upvoted 0 times
...
Clay
4 months ago
We just need to make sure the webhook is triggered whenever the specified repository receives a new version of the image.
upvoted 0 times
...
Elliot
4 months ago
I agree, it seems like a simple task to set up that webhook.
upvoted 0 times
...
...
Danica
5 months ago
I agree, setting up webhooks can be tricky.
upvoted 0 times
...
Wendell
5 months ago
I think this task is quite challenging.
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