What is right-sizing, and why is over-provisioning the most common source of cloud waste?
What they are really testing: Whether you know to match resources to actual utilization using metrics, and that idle over-provisioned capacity, not exotic services, is where most money is wasted.
A real interview question
What is right-sizing, and why is over-provisioning the most common source of cloud waste?
What most people say
drag me
“Right-sizing means picking the correct instance size for your workload.”
Correct definition but no method or why. The key insight is that most waste is over-provisioned, low-utilization resources, and you fix it by looking at actual utilization metrics, continuously, not by gut feel.
The follow-ups they ask next
How do you decide a resource is over-provisioned?
Look at actual utilization metrics (CPU, memory, throughput) over a representative window. Consistently low utilization with headroom to spare means you can downsize or change instance family, keeping margin for real spikes.
Besides resizing, what other waste should you hunt for?
Zombie/orphaned resources: idle instances nobody owns, unattached storage volumes, old snapshots/backups, unused load balancers and IPs. They incur cost with zero value and are easy wins.
What the interviewer is listening for
- Match resources to real utilization
- Knows over-provisioning is the main waste
- Uses metrics, continuous, kills zombies
What sinks the answer
- Definition only, no method
- Guesses by gut
- Treats it as one-time
If you genuinely do not know
Say this instead of freezing. Reasoning out loud from what you do know beats silence every single time, and a good interviewer is listening for exactly that.
“Right-sizing is [matching resource size to actual workload demand, not guessing big]. Over-provisioning dominates waste because [teams provision for peak/safety and never revisit, so resources idle at low utilization]. Fix it with [actual CPU/memory/throughput metrics, downsize/change family with real headroom], [continuously], and [kill zombies, idle instances, unattached volumes, old snapshots].”
Keep going with cost
Foundation
What does elasticity mean in the cloud, and how does pay-as-you-go change the cost model compared to running your own servers?
Foundation
What are the main things that drive a cloud bill?
Foundation
Why is data egress (data transfer) often a hidden cost, and how do you reduce it?
Junior
Compare on-demand, committed/reserved, and spot/preemptible pricing. How do you mix them?
Junior
Why is resource tagging important for cost management?
Mid
How do autoscaling and scheduling reduce cost, and what is an easy win for non-production?
Knowing the answer is not the same as recalling it under pressure
Sign in to send the questions you fumble to spaced recall, so they come back right before you would forget them, and learn the concepts behind them with hands-on labs.
Start free