Microsoft AZ-400 Exam - Topic 4 Question 102 Discussion

Actual exam question for Microsoft's AZ-400 exam

Question #: 102
Topic #: 4

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

Aa trigger

Ba pre deployment approval

Ca post-deployment approval

Da deployment gate

Show Suggested 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.

by Gilberto at Jul 16, 2024, 12:14 AM

Limited Time Offer

25%

Off

Get Premium AZ-400 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Marilynn

10 months ago

Totally agree with the deployment gate option!

upvoted 0 times

...

Corrinne

10 months ago

Wait, can a post-deployment approval really catch all issues?

upvoted 0 times

...

Wayne

10 months ago

Definitely a trigger for quality checks!

upvoted 0 times

...

Dahlia

10 months ago

I think a pre-deployment approval makes more sense.

upvoted 0 times

...

Stephen

10 months ago

A deployment gate is the way to go!

upvoted 0 times

...

Shoshana

11 months ago

From what I recall, post-deployment approvals are usually for checking after deployment, so I don't think that's the right choice here.

upvoted 0 times

...

Francoise

11 months ago

I’m a bit confused about whether a trigger or a gate is more appropriate for this situation. I need to think it through.

upvoted 0 times

...

Stevie

11 months ago

I remember practicing a question about pre-deployment approvals, and it seems like that could be relevant here too.

upvoted 0 times

...

Aleisha

11 months ago

I think we might need a deployment gate to ensure code quality before it goes live, but I'm not entirely sure.

upvoted 0 times

...

Mitzie

11 months ago

I'm not sure if a trigger or a post-deployment approval would be the right solution here. I'll need to double-check the details of each option.

upvoted 0 times

...

Rikki

11 months ago

I'm pretty confident that a pre-deployment approval would be the best way to implement the code quality restriction. That way, we can catch any issues before the code gets deployed.

upvoted 0 times

...

Magda

11 months ago

Hmm, I'm a bit confused by the wording of the question. I'll have to re-read it a few times to make sure I understand what they're asking.

upvoted 0 times

...

Melina

11 months ago

This seems like a tricky one. I'll need to think through the different options carefully.

upvoted 0 times

...

Tamera

11 months ago

Okay, I think I've got this. A deployment gate sounds like the right approach to enforce code quality restrictions on the release pipeline.

upvoted 0 times

...

Elli

11 months ago

Creating instructional videos seems interesting, but I’m not sure if that would actually lead to more sharing or just more viewers.

upvoted 0 times

...

Yolando

12 months ago

I feel like doing nothing is never a good option, but I guess some businesses choose that route when under pressure? I think BBB should consider some proactive strategy, but I'm torn on which one.

upvoted 0 times

...

Kathryn

12 months ago

In a practice question, we talked about how decentralization affects data security, which makes me lean towards true for this one.

upvoted 0 times

...

Katina

1 year ago

A deployment gate? More like a deployment moat! Gotta keep those bugs out of the investment planning castle.

upvoted 0 times

...

Shannan

1 year 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

Yvonne

1 year ago

True, a combination of deployment gates and pre-deployment approvals would be ideal for maintaining code quality.

upvoted 0 times

...

Kaycee

1 year ago

I think a pre-deployment approval could also be useful to catch any issues early on.

upvoted 0 times

...

Alana

1 year ago

I agree, deployment gates are essential for ensuring high code quality.

upvoted 0 times

...

Jestine

1 year ago

D all the way! Deployment gates are the gatekeepers of code quality.

upvoted 0 times

...

Mammie

1 year 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

Gearldine

1 year ago

Let's go with D then to implement the code quality restriction on the release pipeline.

upvoted 0 times

...

Aleta

1 year ago

Yeah, a deployment gate would definitely help in keeping the investment plans bug-free.

upvoted 0 times

...

Leonard

1 year ago

I agree, D seems like the best choice to ensure code quality.

upvoted 0 times

...

Mabel

1 year 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

Tracie

1 year ago

Let's go with D then. It's better to be safe than sorry when it comes to code quality.

upvoted 0 times

...

Ciara

1 year ago

I was considering B at first, but now I see the importance of using a deployment gate.

upvoted 0 times

...

Minna

1 year ago

Agreed, a deployment gate would definitely help prevent any spaghetti code from being released.

upvoted 0 times

...

Jamika

1 year ago

I think D is the way to go. We need to make sure the code quality is top-notch.

upvoted 0 times

...

Ozell

1 year 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

...