Master reserved capacity vocabulary: RIs, committed use discounts, savings plans, coverage vs utilisation rates.
0 / 14 completed
1 / 14
What is the key difference between a 'standard RI' and a 'convertible RI' on AWS?
Standard RIs offer up to 72% discount but lock you to a specific instance type. Convertible RIs offer up to 66% discount but allow exchanges to different instance families, sizes, or OS — useful when workloads evolve.
2 / 14
A FinOps report says 'we're 67% covered by reservations'. What does 'coverage rate' measure?
Coverage rate measures the proportion of eligible usage that is covered by commitments (RIs or Savings Plans). 67% coverage means 33% of usage is still paying on-demand prices, indicating an opportunity to purchase more reservations.
3 / 14
What is 'RI utilisation rate' and why does it matter?
RI utilisation rate measures how much of your committed reservation is actually being consumed. Low utilisation (e.g. 40%) means you're paying for reserved capacity that sits idle — wasted spend that should trigger rightsizing or selling unused RIs on the marketplace.
4 / 14
What is the difference between AWS 'Savings Plans' and 'Reserved Instances'?
Savings Plans offer flexibility — you commit to $/hour spend and get discounts across EC2, Fargate, and Lambda regardless of instance type or region. RIs are more rigid but can offer slightly higher discounts for stable, well-defined workloads.
5 / 14
What are 'Committed Use Discounts' on Google Cloud Platform?
GCP's Committed Use Discounts (CUDs) give up to 57% discount on Compute Engine in exchange for a 1-year or 3-year commitment to a specific amount of vCPUs and memory in a region — similar to AWS RIs but resource-based rather than instance-based.
6 / 14
Reviewer: 'The RI usage is consistently at 80%. We should consider scaling up to a larger RI size to avoid potential overage charges.'
Which of the following best describes the reviewer's concern regarding the Reserved Instance (RI) utilization?
The reviewer is highlighting a potential problem: '80% utilization' suggests that the RI isn't fully utilized. Overage charges occur when compute usage exceeds what the RI provides, meaning the application is consuming more resources than reserved. The other options are incorrect; underutilization isn't a concern in itself (though it reduces cost savings), optimization focuses on efficient use, and scaling doesn't automatically improve performance – it simply increases capacity.
7 / 14
Reviewer: 'The RI usage is consistently at 80%. We should consider scaling up to a larger RI size to avoid potential overage charges.'
Which of the following best describes the reviewer's concern regarding the Reserved Instance (RI) utilization?
The reviewer is highlighting a potential problem: '80% utilization' suggests that the RI isn't fully utilized. Overage charges occur when compute usage exceeds what the RI provides, meaning the application is consuming more resources than reserved. The other options are incorrect; underutilization isn't a concern in itself (though it reduces cost savings), optimization focuses on efficient use, and scaling doesn't automatically improve performance – it simply increases capacity.
8 / 14
Reviewer: 'The RI usage is consistently at 80%. We should consider scaling up to a larger RI size to avoid potential overage charges.'
Which of the following best describes the reviewer's concern regarding the Reserved Instance (RI) utilization?
The reviewer is highlighting a potential problem: '80% utilization' suggests that the RI isn't fully utilized. Overage charges occur when compute usage exceeds what the RI provides, meaning the application is consuming more resources than reserved. The other options are incorrect; underutilization isn't a concern in itself (though it reduces cost savings), optimization focuses on efficient use, and scaling doesn't automatically improve performance – it simply increases capacity.
9 / 14
Reviewer: 'The RI usage is consistently at 80%. We should consider scaling up to a larger RI size to avoid potential overage charges.'
Which of the following best describes the reviewer's concern regarding the Reserved Instance (RI) utilization?
The reviewer is highlighting a potential problem: '80% utilization' suggests that the RI isn't fully utilized. Overage charges occur when compute usage exceeds what the RI provides, meaning the application is consuming more resources than reserved. The other options are incorrect; underutilization isn't a concern in itself (though it reduces cost savings), optimization focuses on efficient use, and scaling doesn't automatically improve performance – it simply increases capacity.
10 / 14
Slack Message: Sarah (DevOps) sends the following message to the team channel:
`@team 'Our RI for the database tier is consistently at 65%. Should we investigate potential misconfigurations or consider increasing our commitment?'`
What does Sarah's message primarily indicate regarding Reserved Instances?
Sarah's message highlights a concern about consistently low RI utilization (65%). While below the typical 'good practice' threshold of 80%, it doesn't automatically signal a problem. A sustained low rate often indicates underutilization or an inaccurate assessment of resource requirements; simply increasing capacity without investigation could waste money.
11 / 14
PR Description: You're reviewing a pull request for a new microservice. The developer includes the following comment:
`"Using reserved instances for the database ensures predictable costs and avoids potential overage charges during peak usage."`
What is the *primary* benefit being described in this PR description?
The PR description focuses on 'cost optimization,' which is the core value proposition of Reserved Instances. While RI's do contribute to high availability and can help avoid overage charges, the *primary* benefit highlighted here is the discounted rate achieved through a committed usage term.
12 / 14
Standup Update: During the daily standup, Alex reports:
`'We've recently switched to using Reserved Instances for our application servers. Our current RI utilization is around 72%, and we're monitoring it closely.'`
What metric should Alex prioritize tracking *beyond* just the RI utilization percentage?
While tracking RI utilization (72%) is important, Alex should also focus on the *cost savings* achieved. The value of a Reserved Instance is directly tied to the difference between its committed rate and the cost of using on-demand instances. Monitoring this difference provides a clearer picture of the investment's effectiveness.
13 / 14
API Response: The following is an excerpt from a Cloud Billing API response:
`{
"resourceType": "ReservedInstance",
"usageAmount": 240,
"committedDuration": "1Year",
"discountPercentage": 60}
`
What does the 'discountPercentage' value in this API response represent?
The 'discountPercentage' indicates how much cheaper the Reserved Instance is compared to paying for on-demand instances. It's a direct measure of the cost savings achieved through the committed usage term – not a fixed fee or utilization measurement.
14 / 14
Code Review Comment: A reviewer adds this comment to a PR:
`'Consider using Savings Plans instead of Reserved Instances for this application. Savings Plans offer more flexibility and can dynamically adjust based on your usage patterns.'`
What is the *primary* advantage of Savings Plans over Reserved Instances?
The key advantage of Savings Plans over Reserved Instances lies in their dynamic scaling capability. Savings Plans adjust automatically based on your actual usage patterns, offering greater flexibility and potentially better cost optimization than the fixed-term commitment of a Reserved Instance.
What will I practice in "Reserved Capacity Planning Vocabulary Quiz"?
This is a Cloud FinOps exercise set. It walks through 14 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 14 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.