🏷️ Cloud Pricing Vocabulary
Master cloud pricing vocabulary: on-demand vs. reserved vs. spot, sustained use discounts, committed use discounts, and pricing calculators. Intermediate
0 / 22 completed
1 / 22
An architect is choosing between on-demand, reserved, and spot pricing models for a new platform.
What is on-demand pricing?
On-demand is the baseline pricing model — no commitment, maximum flexibility, highest per-unit cost.
| Model | Commitment | Discount |
|---|---|---|
| On-demand | None | — |
| Reserved/Savings | 1–3 year | 40–72% |
| Spot | None (can be interrupted) | Up to 90% |
Key vocabulary: "on-demand pricing", "pay-per-use", "no commitment", "variable workload pricing".
2 / 22
A GCP engineer mentions: "We benefit from Sustained Use Discounts on these VMs."
What is a sustained use discount?
GCP Sustained Use Discounts (SUDs) are unique: they apply automatically with no commitment required.
| Cloud provider | Auto-discount model |
|---|---|
| GCP | Sustained Use Discount — automatic, up to ~30%, no commitment needed |
| AWS | No auto-discount — must purchase RI or Savings Plan explicitly |
| Azure | Azure Hybrid Benefit (bring your own Windows/SQL license) |
GCP also offers Committed Use Discounts (CUDs) for deeper savings with a 1- or 3-year commitment. Key vocabulary: "sustained use discount", "automatic discount", "GCP pricing model", "committed use discount (CUD)", "no action required".
3 / 22
The cloud bill shows unexpectedly high inter-AZ data transfer costs.
What most commonly drives unexpected inter-AZ transfer charges in a microservices architecture?
Microservices chat is the most common and easily overlooked source of inter-AZ costs — individually tiny per request, but enormous at scale.
| Transfer path | AWS cost (approx.) |
|---|---|
| Cross-AZ (same region) | $0.01/GB each direction |
| Cross-region | $0.02/GB+ |
| Same AZ | Free |
Solutions: topology-aware routing (route to same-AZ replica), service mesh traffic management, co-locate frequently communicating services. Key vocabulary: "inter-AZ data transfer", "cross-AZ charges", "topology-aware routing", "data transfer architecture".
4 / 22
The team is evaluating a 3-year No Upfront Reserved Instance.
What does "No Upfront" mean in the context of Reserved Instance payment options?
Three payment options trade cash flow against discount depth. All three still represent a binding commitment for the full term.
| Payment option | How you pay | Discount level |
|---|---|---|
| No Upfront | Monthly payments for the full term | Lowest (of the three) |
| Partial Upfront | Upfront payment + lower monthly rate | Medium |
| All Upfront | Full payment now, nothing monthly | Maximum |
Key vocabulary: "no upfront", "partial upfront", "all upfront", "effective hourly rate", "break-even analysis".
5 / 22
The pricing calculator shows a TCO (Total Cost of Ownership) analysis comparing cloud to on-premises.
What does TCO analysis include beyond the raw cloud bill?
TCO is a complete picture of what it truly costs to run a workload — the cloud bill is only one component.
| TCO component | Often underestimated |
|---|---|
| Cloud infrastructure | Compute, storage, networking (the invoice) |
| Licensing | Managed databases, third-party SaaS tools on top of cloud |
| Operations (FTE time) | Engineering hours managing infrastructure, incident response |
| Support plan | AWS Business/Enterprise Support: 3–10% of monthly cloud spend |
| Data transfer / egress | Often forgotten until first large bill |
Key vocabulary: "total cost of ownership", "TCO calculator", "operations overhead in TCO", "cloud migration TCO", "hidden costs".
6 / 22
// Slack message from a DevOps engineer to the team
@team - Just reviewing this PR for the new API gateway deployment. The bill is showing some significant charges for 'Idle Compute' – specifically, the backend services running during off-peak hours. I'm seeing recommendations for 'Rightsizing' and exploring options like Scheduled Instances to reduce these costs. Can anyone explain what 'Idle Compute' represents and how we can proactively manage it?
Idle Compute accurately describes compute resources (like virtual machines or containers) that are running but operating at a very low utilization level – often during off-peak hours. This is the key concept behind FinOps optimization; simply powering down instances doesn't address this situation. The charge is based on the instance's configuration and uptime, even if it's not actively processing requests. Choosing options like Scheduled Instances or Rightsizing allows you to reduce these charges by scaling down resources automatically during low-demand periods.
7 / 22
'Log Costs' refer specifically to the fees associated with storing and processing log data in cloud services like CloudWatch. While data transfer costs can contribute to overall expenses, log storage itself is a significant component of these charges. The key misconception here is that it's *not* just about requests; log volume – the sheer amount of data being recorded – drives the cost. Understanding this distinction allows for proactive optimization strategies like filtering and archiving logs effectively.
8 / 22
PR Description:
During a code review of the new data processing pipeline deployment, Mark (a Developer) added this comment to the PR description:
"Looks like we're spending a lot on egress traffic. The data is moving between regions frequently. I need to understand how 'Egress Costs' are calculated and if there's a way to minimize them."
Which of the following best describes 'Egress Costs' in a cloud environment?
Egress costs specifically refer to the charges incurred when transferring data
out of a cloud provider's region and into another region or the public internet. This is different from *ingress* (data moving in), which often has lower or no associated fees. Many cloud providers charge per GB transferred, making it crucial to consider regional placement and minimize unnecessary data movement between regions during application deployment and operation. Option 'A' is incorrect because egress costs apply regardless of the service type; option 'B' describes a key definition accurately.9 / 22
// Slack message from a DevOps engineer to the team
@team - Just reviewing this PR for the new API gateway deployment. The bill is showing some significant charges for 'Idle Compute' – specifically, the backend services running during off-peak hours. I'm seeing recommendations for 'Rightsizing' and exploring options like Scheduled Instances to reduce these costs. Can anyone explain what 'Idle Compute' represents and how we can proactively manage it?
Idle Compute accurately describes compute resources (like virtual machines or containers) that are running but operating at a very low utilization level – often during off-peak hours. This is the key concept behind FinOps optimization; simply powering down instances doesn't address this situation. The charge is based on the instance's configuration and uptime, even if it's not actively processing requests. Choosing options like Scheduled Instances or Rightsizing allows you to reduce these charges by scaling down resources automatically during low-demand periods.
10 / 22
'Log Costs' refer specifically to the fees associated with storing and processing log data in cloud services like CloudWatch. While data transfer costs can contribute to overall expenses, log storage itself is a significant component of these charges. The key misconception here is that it's *not* just about requests; log volume – the sheer amount of data being recorded – drives the cost. Understanding this distinction allows for proactive optimization strategies like filtering and archiving logs effectively.
11 / 22
PR Description:
During a code review of the new data processing pipeline deployment, Mark (a Developer) added this comment to the PR description:
"Looks like we're spending a lot on egress traffic. The data is moving between regions frequently. I need to understand how 'Egress Costs' are calculated and if there's a way to minimize them."
Which of the following best describes 'Egress Costs' in a cloud environment?
Egress costs specifically refer to the charges incurred when transferring data
out of a cloud provider's region and into another region or the public internet. This is different from *ingress* (data moving in), which often has lower or no associated fees. Many cloud providers charge per GB transferred, making it crucial to consider regional placement and minimize unnecessary data movement between regions during application deployment and operation. Option 'A' is incorrect because egress costs apply regardless of the service type; option 'B' describes a key definition accurately.12 / 22
// Slack message from a DevOps engineer to the team
@team - Just reviewing this PR for the new API gateway deployment. The bill is showing some significant charges for 'Idle Compute' – specifically, the backend services running during off-peak hours. I'm seeing recommendations for 'Rightsizing' and exploring options like Scheduled Instances to reduce these costs. Can anyone explain what 'Idle Compute' represents and how we can proactively manage it?
Idle Compute accurately describes compute resources (like virtual machines or containers) that are running but operating at a very low utilization level – often during off-peak hours. This is the key concept behind FinOps optimization; simply powering down instances doesn't address this situation. The charge is based on the instance's configuration and uptime, even if it's not actively processing requests. Choosing options like Scheduled Instances or Rightsizing allows you to reduce these charges by scaling down resources automatically during low-demand periods.
13 / 22
'Log Costs' refer specifically to the fees associated with storing and processing log data in cloud services like CloudWatch. While data transfer costs can contribute to overall expenses, log storage itself is a significant component of these charges. The key misconception here is that it's *not* just about requests; log volume – the sheer amount of data being recorded – drives the cost. Understanding this distinction allows for proactive optimization strategies like filtering and archiving logs effectively.
14 / 22
PR Description:
During a code review of the new data processing pipeline deployment, Mark (a Developer) added this comment to the PR description:
"Looks like we're spending a lot on egress traffic. The data is moving between regions frequently. I need to understand how 'Egress Costs' are calculated and if there's a way to minimize them."
Which of the following best describes 'Egress Costs' in a cloud environment?
Egress costs specifically refer to the charges incurred when transferring data
out of a cloud provider's region and into another region or the public internet. This is different from *ingress* (data moving in), which often has lower or no associated fees. Many cloud providers charge per GB transferred, making it crucial to consider regional placement and minimize unnecessary data movement between regions during application deployment and operation. Option 'A' is incorrect because egress costs apply regardless of the service type; option 'B' describes a key definition accurately.15 / 22
// Slack message from a DevOps engineer to the team
@team - Just reviewing this PR for the new API gateway deployment. The bill is showing some significant charges for 'Idle Compute' – specifically, the backend services running during off-peak hours. I'm seeing recommendations for 'Rightsizing' and exploring options like Scheduled Instances to reduce these costs. Can anyone explain what 'Idle Compute' represents and how we can proactively manage it?
Idle Compute accurately describes compute resources (like virtual machines or containers) that are running but operating at a very low utilization level – often during off-peak hours. This is the key concept behind FinOps optimization; simply powering down instances doesn't address this situation. The charge is based on the instance's configuration and uptime, even if it's not actively processing requests. Choosing options like Scheduled Instances or Rightsizing allows you to reduce these charges by scaling down resources automatically during low-demand periods.
16 / 22
'Log Costs' refer specifically to the fees associated with storing and processing log data in cloud services like CloudWatch. While data transfer costs can contribute to overall expenses, log storage itself is a significant component of these charges. The key misconception here is that it's *not* just about requests; log volume – the sheer amount of data being recorded – drives the cost. Understanding this distinction allows for proactive optimization strategies like filtering and archiving logs effectively.
17 / 22
PR Description:
During a code review of the new data processing pipeline deployment, Mark (a Developer) added this comment to the PR description:
"Looks like we're spending a lot on egress traffic. The data is moving between regions frequently. I need to understand how 'Egress Costs' are calculated and if there's a way to minimize them."
Which of the following best describes 'Egress Costs' in a cloud environment?
Egress costs specifically refer to the charges incurred when transferring data
out of a cloud provider's region and into another region or the public internet. This is different from *ingress* (data moving in), which often has lower or no associated fees. Many cloud providers charge per GB transferred, making it crucial to consider regional placement and minimize unnecessary data movement between regions during application deployment and operation. Option 'A' is incorrect because egress costs apply regardless of the service type; option 'B' describes a key definition accurately.18 / 22
Reviewing a code review comment from David (a Developer): 'The bill is showing a lot of charges for 'Data Transfer Out.' We're pushing data to S3 in Region US-East-1. What does 'Data Transfer Out' primarily represent in this scenario?',
'Data Transfer Out' refers specifically to the cost of transferring data *from* a region to another. While permissions and security groups can influence costs, the core meaning here is the movement of data across geographical boundaries within AWS. It's distinct from insufficient permissions or discounts.
19 / 22
A DevOps Engineer (Emily) sends this message to the team in Slack: 'I'm seeing some unexpected costs related to our EC2 instances. The 'Reserved Instance' cost is significantly higher than predicted. What does a 'Reserved Instance' typically guarantee?',
A 'Reserved Instance' offers a significant cost reduction by committing to using an EC2 instance for a defined period (typically 1-3 years). This commitment unlocks a discounted hourly rate compared to on-demand pricing. The key is the *fixed price* over that term.
20 / 22
Mark (a Developer) writes in a PR description: 'We've optimized the data pipeline to reduce egress costs. By using Lambda functions for data transformation closer to the source, we're minimizing the amount of data transferred to our data lake. What concept is Mark primarily addressing?',
Mark is focusing on 'data locality,' which means processing data as close as possible to its source. This minimizes network traffic (egress) – a major cost factor in cloud environments – by avoiding large transfers between regions or services. It's about reducing the *amount* of data moved.
21 / 22
"Good morning, team. We're seeing a spike in CloudFront CDN costs this week. It appears we've had a significant increase in requests to our static assets from users outside of North America. What is the primary driver behind this increased CloudFront cost?",
CloudFront costs are directly tied to data transfer – specifically, the volume of data delivered to end-users. An increase in requests from outside North America signifies a higher demand for static content, which translates into more data transferred over the CDN network and therefore increased CloudFront charges. It's about *volume* of data served.
22 / 22
You're reviewing a bill for your application running on AWS Lambda. The bill includes a charge labelled 'Provisioned Concurrency'. What is the primary purpose of Provisioned Concurrency?',
Provisioned Concurrency allows you to maintain a specified number of 'warm' Lambda function instances ready to execute immediately. This avoids the delays associated with 'cold starts,' where the instance needs to be initialized from scratch each time it receives a request – it's a *fixed* cost for availability.
Frequently Asked Questions
What will I practice in "Cloud Pricing Vocabulary | Cloud FinOps Exercises"?
This is a Cloud FinOps exercise set. It walks through 22 scenario-based multiple-choice questions built around real usage of Cloud FinOps 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 22 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 FinOps 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 FinOps exercises?
See the Cloud FinOps 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 FinOps vocabulary comes up often in technical discussions and interviews. Pair this exercise with our dedicated Interview Preparation section for role-specific practice.