Quiz

2988 questions of the kind that actually get asked — in interviews, in architecture review boards, and by the person who has to run the thing at 3 AM. Every answer states the trade-off rather than the slogan, and says when the obvious choice is the wrong one.

All areas2988 Architecture Fundamentals91 Distributed Systems111 Data Architecture100 Cloud Architecture97 Networking96 API & Integration Architecture97 Reliability & Resilience99 Observability92 Performance & Capacity Engineering100 Security Architecture105 Cost Architecture & FinOps102 Business Architecture103 Architecture Communication102 Enterprise Architecture100 Legacy Modernization102 AI-Era Architecture106 Software Architecture & Engineering93 Architecture Patterns94 Architecture Decision-Making101 The Architect's Meta-Skills102 Delivery & Release Engineering103 Platform Engineering & Developer Experience102 Testing & Quality Architecture102 Data Platform Architecture98 Streaming & Real-Time Data103 Data Governance & Semantics91 Frontend & Experience Architecture101 Edge, Mobile & IoT98 Regulatory & Data Protection Architecture99 Assurance, Audit & Model Risk98

Difficulty Any beginner intermediate advanced

4 questions in Workflow Schedulers.

Quiz

An interviewer says - we run one orchestrator with about 4,000 tasks a night, all written by the platform team. Leadership wants to open it to 12 product teams as self-service so they stop queueing behind us. Where do you take this?

Every task in the data platform sits in a queued state. Worker CPU is around 6%, the metadata database is healthy, the task logs show nothing, and no task has failed. Someone proposes adding workers. What do you look at first, and what is probably happening?

What should be evaluated when choosing a workflow scheduler for a data platform?

Why is cron insufficient for a pipeline of interdependent data jobs?