Bird
0
0

A microservice call retries 3 times on failure but never succeeds. What is the main issue in this retry design?

medium📝 Analysis Q14 of 15
Microservices - Real-World Architecture Case Studies
A microservice call retries 3 times on failure but never succeeds. What is the main issue in this retry design?
ANo fallback mechanism to handle persistent failure
BRetries cause infinite loops without limits
CRetries are too few to recover from failure
DService calls are synchronous causing delays
Step-by-Step Solution
Solution:

  1. Step 1: Analyze retry behavior

    Retries are limited to 3 attempts, so no infinite loop.

  2. Step 2: Identify missing resilience feature

    Without fallback, system cannot recover after retries fail.

  3. Final Answer:

    No fallback mechanism to handle persistent failure -> Option A

  4. Quick Check:

    Retries need fallback for persistent failures [OK]
Quick Trick: Retries alone can't fix persistent failures; add fallback [OK]
Common Mistakes:
  • Confusing retry limits with infinite loops
  • Assuming more retries always solve failures
  • Ignoring fallback importance

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Microservices Quizzes
Advanced Patterns - Ambassador pattern - Quiz 1easy CI/CD for Microservices - Mono-repo vs multi-repo - Quiz 4medium Configuration and Secrets Management - Why externalized config enables flexibility - Quiz 4medium Migration from Monolith - Anti-corruption layer - Quiz 15hard Real-World Architecture Case Studies - Architecture decision records (ADR) - Quiz 13medium Real-World Architecture Case Studies - Uber architecture overview - Quiz 12easy Real-World Architecture Case Studies - Microservices maturity model - Quiz 14medium Testing Microservices - End-to-end testing challenges - Quiz 11easy Testing Microservices - Chaos engineering basics - Quiz 14medium Testing Microservices - Integration testing - Quiz 3easy