Loading...
Loading...
Browse 5 real-world technical and behavioral interview questions about Cost optimisation. Review scenarios, edge cases, and architectural best practices.
Managed service vs self-hosted decisions compare operational load, control, lock-in, availability and real cloud cost. The hidden costs are usually egress, cross-zone traffic, idle capacity and the team needed to run the component well. It also connects managed services to the point an interviewer is testing.
Measure utilisation first, because most fleets pay for idle accelerators rather than for too few. Then right-size to whatever each job is bound by, move interruptible work onto spot capacity behind tested checkpointing, and pool the fleet behind one queue instead of reserving per team.
Zombie cloud infrastructure should be detected with billing, utilization, ownership, and access signals, then quarantined before deletion so FinOps automation saves cost without destroying critical standby resources. Use this FINOPS answer to show the decision, trade-off, and evidence rather than a memorised definition. It also connects cloud infrastructure to the point an interviewer is testing.
Flat traffic and a tripled bill means cost per request tripled, so hunt what changed per request: a larger model version, more feature reads per prediction, retries multiplying calls, or warm capacity left running. Per-request cost attribution is what makes this answerable.
Decide from the task. For grounded work over your own corpus, quality is set by what reaches the context, so retrieval dominates model size and a smaller model usually suffices. Keep the larger model for long multi-step reasoning, and treat routing as a second system to evaluate and monitor.