A municipal automation client still holds a Cisco API representation and its ETag. How should the next GET be constructed to optimize bandwidth?
Select an answer to reveal the explanation.
Short Explanation
Show the coat-check stub: if nothing changed, they wave you through without handing the coat back. Pair the stored ETag with If-None-Match so the server can return 304 and skip the body.
Full Explanation
Conditional GET with If-None-Match and a previously received ETag is the standard validator pair for bandwidth optimization. When the representation is unchanged, the origin can respond 304 Not Modified and omit the payload. That pattern is the core HTTP cache-control technique DEVCOR expects consumers to use.