Connect to and consume Azure services and third-party services →mediumMultiple ChoiceObjective-mapped
AZ-204 Practice Question: Connect to and consume Azure services and third-party services
Exhibit
{
"type": "Microsoft.ApiManagement/service/apis/policies",
"apiVersion": "2021-08-01",
"properties": {
"value": "<policies>\n <inbound>\n <base />\n <rate-limit calls=\"10\" renewal-period=\"60\" />\n </inbound>\n <backend>\n <base />\n </backend>\n <outbound>\n <base />\n </outbound>\n</policies>"
}
}Refer to the exhibit. The APIM policy is applied to an API. What is the effect of this policy?
⚠ Common exam trap
Many exam-takers confuse `rate-limit` (per-subscription, sliding window) with `rate-limit-by-key` (per-IP or custom key) or with a hard total quota, leading candidates to mistakenly choose IP-based or total-call options.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Each subscription can make up to 10 calls per minute.
The policy snippet uses the `rate-limit` policy, which enforces a per-subscription key rate limit. The `calls` attribute is set to 10 and the `renewal-period` is 60 seconds, meaning each subscription key is allowed up to 10 API calls within any 60-second sliding window. This matches option A exactly.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Each subscription can make up to 10 calls per minute.
Why this is correct
The `rate-limit` policy, when applied without a `by-key` attribute, defaults to limiting requests per subscription key. With `calls='10'` and `renewal-period='60'`, it precisely means that a single subscription is permitted to make a maximum of 10 API calls within any 60-second window. This ensures fair usage and prevents individual subscriptions from overwhelming the API backend.
- ✗
Each subscription can make up to 10 calls total.
Why it's wrong here
This statement is incorrect because the `rate-limit` policy implements a rolling window, not a cumulative total. The `renewal-period='60'` attribute explicitly indicates that the call count resets every 60 seconds, allowing for continued usage after the period expires. Therefore, the limit of 10 calls is per minute, not a lifetime maximum for the subscription.
- ✗
Each IP address can make up to 10 calls per minute.
Why it's wrong here
The `rate-limit` policy, as configured, applies its restrictions based on the subscription key provided in the request, not the client's IP address. To enforce limits per IP address, the policy would need to explicitly use `<rate-limit-by-key>` with a `counter-key` expression evaluating to `context.Request.IpAddress`. Without this specific configuration, the policy does not track or limit calls by IP.
- ✗
All calls from a single IP are blocked after 10 requests.
Why it's wrong here
This option is incorrect because the policy does not target IP addresses for blocking or limiting; its scope is the subscription key. Furthermore, exceeding the rate limit results in a `429 Too Many Requests` HTTP status code for subsequent calls within the renewal period, rather than an outright block of the IP address. The policy is designed for throttling, not for IP-based security blocking.
Go deeper
Related to this question
About these practice questions
One of 881 original AZ-204 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-204 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-204 exam.