AZ-204 Practice Question: Connect to and consume Azure services and third-party services
Which THREE Azure services or features can be used to implement retry logic for transient failures when calling an external API from a .NET Core application?
⚠ Common exam trap
It's easy for candidates to confuse network-level traffic management services (Traffic Manager, Front Door) with application-level retry mechanisms, assuming they handle transient failures automatically when they only provide routing and load balancing.
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 SDK retry policies
Azure SDK retry policies (A) are correct because the Azure SDK for .NET includes built-in retry policies (e.g., ExponentialRetry, FixedRetry) that automatically handle transient failures such as 408, 429, 500, 502, 503, and 504 responses when calling Azure services or external endpoints through the SDK pipeline. Azure Logic Apps retry policy (B) is correct because Logic Apps actions support configurable retry policies (default, exponential interval, fixed interval) with parameters like count, interval, and maximumInterval, which can wrap HTTP calls to external APIs and retry on transient errors. Polly library (C) is correct because Polly is a .NET resilience and transient-fault-handling library that provides policies such as Retry, WaitAndRetry, and WaitAndRetryAsync with exponential backoff and jitter, and it integrates directly into .NET Core applications via HttpClientFactory. Azure Traffic Manager (D) is not correct because it is a DNS-based global traffic distribution service that routes users to endpoints; it does not implement application-level retry logic for outbound API calls. Azure Front Door (E) is not correct because it is a layer-7 global load balancer and CDN that can retry requests at the edge for inbound traffic, but it does not provide retry logic inside a .NET Core application calling an external API.
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 SDK retry policies
Why this is correct
Many Azure SDKs, such as those for Storage, Cosmos DB, and Service Bus, incorporate built-in retry policies to handle transient faults automatically. These policies typically employ strategies like exponential backoff with jitter, allowing client applications to gracefully recover from temporary network issues or service unavailability without custom code. Developers can often configure parameters like the maximum number of retries and the delay between attempts, ensuring robust communication with Azure services.
- ✓
Azure Logic Apps retry policy
Why this is correct
Azure Logic Apps provides native retry policies configurable directly on individual actions within a workflow, enabling resilience for calls to external services or Azure connectors. This feature allows developers to define the retry type, such as exponential interval or fixed interval, along with the maximum count and interval duration. By automatically reattempting failed operations, Logic Apps ensures the continuity of business processes even when transient issues affect integrated systems.
- ✓
Polly library
Why this is correct
Polly is a popular open-source .NET resilience and transient-fault-handling library that allows developers to fluently express policies like Retry, Circuit Breaker, Timeout, and Fallback. It provides a robust and flexible way to add resilience to any outgoing HTTP requests or other operations within a .NET application. By integrating Polly, applications can programmatically handle transient failures with sophisticated strategies, significantly improving their robustness and user experience.
- ✗
Azure Traffic Manager
Why it's wrong here
Azure Traffic Manager operates as a DNS-based traffic load balancer, distributing user traffic to globally dispersed endpoints based on various routing methods like priority, performance, or geographic location. Its primary function is to provide high availability and responsiveness by directing users to the healthiest available endpoint, but it does not implement application-level retry logic for failed requests. Traffic Manager works at the DNS layer, resolving names to IP addresses, rather than intercepting or reattempting HTTP calls.
- ✗
Azure Front Door
Why it's wrong here
Azure Front Door is a global, scalable entry-point that uses the Microsoft global edge network to create fast, secure, and widely scalable web applications. While it offers features like global HTTP/S load balancing, URL-based routing, and a Web Application Firewall (WAF), it does not perform application-level retries for backend service calls. Front Door routes incoming client requests to the optimal backend based on health probes and routing rules, but it does not re-issue requests if the backend fails to respond to the initial attempt.
Visual reference
Go deeper
Related to this question
About these practice questions
Courseiva writes every AZ-204 question from scratch — 883 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. 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.