An OAuth token response and a privileged Cisco inventory body both arrive with Cache-Control: no-store. What must the consumer do?
Select an answer to reveal the explanation.
Short Explanation
no-store is the librarian’s “do not photocopy the sealed personnel file.” Tokens and privileged inventory bodies must not be written into shared or disk caches—even if caching feels like an optimization.
Full Explanation
Cache-Control no-store directs that the representation must not be stored in non-volatile or shared caches. Applying that directive to tokens and privileged inventory protects confidentiality. Storing those bodies anyway to “optimize” API usage violates the control and confuses caching with secret handling.