Rest API - Rate Limiting and Throttling
You have a REST API that fetches user profile and user posts separately. To apply graceful degradation, which approach is best?
You have a REST API that fetches user profile and user posts separately. To apply graceful degradation, which approach is best?
hard📝 Application Q15 of 15
Step-by-Step Solution
Solution:
Step 1: Understand graceful degradation in multi-part fetch
It means returning partial data if one part fails, not stopping all.Step 2: Evaluate options for partial fallback
If fetching posts fails, return profile with empty posts list returns profile and empty posts if posts fail, matching graceful degradation.Final Answer:
If fetching posts fails, return profile with empty posts list -> Option AQuick Check:
Partial data returned on failure = graceful degradation [OK]
Quick Trick: Return partial data with fallback for failed parts [OK]
Common Mistakes:
- Stopping API on any failure
- Returning no data if one part fails
- Ignoring fallback for partial data
Master "Rate Limiting and Throttling" in Rest API
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Rest API Quizzes