Quiz

2868 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 areas2868 Architecture Fundamentals91 Distributed Systems101 Data Architecture90 Cloud Architecture87 Networking86 API & Integration Architecture87 Reliability & Resilience99 Observability92 Performance & Capacity Engineering90 Security Architecture95 Cost Architecture & FinOps92 Business Architecture93 Architecture Communication102 Enterprise Architecture100 Legacy Modernization92 AI-Era Architecture96 Software Architecture & Engineering93 Architecture Patterns94 Architecture Decision-Making101 The Architect's Meta-Skills102 Delivery & Release Engineering103 Platform Engineering & Developer Experience92 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

2868 questions.

Quiz

Prices change continuously based on demand and dates. Search must filter and sort by price over millions of listings. How?

A written standard says every new service must emit structured logs with eight required fields. Twenty-six teams ship roughly 30 new services a year and about 45% comply. Which change most reduces the annual cost of this standard?

After a full review the CTO chooses an approach you argued against. You believe it will cause serious problems in eighteen months. What do you do?

An architect has no authority over the teams whose systems they are responsible for. What actually produces influence, and what destroys it?

An architect must change how several teams build without the authority to direct them. What works?

An architect must get several teams to adopt a shared approach and has no authority over any of them. What actually works?

How would you change the technical direction of a team that does not report to you and disagrees with you?

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?