Cloud scaling: vertical, horizontal, and autoscaling

What you’ll practice

Scaling isn’t just “add more servers” - it’s choosing the right approach for workload shape, cost, and reliability. You’ll work through vertical scaling limits, horizontal scaling patterns, and autoscaling behavior across common cloud architectures.

Each question uses 4 options and there’s no timer, so you can slow down and reason through trade-offs like latency vs. throughput, stateful vs. stateless design, and scaling triggers.

Common pitfalls to avoid

Many learners mix up scaling up with scaling out, or assume autoscaling automatically fixes bad architecture. This quiz highlights where bottlenecks really come from (CPU, memory, I/O, database connections) and when scaling can make things worse.

• Treating vertical scaling as “infinite” and ignoring instance size limits and downtime
• Assuming horizontal scaling works without stateless services and shared session strategy
• Confusing load balancing with autoscaling (they solve different problems)
• Using CPU-only policies when the true constraint is memory, queue depth, or I/O
• Forgetting cooldowns, warm-up time, and thrashing in autoscaling groups

How difficulty and length are balanced

Difficulty is mixed: you’ll see straightforward definitions alongside scenario-based questions that test judgment and architecture thinking. Before you start, choose your question count and difficulty to match a quick review or a deeper practice run.