Your question is Resilient Event-Driven Microservices. 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 resilient, event-driven microservices architecture for Citi's platforms?
Explain how services communicate through events, how you would support ML data ingestion and online inference, and how the system behaves during dependency failures. Cover service boundaries, event schemas, delivery guarantees, observability, security, deployment, and recovery. State assumptions explicitly and distinguish synchronous request paths from asynchronous workflows.
