Quiz

2667 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 areas2667 Architecture Fundamentals81 Distributed Systems101 Data Architecture90 Cloud Architecture87 Networking86 API & Integration Architecture78 Reliability & Resilience88 Observability81 Performance & Capacity Engineering90 Security Architecture95 Cost Architecture & FinOps92 Business Architecture93 Architecture Communication91 Enterprise Architecture91 Legacy Modernization92 AI-Era Architecture86 Software Architecture & Engineering84 Architecture Patterns84 Architecture Decision-Making91 The Architect's Meta-Skills92 Delivery & Release Engineering93 Platform Engineering & Developer Experience92 Testing & Quality Architecture90 Data Platform Architecture88 Streaming & Real-Time Data93 Data Governance & Semantics81 Frontend & Experience Architecture91 Edge, Mobile & IoT88 Regulatory & Data Protection Architecture90 Assurance, Audit & Model Risk88

Difficulty Any beginner intermediate advanced

53 questions in Cloud Architecture.

Quiz

A compute platform schedules GPU jobs with execution times ranging from minutes to weeks, where large jobs need many co-located accelerators. What happens if the scheduler uses simple first-come-first-served with best-fit packing?

A device-testing platform receives a burst of tens of thousands of test sessions after a major framework release. How should queues, worker pools, concurrency limits, resource classes, scheduling fairness and backpressure prevent capacity exhaustion?

A developer platform receives thousands of simultaneous builds after a popular framework release. How should build queues, worker pools, priority scheduling, concurrency limits, caching and backpressure prevent capacity collapse?

A developer-tools company runs enormous numbers of short-lived build and test containers where startup time dominates total runtime. Which container strategy decisions matter most?

An organisation with eight services and four engineers proposes adopting Kubernetes. Make the case against, then name what would change your mind.

A team proposes moving personalisation to edge functions to cut latency. When does that work and when does it backfire?

An e-commerce product page has cacheable content, a personalised recommendation strip, a logged-in header and a live stock indicator. What runs at the edge and where does each piece of state live?

Walk me through this one. An executive has read that a delivery network runs more than four thousand points of presence and wants product personalisation moved to the edge this quarter. You have fifteen minutes with them. What do you establish and what do you refuse?

Which workloads genuinely belong at the edge, and which become harder there because of state, consistency, debugging or resource limits?

A commerce platform runs many teams' services on Kubernetes and must survive flash-sale traffic without one team's workload harming another. What cluster and tenancy design should it use?

A latency-sensitive service shows periodic latency spikes. CPU utilisation on the node is 40%. What do you check first?

One service restarts unpredictably; another is slow with low CPU. Both run on Kubernetes. What are you looking at?