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 100 Discussion

Actual exam question for Microsoft's AZ-400 exam
Question #: 100
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:

Phung
5 months ago
Yes, we also need to ensure the repository and image names are accurate for the webhook to work.
upvoted 0 times
...
Rashida
5 months ago
Ha! Reminds me of that time I forgot to update the firewall rules and the webhook just spun its wheels. Gotta love DevOps, am I right?
upvoted 0 times
Stephanie
4 months ago
Definitely! One small mistake can cause a lot of headaches in the DevOps world.
upvoted 0 times
...
Norah
5 months ago
Yeah, I've been there before. It's important to double check those configurations.
upvoted 0 times
...
...
Caren
5 months ago
I believe we need to configure the webhook URL and payload correctly.
upvoted 0 times
...
Georgene
5 months ago
Wait, does this mean I have to configure the webhook URL and security settings too? Ugh, the devil is in the details, as they say.
upvoted 0 times
Trinidad
4 months ago
Once you have everything configured correctly, the webhook should be called every time a new version of the image is received.
upvoted 0 times
...
Princess
4 months ago
It's important to pay attention to the details when setting up webhooks.
upvoted 0 times
...
Pedro
5 months ago
Don't forget to set up the security settings to ensure the webhook is called properly.
upvoted 0 times
...
Ammie
5 months ago
Yes, you will need to configure the webhook URL for the repository.
upvoted 0 times
...
...
Tyisha
5 months ago
I agree, setting up webhooks can be tricky.
upvoted 0 times
...
Allene
5 months ago
I think this task is quite challenging.
upvoted 0 times
...
Precious
6 months ago
This seems straightforward. Just need to set up a trigger for the dotnetapp image updates and point it to the statushook webhook. Easy peasy!
upvoted 0 times
Joseph
5 months ago
Yep, it's a simple setup. Just make sure everything is configured correctly.
upvoted 0 times
...
Annabelle
5 months ago
That's right! Just set up the trigger for the image updates and link it to the webhook.
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