Microsoft AZ-204 Exam - Topic 3 Question 114 Discussion

Actual exam question for Microsoft's AZ-204 exam

Question #: 114
Topic #: 3

You have an Azure API Management (APIM) Standard tier instance named APIM1 that uses a managed gateway.

You plan to use APIM1 to publish an API named API1 that uses a backend database that supports only a limited volume of requests per minute. You also need a policy for AP11 that will minimize the possibility that the number of requests to the backend database from an individual IP address you specify exceeds the supported limit.

You need to identify a policy for API1 that will meet the requirements.

Which policy should you use?

Aquota-by-key

Brate-limit

Cip-fitter

Drate-limit-by-key

Show Suggested Answer

Suggested Answer: D

by Rolf at Mar 06, 2025, 10:27 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Sheldon

5 months ago

Definitely going with rate-limit-by-key for this one!

upvoted 0 times

...

Haydee

5 months ago

Surprised that ip-fitter isn't an option here, it sounds useful!

upvoted 0 times

...

Kimberely

5 months ago

Isn't rate-limit better for controlling individual IPs?

upvoted 0 times

...

Charlene

5 months ago

I disagree, quota-by-key seems more fitting for this scenario.

upvoted 0 times

...

Reta

6 months ago

I think rate-limit-by-key is the best choice here.

upvoted 0 times

...

Kimbery

6 months ago

I feel like quota-by-key could also work, but it seems more focused on total requests over a longer period rather than per minute.

upvoted 0 times

...

Mignon

6 months ago

I practiced a similar question where we had to limit requests based on IP, and I think it was about using rate-limit-by-key.

upvoted 0 times

...

Norah

6 months ago

I think the rate-limit policy might be the right choice since it controls the number of requests per second, but I need to double-check the specifics.

upvoted 0 times

...

Donette

6 months ago

I remember studying the difference between rate limiting and quotas, but I'm not sure which one applies here.

upvoted 0 times

...

Danica

6 months ago

I'm pretty confident that the "quota-by-key" policy is the best option. It allows you to set a quota on the number of requests from a specific IP address, which should help prevent the backend database from being overwhelmed.

upvoted 0 times

...

Ammie

6 months ago

The "rate-limit-by-key" policy sounds like it might be the right choice here. It allows you to limit requests based on a specific key, which in this case could be the IP address.

upvoted 0 times

...

Belen

6 months ago

Hmm, I'm a bit confused by the different policy options. I'll need to review the details of each one to determine which one best meets the requirement of limiting requests from a specific IP address.

upvoted 0 times

...

Maybelle

6 months ago

This seems like a straightforward question about applying the right APIM policy to limit requests to a backend database. I think the key is to identify the policy that can limit requests based on the IP address.

upvoted 0 times

...

Fernanda

1 year ago

I agree with Tess, A) quota-by-key seems like the best choice to meet the requirements.

upvoted 0 times

...

Ernest

1 year ago

I think B) rate-limit could also be a valid option to consider.

upvoted 0 times

...

Vi

1 year ago

I disagree, I believe the correct answer is D) rate-limit-by-key.

upvoted 0 times

...

Shasta

1 year ago

This is a tough one, but I think D is the way to go. Gotta keep those greedy IP addresses in check, you know?

upvoted 0 times

...

Tess

1 year ago

I think the answer is A) quota-by-key.

upvoted 0 times

...

Ellsworth

1 year ago

Haha, I bet the backend database just can't handle all the traffic from the 'I love APIs' fan club. Better limit those requests, am I right?

upvoted 0 times

Pok

12 months ago

C) ip-fitter

upvoted 0 times

...

Dyan

1 year ago

B) rate-limit

upvoted 0 times

...

Paz

1 year ago

A) quota-by-key

upvoted 0 times

...

Ashley

1 year ago

Wait, isn't the ip-filter policy the one that allows you to specify a list of allowed or denied IP addresses? That might be a better fit here.

upvoted 0 times

Shakira

12 months ago

I agree, ip-filter will help limit requests from specific IP addresses.

upvoted 0 times

...

Jesusita

12 months ago

C) ip-fitter

upvoted 0 times

...

Maira

12 months ago

I think ip-filter is the best option for this scenario.

upvoted 0 times

...

Gail

12 months ago

D) rate-limit-by-key

upvoted 0 times

...

Jesusita

12 months ago

C) ip-fitter

upvoted 0 times

...

Frankie

1 year ago

B) rate-limit

upvoted 0 times

...

Malcom

1 year ago

A) quota-by-key

upvoted 0 times

...

Mitsue

1 year ago

I'm going with B. The rate-limit policy is designed to handle situations where you need to limit the number of requests, which is exactly what this question is asking for.

upvoted 0 times

Karl

1 year ago

I agree with you, D seems like the most appropriate choice for this scenario.

upvoted 0 times

...

Teddy

1 year ago

I think D is the best option. The rate-limit-by-key policy allows you to set limits based on a key, which would be useful for limiting requests from specific IP addresses.

upvoted 0 times

...

Martin

1 year ago

I'm going with B. The rate-limit policy is designed to handle situations where you need to limit the number of requests, which is exactly what this question is asking for.

upvoted 0 times

...

Kimberely

1 year ago

Hmm, I'm not so sure. The rate-limit policy might work as well, since it can limit the overall number of requests to the backend database.

upvoted 0 times

...

Gabriele

1 year ago

I think the answer is D. The rate-limit-by-key policy allows you to limit the number of requests from a specific IP address, which seems to be the requirement here.

upvoted 0 times