Operators place a Redis-like key-value cache in front of citizen profiles to speed reads. What must they remember about that cache tier?
Select an answer to reveal the explanation.
Short Explanation
A cache is the espresso shot—fast, not the whole pantry. Profiles still need a durable system of record behind Redis-like layers. Lose only the cache and you should still rebuild from the real store.
Full Explanation
In-memory or KV caches improve read latency by holding hot copies of data. They are typically volatile or secondary relative to a durable system of record that owns authoritative citizen profiles. Treating the cache as the sole system of record risks data loss and weak auditability. Clear tier roles keep civic profile integrity intact while still gaining performance.