Bird
0
0

Why might a server choose to use a weak ETag instead of a strong ETag?

hard📝 Conceptual Q10 of 15
Rest API - Caching Strategies

Why might a server choose to use a weak ETag instead of a strong ETag?

ATo force clients to always re-download the resource
BTo identify resources by their size only
CTo allow minor changes that do not affect resource semantics
DTo disable caching entirely
Step-by-Step Solution
Solution:

  1. Step 1: Understand difference between weak and strong ETags

    Weak ETags tolerate minor changes that don't affect meaning; strong ETags require exact match.

  2. Step 2: Identify why weak ETags are used

    They allow caching even if minor, insignificant changes occur.

  3. Final Answer:

    To allow minor changes that do not affect resource semantics -> Option C

  4. Quick Check:

    Weak ETags tolerate minor changes [OK]
Quick Trick: Weak ETags allow caching despite minor resource changes [OK]
Common Mistakes:
MISTAKES
  • Thinking weak ETags disable caching
  • Confusing weak with strong ETags
  • Assuming weak ETags force reload

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Rest API Quizzes
API Testing and Monitoring - Integration testing - Quiz 3easy API Testing and Monitoring - Postman collection organization - Quiz 3easy API Testing and Monitoring - SLA and uptime tracking - Quiz 6medium Advanced Patterns - Long-running operations (async responses) - Quiz 5medium Batch and Bulk Operations - Batch create endpoint design - Quiz 7medium Caching Strategies - Cache-Control header directives - Quiz 11easy Caching Strategies - Why caching reduces server load - Quiz 13medium Caching Strategies - Expiration-based caching - Quiz 2easy Webhooks and Events - Event types and filtering - Quiz 7medium Webhooks and Events - Webhook payload design - Quiz 2easy