Your question is Design Ingestion for High Volume. 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 data ingestion pipeline for a high-volume banking application?
Explain a practical architecture for ingesting transactional and operational data from APIs, databases, and event streams. Address streaming and batch ingestion, schema validation, deduplication, ordering, idempotent processing, encryption, auditability, orchestration, monitoring, failure recovery, and backfills. State the technology choices, data flow, operational SLAs, and trade-offs between latency, consistency, cost, and compliance.