Infrastructure Scaling, Capacity Planning, and High Availability Questions
How to make running infrastructure scale and stay available: the operational and architectural mechanics of doing it, not the growth-modeling math behind it. Covers autoscaling policy design and Kubernetes cluster scaling (target-tracking, step, scheduled, and predictive triggers, cooldowns, warm pools, HPA, VPA, Cluster Autoscaler, GPU/node scheduling, bin-packing), load balancing algorithms and architecture (round-robin, least-connections, consistent hashing, L4 vs L7, health checks, connection draining, session affinity), horizontal versus vertical scaling choices, and high-availability and redundancy design (multi-AZ and multi-region failover, active-active vs active-passive, split-brain and leader election). Also covers turning a given demand or growth figure into concrete provisioning: headroom and safety-margin sizing, back-of-envelope instance, IOPS, and replica-count math, right-sizing, and multi-year procurement planning; validating a sizing or scaling change through load, stress, soak, and chaos testing; scaling stateful tiers such as databases, caches, and message queues; cost-aware trade-offs including reserved versus spot capacity and managed versus self-hosted infrastructure; and the observability needed to catch capacity saturation before it breaches an SLO.
You are the data engineering lead on-call: capacity forecasts were wrong, and resource exhaustion is causing degraded analytics and SLA violations. Walk through a structured incident response: immediate mitigation steps to restore critical functionality, coordination and communication with SRE/product/finance, temporary vs long-term fixes, a plan for root-cause analysis, and governance changes you would propose to prevent future forecasting failures.
You are responsible for a 3-5 year capacity roadmap for a data platform that currently handles 10K DAUs and is expected to grow to 10M DAUs. The architecture includes Kafka ingestion, a nearline processing layer (Spark/Flink), an object data lake, and an analytics warehouse. Produce a high-level roadmap that lists growth assumptions, capacity inflection points, when and why to introduce structural changes (e.g., sharded Kafka clusters, hot/cold storage separation, regionalization), staffing and budget implications, and risk mitigation strategies.
Differentiate capacity planning from cost optimization in cloud infrastructure. Provide three concrete examples where improving capacity efficiency (right-sizing, spot capacity, scheduling) reduces cost without negatively impacting application performance.
Compare managed cloud services (for example RDS, managed Kubernetes) with self-hosted alternatives for capacity planning and scaling. List operational, financial, scaling speed, reliability, and compliance trade-offs, and provide two scenarios: one where managed services are preferable and one where self-hosted is preferable.
How would you translate a business projection of 30% year-over-year active user growth into a 3-5 year capacity roadmap for network infrastructure? Explain the assumptions you would document, how you would build in scenario planning for growth uncertainty, procurement cadence for circuits and appliances, capacity headroom targets, and how you would communicate uncertainty and contingencies to leadership.
Unlock Full Question Bank
Get access to all 33 Infrastructure Scaling, Capacity Planning, and High Availability interview questions and detailed answers.
Sign in to ContinueJoin thousands of developers preparing for their dream job.