Your question is Design Rate-Limiting API Gateway. 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 highly available, rate-limiting service for an API gateway handling millions of requests per second at Okta?
Focus on how you would meet strict latency and availability goals, support per-tenant and per-user policies, and keep enforcement correct under partial failures. Be explicit about data model, serving path, and how you would monitor and recover from drift, skew, or outages.