You want to optimize bandwidth by using ETags. Which combination of request and response headers correctly implements conditional GET caching?

hard📝 Application Q8 of 15

Rest API - Caching Strategies

AClient sends <code>If-None-Match: "etag123"</code>; server responds 304 if ETag matches

BClient sends <code>If-Match: "etag123"</code>; server responds 200 with full body if ETag matches

CClient sends <code>If-Modified-Since: "etag123"</code>; server responds 404 if ETag matches

DClient sends <code>If-Unmodified-Since: "etag123"</code>; server responds 500 if ETag matches

Step-by-Step Solution

Solution:

Step 1: Identify correct header for conditional GET with ETag
Client uses If-None-Match with ETag to ask server if resource changed.
Step 2: Understand server response on match
If ETag matches, server returns 304 Not Modified to save bandwidth.
Final Answer:
Client sends If-None-Match with ETag; server responds 304 if matches -> Option A
Quick Check:
Conditional GET uses If-None-Match and 304 response [OK]

Quick Trick: Use If-None-Match and 304 to save bandwidth with ETags [OK]

Common Mistakes:

MISTAKES

Master "Caching Strategies" in Rest API

9 interactive learning modes - each teaches the same concept differently

Want More Practice?

15+ quiz questions · All difficulty levels · Free

More Rest API Quizzes