Intermediate
Cloud Migration
#TCO
#cloud-economics
#rightsizing
#FinOps
TCO & Cloud Economics
5 exercises — master cloud economics vocabulary: total cost of ownership, CapEx vs OpEx, Reserved Instances / Savings Plans / Spot pricing, rightsizing, and presenting ROI and payback period to a CFO.
0 / 26 completed
1 / 26
A CFO asks: "Our on-premises data centre is fully depreciated. Running it costs us almost nothing. Why should we pay for cloud?"
How do you construct the full TCO comparison?
A fully-depreciated asset is a sunk cost. The relevant question is: what does it cost to keep running — and how does that compare to cloud?
Hidden on-premises costs (often excluded from naive comparisons):
PUE (Power Usage Effectiveness):
Ratio of total data centre power to IT equipment power. World-class hyperscaler PUE: 1.1-1.2. Typical enterprise DC: 1.6-2.0. All that overhead is pure cost with no compute value.
Stranded capacity example:
You provision 100 servers for peak load (Christmas, month-end). Average utilisation in the remaining 11 months: 18%. You are paying for 100% of those servers 100% of the time. Cloud scales to demand — you pay only for what's running.
Key vocabulary:
• TCO (Total Cost of Ownership) — all costs associated with owning and operating an asset over its useful life
• Sunk cost — a past cost that cannot be recovered; irrelevant to future decisions
• Stranded capacity — provisioned compute that is idle and paid for but delivering no business value
• PUE (Power Usage Effectiveness) — efficiency metric for data centre power overhead
Hidden on-premises costs (often excluded from naive comparisons):
| Cost category | Typical impact |
|---|---|
| Hardware refresh | Every 3-5 years; servers, storage, networking. Often ≥ initial cost. |
| Power & cooling | Typically 40-60% of hardware cost as annual overhead (PUE) |
| Physical security | Physical access controls, security staff, CCTV, cage rental |
| Stranded capacity | Avg on-prem utilisation: 15-20% of provisioned capacity |
| Operational staff | SysAdmins, storage admins, network engineers managing hardware |
| Licensing | VMware hypervisor, management tooling, OS licenses |
| DR / backup | Secondary site, tape infrastructure, backup software licensing |
PUE (Power Usage Effectiveness):
Ratio of total data centre power to IT equipment power. World-class hyperscaler PUE: 1.1-1.2. Typical enterprise DC: 1.6-2.0. All that overhead is pure cost with no compute value.
Stranded capacity example:
You provision 100 servers for peak load (Christmas, month-end). Average utilisation in the remaining 11 months: 18%. You are paying for 100% of those servers 100% of the time. Cloud scales to demand — you pay only for what's running.
Key vocabulary:
• TCO (Total Cost of Ownership) — all costs associated with owning and operating an asset over its useful life
• Sunk cost — a past cost that cannot be recovered; irrelevant to future decisions
• Stranded capacity — provisioned compute that is idle and paid for but delivering no business value
• PUE (Power Usage Effectiveness) — efficiency metric for data centre power overhead
2 / 26
Your finance director says: "I prefer CapEx to OpEx. Hardware sits on the balance sheet; cloud costs go straight to P&L and inflate our operating costs every quarter."
How do you explain the financial and strategic trade-offs?
CapEx vs OpEx involves real accounting, tax, and cash-flow differences — neither is universally "better".
CapEx (Capital Expenditure):
• Upfront large payment for long-lived assets (servers, storage, networking)
• Capitalised on balance sheet; depreciated over useful life (e.g., 5 years straight-line)
• Tax treatment: depreciation allowances taken over time, not immediately
• Cash flow: large outflow in year 0; after that, the asset is "free"
• Risk: asset obsolescence; refresh cycle locks in large future spend regardless of business needs
OpEx (Operating Expenditure) — cloud:
• Recurring monthly payment; expensed immediately against P&L
• No balance sheet asset, no depreciation schedule
• Tax treatment: fully deductible in the period incurred (faster tax benefit in many jurisdictions)
• Cash flow: smooth, predictable (with commitments) or variable (on-demand)
• Risk: "bill shock" if usage is uncontrolled; requires FinOps discipline
The CFO framing for cloud:
• Cloud frees capital that was tied up in hardware cycles — capital can be invested in product development, acquisitions, or returned to shareholders
• Variable cost model aligns IT spend to business outcomes: if revenue falls, cloud costs can scale down
• Reserved Instances (1yr/3yr commitment) can appear on balance sheet as operating leases under IFRS 16 / ASC 842 depending on audit treatment
FinOps (Cloud Financial Management):
The practice of bringing engineering, finance, and business together to manage cloud spend. Key practices: unit economics (cost per customer/transaction), showback/chargeback per team, anomaly detection, rightsizing.
Key vocabulary:
• CapEx — large upfront capital investment in long-lived assets; depreciated over time
• OpEx — recurring operational spend; expensed immediately against P&L
• Depreciation — systematic allocation of asset cost over its useful life
• FinOps — discipline of cloud financial management; treats cloud spend as a variable, optimisable cost
CapEx (Capital Expenditure):
• Upfront large payment for long-lived assets (servers, storage, networking)
• Capitalised on balance sheet; depreciated over useful life (e.g., 5 years straight-line)
• Tax treatment: depreciation allowances taken over time, not immediately
• Cash flow: large outflow in year 0; after that, the asset is "free"
• Risk: asset obsolescence; refresh cycle locks in large future spend regardless of business needs
OpEx (Operating Expenditure) — cloud:
• Recurring monthly payment; expensed immediately against P&L
• No balance sheet asset, no depreciation schedule
• Tax treatment: fully deductible in the period incurred (faster tax benefit in many jurisdictions)
• Cash flow: smooth, predictable (with commitments) or variable (on-demand)
• Risk: "bill shock" if usage is uncontrolled; requires FinOps discipline
The CFO framing for cloud:
• Cloud frees capital that was tied up in hardware cycles — capital can be invested in product development, acquisitions, or returned to shareholders
• Variable cost model aligns IT spend to business outcomes: if revenue falls, cloud costs can scale down
• Reserved Instances (1yr/3yr commitment) can appear on balance sheet as operating leases under IFRS 16 / ASC 842 depending on audit treatment
FinOps (Cloud Financial Management):
The practice of bringing engineering, finance, and business together to manage cloud spend. Key practices: unit economics (cost per customer/transaction), showback/chargeback per team, anomaly detection, rightsizing.
Key vocabulary:
• CapEx — large upfront capital investment in long-lived assets; depreciated over time
• OpEx — recurring operational spend; expensed immediately against P&L
• Depreciation — systematic allocation of asset cost over its useful life
• FinOps — discipline of cloud financial management; treats cloud spend as a variable, optimisable cost
3 / 26
An architect is sizing the cloud commitment for a large workload migration. They're evaluating On-Demand, Reserved Instances, Savings Plans, and Spot Instances.
Which pricing model fits which scenario?
Mixing all four pricing models is the optimal cloud cost strategy — each serves a different workload archetype.
Optimal strategy (blended):
• Convertible RIs — can be exchanged for different instance types within the same class; slightly lower discount than Standard RIs
• Compute Savings Plans — apply across any instance family, region, OS, enabling maximum flexibility
• EC2 Instance Savings Plans — highest discount but locked to a specific instance family and region
• Azure equivalent for RIs: Reserved VM Instances; for Spot: Azure Spot VMs with Eviction policy
Key vocabulary:
• Reserved Instance (RI) — a 1- or 3-year commitment to a specific instance type in exchange for a significant discount
• Savings Plans — flexible commitment to a $/hr spend level, applied across eligible instance types
• Spot Instance / Preemptible VM — discounted instance using spare cloud capacity; can be interrupted with minimal notice
• Blended rate — the effective hourly cost across all pricing models in your fleet
| Model | Discount | Use case | Risk |
|---|---|---|---|
| On-Demand | Baseline (0%) | Variable workloads, dev/test, spiky traffic | Most expensive; no commitment |
| Reserved Instances | 40-60% (1yr); up to 72% (3yr all-upfront) | Steady-state production workloads | Committed to specific instance family/region |
| Savings Plans | Up to 66% (Compute SP) | Baseline workloads; want instance-type flexibility | $/hr spend commitment; less flexible than On-Demand |
| Spot / Preemptible | 50-90% | Batch, ML training, big data, CI/CD | Can be reclaimed in 2 min; workload must be fault-tolerant |
Optimal strategy (blended):
Baseline steady load → Reserved Instances or Savings Plans (60-70% of total fleet) Variable peak traffic → On-Demand (auto-scaling, on top of committed baseline) Batch / analytics → Spot Instances (stateless jobs; retry on interruption)Key AWS-specific notes:
• Convertible RIs — can be exchanged for different instance types within the same class; slightly lower discount than Standard RIs
• Compute Savings Plans — apply across any instance family, region, OS, enabling maximum flexibility
• EC2 Instance Savings Plans — highest discount but locked to a specific instance family and region
• Azure equivalent for RIs: Reserved VM Instances; for Spot: Azure Spot VMs with Eviction policy
Key vocabulary:
• Reserved Instance (RI) — a 1- or 3-year commitment to a specific instance type in exchange for a significant discount
• Savings Plans — flexible commitment to a $/hr spend level, applied across eligible instance types
• Spot Instance / Preemptible VM — discounted instance using spare cloud capacity; can be interrupted with minimal notice
• Blended rate — the effective hourly cost across all pricing models in your fleet
4 / 26
The FinOps team flags that rightsizing could save 30% of the current cloud bill. A developer pushes back: "We sized these instances in production — downgrading them is risky."
What's the data-driven response?
Rightsizing is data-driven engineering, not guesswork. The concern about "risk" is valid but managed with proper tooling and process.
Why on-premises instances are typically oversized:
• When migrating ("lift-and-shift"), teams map on-prem vCPUs/RAM 1:1 to cloud — but on-prem was provisioned for peak, not average
• Average on-premises server utilisation: 15-20% of provisioned capacity
• Cloud pricing scales linearly with instance size; you pay 4x for a 4x larger instance
• Result: a workload using 4 vCPUs average running on a 16-vCPU instance wastes 75% of cost
Rightsizing tooling:
• AWS Compute Optimizer — analyses EC2, Lambda, ECS, EBS, RDS, ASG configurations using ML; provides Right-Sized, Over-Provisioned, Under-Provisioned recommendations with risk indicators
• AWS Cost Explorer Rightsizing Recommendations — simpler but less ML-driven
• Azure Advisor Cost recommendations — analyses VM utilisation and recommends resize or shutdown
• Infracost / CloudHealth / Apptio Cloudability — third-party FinOps platforms
Safe rightsizing process:
• Not selecting the smallest possible instance
• Not ignoring burst patterns and memory pressure
• Not resizing without a rollback plan
Key vocabulary:
• Rightsizing — adjusting cloud instance types/sizes to match actual workload resource demand plus safety margin
• Compute Optimizer — AWS ML-based service providing rightsizing recommendations for EC2 and other compute services
• Utilisation rate — percentage of provisioned capacity that is actively being used by the workload
• Safety margin — the buffer above measured peak utilisation to allow for traffic spikes without degradation
Why on-premises instances are typically oversized:
• When migrating ("lift-and-shift"), teams map on-prem vCPUs/RAM 1:1 to cloud — but on-prem was provisioned for peak, not average
• Average on-premises server utilisation: 15-20% of provisioned capacity
• Cloud pricing scales linearly with instance size; you pay 4x for a 4x larger instance
• Result: a workload using 4 vCPUs average running on a 16-vCPU instance wastes 75% of cost
Rightsizing tooling:
• AWS Compute Optimizer — analyses EC2, Lambda, ECS, EBS, RDS, ASG configurations using ML; provides Right-Sized, Over-Provisioned, Under-Provisioned recommendations with risk indicators
• AWS Cost Explorer Rightsizing Recommendations — simpler but less ML-driven
• Azure Advisor Cost recommendations — analyses VM utilisation and recommends resize or shutdown
• Infracost / CloudHealth / Apptio Cloudability — third-party FinOps platforms
Safe rightsizing process:
1. Observe: collect 2-4 weeks of CPU, memory, network, disk I/O metrics 2. Analyse: Compute Optimizer recommendation + safety margin (e.g., peak × 1.5) 3. Test: resize in staging → run load tests 4. Implement: resize in maintenance window, with automated rollback alarm 5. Monitor: watch for performance degradation alerts for 2 weeks post-resizeWhat rightsizing is NOT:
• Not selecting the smallest possible instance
• Not ignoring burst patterns and memory pressure
• Not resizing without a rollback plan
Key vocabulary:
• Rightsizing — adjusting cloud instance types/sizes to match actual workload resource demand plus safety margin
• Compute Optimizer — AWS ML-based service providing rightsizing recommendations for EC2 and other compute services
• Utilisation rate — percentage of provisioned capacity that is actively being used by the workload
• Safety margin — the buffer above measured peak utilisation to allow for traffic spikes without degradation
5 / 26
You need to present a cloud migration business case to a CFO and board. They want to understand: "What is our payback period and what is the 5-year ROI?"
How do you structure the financial model?
A credible CFO-ready cloud business case has three financial layers: migration investment, avoided on-prem costs, new cloud costs.
Model structure:
1. Migration cost (one-time, Year 0-1):
• Assessment and discovery tooling (e.g., AWS Migration Evaluator, Cloudamize)
• Migration tooling (AWS MGN, Database Migration Service, partner licences)
• Professional services / SI partner fees
• Internal retraining and certification
• Productivity loss during migration (teams distracted from BAU)
• Dual-run costs (running both on-prem and cloud during parallel operation — typically 3-6 months)
2. Avoided on-premises costs (starting Year 1-2):
• Hardware refresh avoided (savings is realised when the next planned refresh is cancelled)
• Data centre lease, power, cooling — prorated as accounts migrate off
• Operational staff — redeployment or reduction (be cautious; redundancy costs are real)
3. Cloud run-rate costs:
• Compute (blended On-Demand + Reserved + Spot model)
• Storage, data transfer (egress costs are real; often underestimated)
• Managed service premiums (RDS > self-managed MySQL, but operational savings offset it)
Payback period formula:
$$ ext{Payback} = rac{ ext{Total migration cost}}{ ext{Annual on-prem savings} - ext{Annual cloud cost}}$$
Typical range: 18 months to 3 years. Heavily dependent on on-prem refresh timing.
5-year ROI formula:
$$ ext{ROI} = rac{ ext{5-year net savings} - ext{Migration cost}}{ ext{Migration cost}} imes 100%$$
Typical range for well-managed migration: 30-200% depending on starting on-prem cost structure.
Common model mistakes:
• Forgetting egress costs (cloud charges for data leaving the region or cloud)
• Underestimating dual-run period costs
• Assuming 1:1 instance mapping without rightsizing (overstates cloud costs)
• Not accounting for software licensing changes (BYOL vs licence-included)
Key vocabulary:
• Payback period — time until cumulative savings offset total migration investment
• ROI (Return on Investment) — net financial benefit relative to investment, expressed as a percentage
• Dual-run cost — cost of operating both on-premises and cloud environments simultaneously during migration transition
• Egress cost — charges incurred when data is transferred out of a cloud region or to the internet
Model structure:
1. Migration cost (one-time, Year 0-1):
• Assessment and discovery tooling (e.g., AWS Migration Evaluator, Cloudamize)
• Migration tooling (AWS MGN, Database Migration Service, partner licences)
• Professional services / SI partner fees
• Internal retraining and certification
• Productivity loss during migration (teams distracted from BAU)
• Dual-run costs (running both on-prem and cloud during parallel operation — typically 3-6 months)
2. Avoided on-premises costs (starting Year 1-2):
• Hardware refresh avoided (savings is realised when the next planned refresh is cancelled)
• Data centre lease, power, cooling — prorated as accounts migrate off
• Operational staff — redeployment or reduction (be cautious; redundancy costs are real)
3. Cloud run-rate costs:
• Compute (blended On-Demand + Reserved + Spot model)
• Storage, data transfer (egress costs are real; often underestimated)
• Managed service premiums (RDS > self-managed MySQL, but operational savings offset it)
Payback period formula:
$$ ext{Payback} = rac{ ext{Total migration cost}}{ ext{Annual on-prem savings} - ext{Annual cloud cost}}$$
Typical range: 18 months to 3 years. Heavily dependent on on-prem refresh timing.
5-year ROI formula:
$$ ext{ROI} = rac{ ext{5-year net savings} - ext{Migration cost}}{ ext{Migration cost}} imes 100%$$
Typical range for well-managed migration: 30-200% depending on starting on-prem cost structure.
Common model mistakes:
• Forgetting egress costs (cloud charges for data leaving the region or cloud)
• Underestimating dual-run period costs
• Assuming 1:1 instance mapping without rightsizing (overstates cloud costs)
• Not accounting for software licensing changes (BYOL vs licence-included)
Key vocabulary:
• Payback period — time until cumulative savings offset total migration investment
• ROI (Return on Investment) — net financial benefit relative to investment, expressed as a percentage
• Dual-run cost — cost of operating both on-premises and cloud environments simultaneously during migration transition
• Egress cost — charges incurred when data is transferred out of a cloud region or to the internet
6 / 26
This question tests your understanding of a multi-faceted approach to cloud cost management beyond just instance size. While selecting smaller instances can help, it's not a complete solution; dynamic scaling (auto-scaling) is vital for responding to fluctuating workloads and avoiding over-provisioning. Monitoring and alerting are equally important for identifying inefficient usage patterns that might be missed with static sizing – failing to do so leads to wasted spend.
7 / 26
// Slack message from a DevOps engineer to the team
@team Hi everyone, just noticed our new EC2 instances are running on On-Demand pricing. While it's simple, we're seeing some significant hourly costs – especially during peak times. I've been researching Reserved Instances and Savings Plans. Any initial thoughts on whether we should explore these options to potentially reduce our overall cloud spend? Let's discuss how we can proactively manage this.This question tests understanding of proactive cost management in the cloud. While On-Demand is simple, it's rarely the most economical choice long-term. Spot Instances are volatile and unsuitable for all workloads due to potential interruptions. Reserved Instances and Savings Plans offer predictable discounts based on sustained usage – this requires a deeper dive into your workload patterns.
// The key here is understanding that 'easy' doesn't always mean 'cheapest'.8 / 26
PR Description:
Subject: EC2 Instance Cost Optimization - Initial Review
We've recently deployed several new EC2 instances using On-Demand pricing. Initial monitoring shows high hourly costs, particularly during peak usage periods. We need to investigate alternative pricing models like Reserved Instances or Savings Plans to mitigate these costs and ensure we're optimizing our cloud spend. Let's schedule a brief meeting to discuss potential strategies.
What's the most effective immediate next step for addressing this issue?The correct answer is investigating Reserved Instances or Savings Plans. While scaling down (option 1) might provide short-term relief, it lacks a strategic approach to long-term cost management. Spot Instances (option 2) introduce instability and aren't suitable for predictable workloads. Ignoring the issue (option 4) demonstrates a lack of proactive cloud financial management – the core principle of TCO analysis. Reserved Instances and Savings Plans offer predictable pricing based on committed usage, providing a more sustainable solution.
9 / 26
You're a cloud architect presenting a cost analysis to the development team after migrating a critical application to AWS. The initial On-Demand pricing has resulted in unexpectedly high hourly costs. A developer raises concerns about potential downtime if they switch to Reserved Instances or Savings Plans, citing previous issues with instance availability during planned changes. Which of the following is the MOST appropriate immediate response to address this situation and reassure the team?
Note: This scenario reflects a common challenge in cloud migration – balancing cost optimization with operational stability.
Note: This scenario reflects a common challenge in cloud migration – balancing cost optimization with operational stability.
The best approach is a phased implementation. Jumping directly to Reserved Instances could lead to service disruption if instances become unavailable during the switchover. Starting with a small subset allows for monitoring of availability while simultaneously exploring cost savings. This demonstrates a pragmatic balance between optimization and operational stability – key considerations when dealing with complex cloud migrations.
10 / 26
This question tests your understanding of a multi-faceted approach to cloud cost management beyond just instance size. While selecting smaller instances can help, it's not a complete solution; dynamic scaling (auto-scaling) is vital for responding to fluctuating workloads and avoiding over-provisioning. Monitoring and alerting are equally important for identifying inefficient usage patterns that might be missed with static sizing – failing to do so leads to wasted spend.
11 / 26
// Slack message from a DevOps engineer to the team
@team Hi everyone, just noticed our new EC2 instances are running on On-Demand pricing. While it's simple, we're seeing some significant hourly costs – especially during peak times. I've been researching Reserved Instances and Savings Plans. Any initial thoughts on whether we should explore these options to potentially reduce our overall cloud spend? Let's discuss how we can proactively manage this.This question tests understanding of proactive cost management in the cloud. While On-Demand is simple, it's rarely the most economical choice long-term. Spot Instances are volatile and unsuitable for all workloads due to potential interruptions. Reserved Instances and Savings Plans offer predictable discounts based on sustained usage – this requires a deeper dive into your workload patterns.
// The key here is understanding that 'easy' doesn't always mean 'cheapest'.12 / 26
PR Description:
Subject: EC2 Instance Cost Optimization - Initial Review
We've recently deployed several new EC2 instances using On-Demand pricing. Initial monitoring shows high hourly costs, particularly during peak usage periods. We need to investigate alternative pricing models like Reserved Instances or Savings Plans to mitigate these costs and ensure we're optimizing our cloud spend. Let's schedule a brief meeting to discuss potential strategies.
What's the most effective immediate next step for addressing this issue?The correct answer is investigating Reserved Instances or Savings Plans. While scaling down (option 1) might provide short-term relief, it lacks a strategic approach to long-term cost management. Spot Instances (option 2) introduce instability and aren't suitable for predictable workloads. Ignoring the issue (option 4) demonstrates a lack of proactive cloud financial management – the core principle of TCO analysis. Reserved Instances and Savings Plans offer predictable pricing based on committed usage, providing a more sustainable solution.
13 / 26
You're a cloud architect presenting a cost analysis to the development team after migrating a critical application to AWS. The initial On-Demand pricing has resulted in unexpectedly high hourly costs. A developer raises concerns about potential downtime if they switch to Reserved Instances or Savings Plans, citing previous issues with instance availability during planned changes. Which of the following is the MOST appropriate immediate response to address this situation and reassure the team?
Note: This scenario reflects a common challenge in cloud migration – balancing cost optimization with operational stability.
Note: This scenario reflects a common challenge in cloud migration – balancing cost optimization with operational stability.
The best approach is a phased implementation. Jumping directly to Reserved Instances could lead to service disruption if instances become unavailable during the switchover. Starting with a small subset allows for monitoring of availability while simultaneously exploring cost savings. This demonstrates a pragmatic balance between optimization and operational stability – key considerations when dealing with complex cloud migrations.
14 / 26
This question tests your understanding of a multi-faceted approach to cloud cost management beyond just instance size. While selecting smaller instances can help, it's not a complete solution; dynamic scaling (auto-scaling) is vital for responding to fluctuating workloads and avoiding over-provisioning. Monitoring and alerting are equally important for identifying inefficient usage patterns that might be missed with static sizing – failing to do so leads to wasted spend.
15 / 26
// Slack message from a DevOps engineer to the team
@team Hi everyone, just noticed our new EC2 instances are running on On-Demand pricing. While it's simple, we're seeing some significant hourly costs – especially during peak times. I've been researching Reserved Instances and Savings Plans. Any initial thoughts on whether we should explore these options to potentially reduce our overall cloud spend? Let's discuss how we can proactively manage this.This question tests understanding of proactive cost management in the cloud. While On-Demand is simple, it's rarely the most economical choice long-term. Spot Instances are volatile and unsuitable for all workloads due to potential interruptions. Reserved Instances and Savings Plans offer predictable discounts based on sustained usage – this requires a deeper dive into your workload patterns.
// The key here is understanding that 'easy' doesn't always mean 'cheapest'.16 / 26
PR Description:
Subject: EC2 Instance Cost Optimization - Initial Review
We've recently deployed several new EC2 instances using On-Demand pricing. Initial monitoring shows high hourly costs, particularly during peak usage periods. We need to investigate alternative pricing models like Reserved Instances or Savings Plans to mitigate these costs and ensure we're optimizing our cloud spend. Let's schedule a brief meeting to discuss potential strategies.
What's the most effective immediate next step for addressing this issue?The correct answer is investigating Reserved Instances or Savings Plans. While scaling down (option 1) might provide short-term relief, it lacks a strategic approach to long-term cost management. Spot Instances (option 2) introduce instability and aren't suitable for predictable workloads. Ignoring the issue (option 4) demonstrates a lack of proactive cloud financial management – the core principle of TCO analysis. Reserved Instances and Savings Plans offer predictable pricing based on committed usage, providing a more sustainable solution.
17 / 26
You're a cloud architect presenting a cost analysis to the development team after migrating a critical application to AWS. The initial On-Demand pricing has resulted in unexpectedly high hourly costs. A developer raises concerns about potential downtime if they switch to Reserved Instances or Savings Plans, citing previous issues with instance availability during planned changes. Which of the following is the MOST appropriate immediate response to address this situation and reassure the team?
Note: This scenario reflects a common challenge in cloud migration – balancing cost optimization with operational stability.
Note: This scenario reflects a common challenge in cloud migration – balancing cost optimization with operational stability.
The best approach is a phased implementation. Jumping directly to Reserved Instances could lead to service disruption if instances become unavailable during the switchover. Starting with a small subset allows for monitoring of availability while simultaneously exploring cost savings. This demonstrates a pragmatic balance between optimization and operational stability – key considerations when dealing with complex cloud migrations.
18 / 26
This question tests your understanding of a multi-faceted approach to cloud cost management beyond just instance size. While selecting smaller instances can help, it's not a complete solution; dynamic scaling (auto-scaling) is vital for responding to fluctuating workloads and avoiding over-provisioning. Monitoring and alerting are equally important for identifying inefficient usage patterns that might be missed with static sizing – failing to do so leads to wasted spend.
19 / 26
// Slack message from a DevOps engineer to the team
@team Hi everyone, just noticed our new EC2 instances are running on On-Demand pricing. While it's simple, we're seeing some significant hourly costs – especially during peak times. I've been researching Reserved Instances and Savings Plans. Any initial thoughts on whether we should explore these options to potentially reduce our overall cloud spend? Let's discuss how we can proactively manage this.This question tests understanding of proactive cost management in the cloud. While On-Demand is simple, it's rarely the most economical choice long-term. Spot Instances are volatile and unsuitable for all workloads due to potential interruptions. Reserved Instances and Savings Plans offer predictable discounts based on sustained usage – this requires a deeper dive into your workload patterns.
// The key here is understanding that 'easy' doesn't always mean 'cheapest'.20 / 26
PR Description:
Subject: EC2 Instance Cost Optimization - Initial Review
We've recently deployed several new EC2 instances using On-Demand pricing. Initial monitoring shows high hourly costs, particularly during peak usage periods. We need to investigate alternative pricing models like Reserved Instances or Savings Plans to mitigate these costs and ensure we're optimizing our cloud spend. Let's schedule a brief meeting to discuss potential strategies.
What's the most effective immediate next step for addressing this issue?The correct answer is investigating Reserved Instances or Savings Plans. While scaling down (option 1) might provide short-term relief, it lacks a strategic approach to long-term cost management. Spot Instances (option 2) introduce instability and aren't suitable for predictable workloads. Ignoring the issue (option 4) demonstrates a lack of proactive cloud financial management – the core principle of TCO analysis. Reserved Instances and Savings Plans offer predictable pricing based on committed usage, providing a more sustainable solution.
21 / 26
You're a cloud architect presenting a cost analysis to the development team after migrating a critical application to AWS. The initial On-Demand pricing has resulted in unexpectedly high hourly costs. A developer raises concerns about potential downtime if they switch to Reserved Instances or Savings Plans, citing previous issues with instance availability during planned changes. Which of the following is the MOST appropriate immediate response to address this situation and reassure the team?
Note: This scenario reflects a common challenge in cloud migration – balancing cost optimization with operational stability.
Note: This scenario reflects a common challenge in cloud migration – balancing cost optimization with operational stability.
The best approach is a phased implementation. Jumping directly to Reserved Instances could lead to service disruption if instances become unavailable during the switchover. Starting with a small subset allows for monitoring of availability while simultaneously exploring cost savings. This demonstrates a pragmatic balance between optimization and operational stability – key considerations when dealing with complex cloud migrations.
22 / 26
During a code review of a new Terraform script provisioning EC2 instances for a web application, your team lead comments: 'This configuration uses On-Demand pricing. To minimize costs, we should consider using Reserved Instances for predictable workloads. What's the primary benefit of utilizing Reserved Instances in this scenario?'
Reserved Instances offer substantial discounts (typically 70%) compared to On-Demand pricing when you commit to a specific instance type and term length. This is ideal for predictable workloads like web applications with consistent traffic patterns. The key benefit isn't just flexibility; it's the cost savings achieved through commitment. Option A is incorrect because size impacts utilization, not the pricing model itself.
23 / 26
A DevOps engineer sends a Slack message to the team: 'We've noticed our new Lambda functions are being billed at $0.20 per million requests. This is higher than anticipated. What's the most immediate action we should take to investigate and potentially reduce these costs?'
While scaling might seem intuitive, it doesn't address the root cause of the high cost. The $0.20/million requests figure suggests an inefficiency – perhaps excessive function execution or unnecessary data transfer. Analyzing invocation patterns and request frequency is crucial to pinpointing bottlenecks and optimizing code for performance. Option A is incorrect as simply scaling will not solve underlying inefficiencies.
24 / 26
You're writing a PR description for a change that implements cost monitoring alerts for EC2 instances using AWS CloudWatch. The description should clearly state the purpose of the change and how it contributes to TCO optimization. Which of the following best reflects this description?
A clear PR description should focus on the *outcome* – proactive cost management. Saying that CloudWatch alarms will trigger an alarm is more informative than simply stating a metric being tracked. The change's purpose is to proactively manage costs and prevent overspending. Option A focuses solely on a single metric, while options B, C, and D describe actions rather than the core functionality.
25 / 26
"During today's stand-up, our team lead asks: 'Regarding the recent migration to the cloud, are we tracking Total Cost of Ownership (TCO)? What metrics are we using to compare on-premises costs with our cloud expenses?' How should you respond to this question concisely and accurately?"
A comprehensive TCO analysis goes beyond just EC2 instance costs. It includes storage, networking, software licensing, and other operational expenses. Tracking all these factors provides a realistic comparison between on-premises and cloud environments, enabling informed decisions about resource allocation and optimization. Option A is too narrow; it only considers one component of TCO.
26 / 26
You receive the following API response from an AWS Cost Explorer endpoint, detailing the cost breakdown for a specific service:
{
"Widget": {
"TotalAmount": 123.45,
"ItemizedCosts": [
{"Resource":"EC2", "Amount": 80.00},
{"Resource":"S3", "Amount": 30.00}
]
}
What does this response primarily indicate regarding cost optimization?The response clearly shows that EC2 instances account for $80.00 out of a total $123.45. This indicates that optimizing EC2 instance usage (e.g., right-sizing, using reserved instances) would likely have the most significant impact on reducing costs. While S3 is also contributing ($30.00), the higher cost from EC2 suggests it's the primary area for optimization.
Frequently Asked Questions
What will I practice in "TCO & Cloud Economics — Cloud Migration Language Exercises"?
This is a Cloud Migration Language exercise set. It walks through 26 scenario-based multiple-choice questions built around real usage of Cloud Migration Language terminology that IT professionals encounter on the job.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to complete with no account, sign-up, or paywall.
How many questions are in this exercise?
This set contains 26 questions. Each one shows immediate feedback and a detailed explanation after you answer, so you learn the correct usage right away rather than waiting for a final score.
Do I need prior experience to complete this exercise?
No prior experience is required. Each question includes a full explanation covering the reasoning behind the correct answer, so the exercise itself teaches the Cloud Migration Language vocabulary as you go.
Can I retry the exercise if I get questions wrong?
Yes — use the "Try again" button on the results screen to reset your answers and go through all the questions again. There is no limit on attempts.
Is my progress saved?
Your answers and score for the current session are tracked in the browser as you go. No account or login is needed, and there is nothing to install.
What if I don't understand a term used in a question?
Read the explanation shown after you answer each question — it breaks down the correct term in plain English with a real-world example. You can also check the site Glossary for quick definitions.
How is this different from reading a blog article on the topic?
Exercises like this one are interactive drills that test and reinforce specific vocabulary through multiple-choice questions, while blog articles explain concepts in prose. Practising here after reading builds active recall, not just passive recognition.
Where can I find more Cloud Migration Language exercises?
See the Cloud Migration Language exercises hub for the full set of related pages, or browse all exercise categories from the main Exercises index.
Can I use this exercise to prepare for a technical interview?
Yes — Cloud Migration Language vocabulary comes up often in technical discussions and interviews. Pair this exercise with our dedicated Interview Preparation section for role-specific practice.