Rest API - Caching Strategies
Why might a server choose to use weak ETags instead of strong ETags in validation-based caching?
Why might a server choose to use weak ETags instead of strong ETags in validation-based caching?
hard📝 Conceptual Q10 of 15
Step-by-Step Solution
Solution:
Step 1: Understand difference between weak and strong ETags
Weak ETags tolerate minor changes that don't affect resource meaning.Step 2: Reason why server uses weak ETags
They avoid unnecessary cache invalidation for insignificant changes.Final Answer:
To allow minor changes without forcing cache refresh -> Option DQuick Check:
Weak ETags allow minor changes without refresh = C [OK]
Quick Trick: Weak ETags tolerate small changes to avoid cache misses [OK]
Common Mistakes:
MISTAKES- Thinking weak ETags improve security
- Believing weak ETags disable caching
- Assuming HTTP/2 requires weak ETags
Master "Caching Strategies" in Rest API
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Rest API Quizzes