If the data at the origin changes after being cached, what happens to subsequent reads?

If the data at the origin changes after being cached, what happens to subsequent reads?

• A. The cache continues serving the old data until manually cleared.
• B. The next read fetches fresh data from the origin and updates the cache.
• C. The origin change is rejected by the FlexCache.
• D. The entire origin dataset is re-cached automatically before serving.

Answer: (B)

When the origin data changes, the cached copy is considered stale and the system ensures subsequent reads fetch the latest data. In FlexCache’s read-through style, the next access validates against the origin and retrieves fresh data, updating the cache in the process. This means future reads will continue to use the updated value without requiring manual cache clearing. It isn’t about keeping old data indefinitely, nor about rejecting origin changes or re-caching the entire dataset automatically; the cache updates on demand as soon as the next read occurs.

When the origin data changes, the cached copy is considered stale and the system ensures subsequent reads fetch the latest data. In FlexCache’s read-through style, the next access validates against the origin and retrieves fresh data, updating the cache in the process. This means future reads will continue to use the updated value without requiring manual cache clearing. It isn’t about keeping old data indefinitely, nor about rejecting origin changes or re-caching the entire dataset automatically; the cache updates on demand as soon as the next read occurs.