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

5 questions in DNS.

Quiz

A globally distributed API experiences a regional networking failure. How should DNS, health checks, traffic steering, connection draining, failover and consistency interact?

At 09:00 a team creates the DNS record for a new regional endpoint. It resolves from their laptops at once, but part of the fleet keeps getting NXDOMAIN until about 09:20 even though the record's TTL is 60 seconds. Why?

Why is DNS a poor primary mechanism for fast failover, and what should be used instead for a globally distributed service?

You use DNS with a 60-second TTL for regional failover. During a test, some traffic still hit the failed region 40 minutes later. Explain.

Your DR plan assumes a 60-second DNS TTL gives 60-second failover. Traffic to the failed region continues for 20 minutes. Explain and design something better.