26. A multi-tenant service caches API responses. What tenant-isolation risks would you review?
HardApplication & data security
Technical
Show model answer
Check whether cache keys, authorization decisions, shared proxies, and invalidation preserve the owner and permission boundary. Consider users changing roles, revoked shares, and responses that must never enter a shared cache.
Use fictional cross-tenant tests for hits, misses, updates, and revocation. A correct database filter does not by itself establish that a cached response is safe for the next caller.
What interviewers listen for
- Review the full response path
- Include changing permissions
- Test cache hits across tenants