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 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]

What should you use to implementthe code quality restriction on the release pipeline for the investment planning applications suite?

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:

Katina
15 days ago
A deployment gate? More like a deployment moat! Gotta keep those bugs out of the investment planning castle.
upvoted 0 times
...
Shannan
16 days ago
D all the way! Deployment gates are the gatekeepers of code quality. Can't have any investment planning mishaps on my watch.
upvoted 0 times
...
Mammie
28 days ago
Hmm, I was thinking A, but D sounds like the right choice. Gotta keep those investment plans bug-free, you know?
upvoted 0 times
Leonard
9 days ago
I agree, D seems like the best choice to ensure code quality.
upvoted 0 times
...
...
Mabel
1 months ago
I was leaning towards B, but D makes more sense. Can't risk releasing spaghetti code to the investment planning app!
upvoted 0 times
...
Ozell
1 months ago
I think the correct answer is D. A deployment gate is used to enforce code quality restrictions on the release pipeline. It's the perfect tool for the job.
upvoted 0 times
...
Lindsey
2 months ago
I prefer using a deployment gate to implement code quality restriction.
upvoted 0 times
...
Derick
2 months ago
I agree with Jamie, a pre deployment approval ensures code quality before deployment.
upvoted 0 times
...
Jamie
2 months ago
I think we should use a pre deployment approval.
upvoted 0 times
...

Save Cancel