Portfolio ↗

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

4 questions in Load Balancing.

  1. Load Balancing intermediate

    A live-learning platform expects a synchronised audience for a single scheduled class. How should video delivery, interactive features, enrolment and notifications be architected differently from each other?

    2 min answer unacademylive-videocdnfan-out
  2. Load Balancing intermediate Multiple choice

    A mobility platform must route API traffic, long-lived driver location streams and internal service calls. Which load-balancing layer suits each, and what breaks if one choice is applied uniformly?

    2 min answer load-balancinglayer4layer7websockets
  3. Load Balancing intermediate

    At 11:40 autoscaling adds 20 instances to a 40-instance fleet as request rate doubles. By 11:43 p99 has gone from 300 ms to 7 s with a 4% error rate while average CPU across the fleet is 35%. By 11:55 nothing has been changed and p99 is back to 320 ms. What failed and which configuration decision made it possible?

    2 min answer cloud-load-balancingautoscalingslow-starttail-latency
  4. Load Balancing intermediate

    Every deployment produces a small spike of 502s that the team has learned to ignore. Fix it.

    2 min answer drainingdeploymentgraceful-shutdown