A user edits an order in a detail view, navigates back to the list, and the list still shows the old value. Then they hard-refresh and it is correct. What is your model of the client cache, and where do you fix this?
Answer it out loud before you open anything. The value of the flags below is in comparing them to what you actually said.
The situation behind the question
A SPA using a data-fetching library with cached queries. The mutation succeeds; the server is correct. The team's current fix in similar cases has been to refetch on window focus.
What it is really testing
Whether the candidate has a coherent model of client cache keys and invalidation, or treats the cache as an accident to be worked around. The hard-refresh detail rules out the server and the HTTP cache and points squarely at in-memory state.