Your question is Caching for High-Traffic Financial APIs. Take a moment with it on the right.
Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).
How would you design a caching strategy for a high-traffic financial API?
Explain which responses are safe to cache, where caches belong, how you would handle invalidation and consistency, and how you would prevent stale or unauthorized financial data from being served. Discuss reliability, observability, cost, and failure behavior. Clarify assumptions about read and write endpoints, data sensitivity, traffic patterns, and freshness requirements before proposing the design.
