SRE Cost Optimization and Cloud Resource Management

Question 1

What is 'cloud cost optimization' in the SRE context, and why is it part of SRE's responsibilities?

Accepted Answer

Cloud cost optimization ensures that infrastructure resources are right-sized and efficiently utilized, supporting reliability goals by preventing resource waste that could be invested in redundancy, monitoring, and DR capabilities

Answer

Cloud cost optimization is exclusively a finance team responsibility; SREs should focus only on reliability without considering cost implications

Answer

Cloud cost optimization means minimizing cloud spend to the absolute minimum regardless of reliability impact

Answer

Cloud cost optimization is only relevant for startups with limited budgets; large enterprises do not need to optimize cloud costs

Question 2

What is 'right-sizing' in cloud infrastructure, and what data is needed to do it effectively?

Accepted Answer

Right-sizing matches instance types and sizes to actual resource consumption by analyzing CPU, memory, and I/O utilization metrics over time, selecting the smallest instance that provides adequate headroom for peak load and scaling events

Answer

Right-sizing means always selecting the smallest available instance type to minimize cost, regardless of service performance requirements

Answer

Right-sizing is the process of ensuring all services use the same instance type for simplified management

Answer

Right-sizing is only applicable to virtual machine instances; container-based services cannot be right-sized

Question 3

What are 'reserved instances' (RIs) or 'committed use discounts' (CUDs), and when should SREs recommend them?

Accepted Answer

Reserved instances are pre-purchased cloud compute commitments (typically 1-3 years) that provide 30-70% cost savings over on-demand pricing in exchange for committing to a minimum usage level — appropriate for stable, predictable baseline workloads

Answer

Reserved instances guarantee that specific physical servers will always be available for the workload, providing stronger reliability than on-demand instances

Answer

Reserved instances are only available for the largest instance types; standard-sized instances always use on-demand pricing

Answer

Reserved instances provide no discount but ensure priority access during cloud provider capacity crunches

Question 4

What are 'spot instances' (AWS) or 'preemptible VMs' (GCP), and what type of workloads are they MOST suitable for?

Accepted Answer

Spot/preemptible instances are deeply discounted (70-90%) cloud compute that can be reclaimed by the provider with short notice; they are most suitable for fault-tolerant batch workloads like data processing, rendering, and CI/CD workers that can be safely interrupted and restarted

Answer

Spot instances are the fastest instance type available; they are suitable for latency-sensitive user-facing services

Answer

Spot instances guarantee availability for the duration of the commitment window; they are suitable for any production workload

Answer

Spot instances are only available in specific geographic regions and cannot be used for globally distributed services

Question 5

What is 'resource tagging strategy' in cloud cost management, and why is it important for SRE teams?

Accepted Answer

Resource tags (key-value pairs on cloud resources) enable cost allocation by service, team, environment, and owner — allowing SREs to identify cost anomalies, enforce accountability, and make data-driven right-sizing decisions per service

Answer

Resource tags are used by cloud providers to prioritize support tickets from enterprise customers with high spend

Answer

Resource tags are metadata labels used by monitoring systems to route alerts to the correct on-call team, not for cost purposes

Answer

Resource tagging is a compliance requirement for financial audits but provides no operational benefit to SRE teams

Question 6

What is 'idle resource detection,' and what are common examples of cloud waste it addresses?

Accepted Answer

Idle resource detection identifies cloud resources that are running but not being used, such as stopped EC2 instances with attached EBS volumes, unattached Elastic IPs, oversized databases with near-zero query load, and dev environments running 24/7

Answer

Idle resource detection is a security practice that identifies unused IAM credentials that should be rotated

Answer

Idle resource detection only applies to networking resources (load balancers, VPNs) that incur fixed hourly costs regardless of usage

Answer

Idle resource detection refers to monitoring CPU idle time to identify opportunities for vertical scaling