You have a microservice that calls two downstream services sequentially. How would you apply the fallback pattern to ensure the overall service remains responsive if either downstream service fails?

hard📝 Trade-off Q8 of 15

Microservices - Resilience Patterns

AOnly add a fallback to the first downstream service call

BRetry both downstream services indefinitely until success

CImplement separate fallback methods for each downstream call and return partial data if one fails

DRemove fallback and rely on client retries

Step-by-Step Solution

Solution:

Step 1: Understand fallback for multiple calls
Each downstream call can fail independently, so separate fallbacks allow handling failures gracefully per call.
Step 2: Provide partial data on failure
Returning partial data maintains responsiveness and user experience even if one service fails.
Final Answer:
Implement separate fallback methods for each downstream call and return partial data if one fails -> Option C
Quick Check:
Separate fallbacks for each call = partial data fallback [OK]

Quick Trick: Use separate fallbacks for each service call [OK]

Common Mistakes:

MISTAKES

Adding fallback only to one call
Relying on infinite retries
Removing fallback entirely

Master "Resilience Patterns" in Microservices

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Arch Try Challenge Design Recall Scale

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions

More Microservices Quizzes

You have a microservice that calls two downstream services sequentially. How would you apply the fallback pattern to ensure the overall service remains responsive if either downstream service fails?

Step 1: Understand fallback for multiple calls

Step 2: Provide partial data on failure

Final Answer:

Quick Check:

Want More Practice?