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

87 questions in Cloud Architecture.

Quiz

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 moves request signing from one region to an edge platform. p50 falls from 140 ms to 35 ms and p99 rises from 220 ms to 900 ms. Error rate is unchanged and the platform reports no throttling. Which mechanism most likely explains the tail?

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 platform manages infrastructure with code, but engineers make emergency console changes during incidents that are never reflected back. What problems does this drift cause, and how should it be handled without blocking incident response?

During an incident an engineer makes a manual change in the cloud console. It resolves the issue. What should happen next and what should have prevented it?

Half your production changes are made through the console during incidents. The IaC repository no longer matches reality. What do you do?

Infrastructure is defined as code, but production has drifted from the definitions through manual incident fixes. How should drift be handled, and what is wrong with simply enforcing the code?