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-204 Topic 3 Question 114 Discussion

Actual exam question for Microsoft's AZ-204 exam
Question #: 114
Topic #: 3
[All AZ-204 Questions]

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?

Show Suggested Answer Hide Answer
Suggested Answer: D

Contribute your Thoughts:

Fernanda
16 days ago
I agree with Tess, A) quota-by-key seems like the best choice to meet the requirements.
upvoted 0 times
...
Ernest
17 days ago
I think B) rate-limit could also be a valid option to consider.
upvoted 0 times
...
Vi
18 days ago
I disagree, I believe the correct answer is D) rate-limit-by-key.
upvoted 0 times
...
Shasta
18 days 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
19 days ago
I think the answer is A) quota-by-key.
upvoted 0 times
...
Ellsworth
19 days 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
Paz
2 days ago
A) quota-by-key
upvoted 0 times
...
...
Ashley
28 days 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
Frankie
6 days ago
B) rate-limit
upvoted 0 times
...
Malcom
8 days ago
A) quota-by-key
upvoted 0 times
...
...
Mitsue
1 months 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
16 days ago
I agree with you, D seems like the most appropriate choice for this scenario.
upvoted 0 times
...
Teddy
21 days 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
25 days 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 months 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 months 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
Lizbeth
12 days ago
Let's go with D, rate-limit-by-key policy for API1.
upvoted 0 times
...
Leontine
14 days ago
Yes, rate-limit-by-key will help in limiting requests from a specific IP address.
upvoted 0 times
...
Catrice
17 days ago
I think rate-limit-by-key is the best option for this scenario.
upvoted 0 times
...
Dorothea
23 days ago
I agree with you, D seems to be the correct answer.
upvoted 0 times
...
...

Save Cancel