Answer these interview prompts as if you had to defend a design on a whiteboard. The options are deliberately short; the reason is where you show that the requirement caused the decision. Don't add a distributed component simply because it is familiar. A small service still needs a correctness argument when two requests race.
The questions revisit latency, durable identity, caches and request routing using fresh fictional situations. In an interview, you would describe assumptions aloud. Here, the prompt gives those assumptions so the answer can be checked. Separate what a component can do from what it can't promise. A cache doesn't make a stale value current, an extra API replica doesn't repair a database outage and a timestamp doesn't guarantee a unique record.