Cloud Compute Options and Trade-offs Questions

Choosing among compute abstractions independent of provider: virtual machines, containers, managed container services, serverless functions, and bare metal. Covers the cost, control, cold-start, scaling, and operational trade-offs of each model; how to pick an instance family or hardware accelerator (general-purpose, compute-optimized, memory-optimized, GPU, TPU) and a purchasing model (on-demand, reserved, spot); and how workload characteristics (latency, statefulness, burstiness) drive the decision. Managed-versus-self-managed reasoning lives here.

HardTechnical
60 practiced

Compare cost for two deployment options given this workload: 1,000,000 requests per day with a 1-hour peak at 3,000 requests per second, average execution time 200ms, and 512MB memory per serverless invocation. The alternative is a managed container platform running 3 replicas sized at 0.5 vCPU and 1GB memory each behind a load balancer. Walk through how you'd estimate monthly cost, what additional operational costs to account for, and what non-price factors would influence the final recommendation.

MediumTechnical
89 practiced

Describe the main autoscaling approaches available for cloud compute: horizontal autoscaling (of pods or instances), vertical scaling, scheduled scaling, and predictive autoscaling. For each approach, explain typical use cases, benefits, and the pitfalls it can introduce in production.

HardTechnical
69 practiced

Create a decision framework to help choose a compute option for a given workload: identify the criteria that matter and how you'd weight them, then demonstrate how you'd score and rank the options for five example workloads: a batch-processing job, a web API, a high-throughput streaming pipeline, an ML training job, and a low-latency trading system.

HardSystem Design
68 practiced

You're designing an event-driven pipeline on a serverless (FaaS) platform that must absorb sudden bursts of events. Cold-start latency and the provider's per-account concurrency limits are causing dropped or delayed processing during spikes. Design an architecture that keeps end-to-end latency low and processing reliable under these constraints, and explain how you'd validate that your design actually holds up under a realistic burst.

HardTechnical
53 practiced

For a legacy monolith currently running on VMs, compare a lift-and-shift to containers against rearchitecting to serverless microservices. For each approach, sketch a migration plan with phases, expected timelines, key risks, a testing strategy, and the metrics you'd use to decide which path to pursue.

Unlock Full Question Bank

Get access to all 40 Cloud Compute Options and Trade-offs interview questions and detailed answers.

Sign in to Continue

Join thousands of developers preparing for their dream job.