Question 657 of 997

Connect to and consume Azure services and third-party services →hardMultiple ChoiceObjective-mapped

Quick Answer

The correct choice is Azure API Management with its built-in rate-limit and caching policies. This combination directly addresses the need to enforce a rate limit of 10 requests per second for the third-party weather API and cache responses for 10 minutes, because APIM’s `rate-limit` policy allows you to set a per-key request quota, while the `cache-store` and `cache-lookup` policies automatically store and serve cached responses without requiring external services or custom code. On the AZ-204 exam, this scenario tests your understanding of how API Management centralizes cross-cutting concerns like throttling and caching, often appearing as a distractor against solutions using Azure Functions with custom logic or Redis Cache separately. A common trap is overcomplicating the solution by adding a separate caching service when APIM handles both requirements natively. Remember the memory tip: “APIM limits and caches in one pass,” so when you see rate limits and response caching together, think of API Management policies first.

AZ-204 Practice Question: Connect to and consume Azure services and third-party services

This AZ-204 practice question tests your understanding of connect to and consume azure services and third-party services. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

You are developing a web application that relies on a third-party weather API. The API has a rate limit of 10 requests per second per API key. You need to ensure your application never exceeds this limit and also caches responses for 10 minutes to reduce call frequency. Which combination of Azure services should you implement?

Clue words in this question

Noticing these words before you look at the options changes how you read each choice.

Clue: "never"
Why it matters: Absolute qualifier. True only if the statement has zero exceptions — be cautious of options that seem obvious but break down in edge cases.

Question 1hardmultiple choice

Read the full NAT/PAT explanation →

A
Azure Functions with Durable Functions to throttle calls and a static in-memory cache.
Why wrong: Implementing rate limiting and caching in Azure Functions requires custom code and managing state; it's less robust and scalable than using API Management's built-in policies.
B
Azure Logic Apps with a retry policy and a cache using Azure Redis Cache.
Why wrong: Logic Apps can cache but do not have native rate limiting policies. You would need to implement custom logic, increasing complexity. API Management is purpose-built for this.
C
Azure API Management with rate-limit and caching policies.
API Management provides out-of-the-box policies for rate limiting (by key or subscription) and caching (response cache). This is the recommended approach for controlling access to third-party APIs and improving performance.
D
Azure Traffic Manager to distribute requests and Azure Front Door for caching.
Why wrong: Traffic Manager is for global load balancing, not rate limiting. Front Door can cache content, but it does not provide fine-grained rate limiting policies per API key.

Full breakdown with real-world context →

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

✓

Azure API Management with rate-limit and caching policies.

Azure API Management (APIM) provides built-in rate-limit and caching policies that directly address the requirements: the `rate-limit` policy enforces a per-key request quota (e.g., 10 calls/second), and the `cache-store`/`cache-lookup` policies cache responses for a configurable duration (e.g., 10 minutes). This eliminates the need for custom throttling logic or external caching services, making it the most straightforward and maintainable solution.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
Azure Functions with Durable Functions to throttle calls and a static in-memory cache.
Why it's wrong here
Implementing rate limiting and caching in Azure Functions requires custom code and managing state; it's less robust and scalable than using API Management's built-in policies.
✗
Azure Logic Apps with a retry policy and a cache using Azure Redis Cache.
Why it's wrong here
Logic Apps can cache but do not have native rate limiting policies. You would need to implement custom logic, increasing complexity. API Management is purpose-built for this.
✓
Azure API Management with rate-limit and caching policies.
Why this is correct
API Management provides out-of-the-box policies for rate limiting (by key or subscription) and caching (response cache). This is the recommended approach for controlling access to third-party APIs and improving performance.
Clue confirmation
The clue word "never" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
Azure Traffic Manager to distribute requests and Azure Front Door for caching.
Why it's wrong here
Traffic Manager is for global load balancing, not rate limiting. Front Door can cache content, but it does not provide fine-grained rate limiting policies per API key.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often overcomplicate the solution by choosing a combination of services (e.g., Functions + Redis) when Azure API Management's single, purpose-built policy set directly solves both rate limiting and caching without custom code.

Detailed technical explanation

How to think about this question

APIM's `rate-limit` policy operates by tracking counters per API key in a distributed, in-memory counter store (using a sliding window algorithm), ensuring accurate enforcement even across multiple APIM instances. The caching policy uses a configurable TTL (time-to-live) and respects the `Cache-Control` headers from the backend, but if the backend omits them, APIM will cache based on the policy-defined duration. In a real-world scenario, if the third-party API returns different data for the same request (e.g., based on location), you must configure cache key variation (e.g., via `vary-by-query-parameter`) to avoid serving stale or incorrect cached responses.

KKey Concepts to Remember

Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.

TExam Day Tips

Watch for words such as best, first, most likely and least administrative effort.
Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related AZ-204 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Develop Azure compute solutions practice questions

Practise AZ-204 questions linked to Develop Azure compute solutions.

Develop for Azure storage practice questions

Practise AZ-204 questions linked to Develop for Azure storage.

Implement Azure security practice questions

Practise AZ-204 questions linked to Implement Azure security.

Connect to and consume Azure services and third-party services practice questions

Practise AZ-204 questions linked to Connect to and consume Azure services and third-party services.

Monitor, troubleshoot, and optimize Azure solutions practice questions

Practise AZ-204 questions linked to Monitor, troubleshoot, and optimize Azure solutions.

AZ-204 fundamentals practice questions

Practise AZ-204 questions linked to AZ-204 fundamentals.

AZ-204 scenario practice questions

Practise AZ-204 questions linked to AZ-204 scenario.

AZ-204 troubleshooting practice questions

Practise AZ-204 questions linked to AZ-204 troubleshooting.

Practice this exam

Start a free AZ-204 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

10 questions 20 questions 30 questions 50 questions Timed 30

AZ-204 practice-test guide →Study guide →Browse all practice tests

FAQ

Questions learners often ask

What does this AZ-204 question test?

Connect to and consume Azure services and third-party services — This question tests Connect to and consume Azure services and third-party services — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Azure API Management with rate-limit and caching policies. — Azure API Management (APIM) provides built-in rate-limit and caching policies that directly address the requirements: the `rate-limit` policy enforces a per-key request quota (e.g., 10 calls/second), and the `cache-store`/`cache-lookup` policies cache responses for a configurable duration (e.g., 10 minutes). This eliminates the need for custom throttling logic or external caching services, making it the most straightforward and maintainable solution.

What should I do if I get this AZ-204 question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Are there clue words in this question I should notice?

Yes — watch for: "never". Absolute qualifier. True only if the statement has zero exceptions — be cautious of options that seem obvious but break down in edge cases.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Keep practising

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

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.