A FinOps engineer says 'we have 14 rightsizing recommendations'. What does rightsizing mean?
Rightsizing means matching the resource specification to actual workload needs. If a server uses 8% of its CPU, it's over-provisioned and should be downsized to a smaller instance type — often reducing cost by 30-60%.
2 / 14
What are 'zombie instances' in cloud cost management?
Zombie instances (or 'zombie resources') are cloud assets that are still running and billing but no longer serve any purpose. Common examples: dev VMs from closed projects, detached storage volumes, idle NAT gateways, and forgotten test databases.
3 / 14
What is a 'cost anomaly alert' in AWS or cloud cost management?
Cost anomaly detection uses ML to learn your normal spend patterns and alerts you when actual costs deviate significantly — catching unexpected spikes caused by misconfigurations, runaway jobs, or billing errors before they become huge bills.
4 / 14
What does an 'S3 lifecycle policy' help optimise?
S3 lifecycle policies automate cost-saving transitions: moving objects to S3-IA after 30 days (60% cheaper), to Glacier after 90 days (much cheaper for archival), and deleting expired objects — reducing storage costs without manual intervention.
5 / 14
What does 'auto-scaling optimisation' mean from a cost perspective?
Auto-scaling optimisation from a cost perspective means tuning the scale-in behaviour: reducing the minimum instance count, shortening cooldown periods, and using scheduled scaling for predictable traffic drops — so you pay for only what you need.
6 / 14
PR Description: 'Applying a new reserved instance strategy to the API Gateway tier. Initial estimates suggest a 20% reduction in monthly spend. Please review and approve.'
During code review, which of the following best captures the *intent* behind this PR description regarding cloud cost optimization?
This question tests understanding of common phrasing in cloud cost optimization. While 'reserved instance' is *part* of the description, the core intent is highlighted by 'reducing monthly spend'. Option A is incorrect because the PR description does provide detail about the strategy. Option B misinterprets the use of 'reserved instance' – it's a *technique*, not just a component. Option D is too broad; the focus is specifically on cost reduction, and pre-purchased capacity is a key element of that.
7 / 14
PR Description: 'Applying a new reserved instance strategy to the API Gateway tier. Initial estimates suggest a 20% reduction in monthly spend. Please review and approve.'
During code review, which of the following best captures the *intent* behind this PR description regarding cloud cost optimization?
This question tests understanding of common phrasing in cloud cost optimization. While 'reserved instance' is *part* of the description, the core intent is highlighted by 'reducing monthly spend'. Option A is incorrect because the PR description does provide detail about the strategy. Option B misinterprets the use of 'reserved instance' – it's a *technique*, not just a component. Option D is too broad; the focus is specifically on cost reduction, and pre-purchased capacity is a key element of that.
8 / 14
PR Description: 'Applying a new reserved instance strategy to the API Gateway tier. Initial estimates suggest a 20% reduction in monthly spend. Please review and approve.'
During code review, which of the following best captures the *intent* behind this PR description regarding cloud cost optimization?
This question tests understanding of common phrasing in cloud cost optimization. While 'reserved instance' is *part* of the description, the core intent is highlighted by 'reducing monthly spend'. Option A is incorrect because the PR description does provide detail about the strategy. Option B misinterprets the use of 'reserved instance' – it's a *technique*, not just a component. Option D is too broad; the focus is specifically on cost reduction, and pre-purchased capacity is a key element of that.
9 / 14
PR Description: 'Applying a new reserved instance strategy to the API Gateway tier. Initial estimates suggest a 20% reduction in monthly spend. Please review and approve.'
During code review, which of the following best captures the *intent* behind this PR description regarding cloud cost optimization?
This question tests understanding of common phrasing in cloud cost optimization. While 'reserved instance' is *part* of the description, the core intent is highlighted by 'reducing monthly spend'. Option A is incorrect because the PR description does provide detail about the strategy. Option B misinterprets the use of 'reserved instance' – it's a *technique*, not just a component. Option D is too broad; the focus is specifically on cost reduction, and pre-purchased capacity is a key element of that.
10 / 14
Alex (a DevOps Engineer) sends this Slack message: 'Hey team, running some quick tests on scaling our database. Initial results show we're hitting CPU limits frequently – maybe we should consider increasing the instance size temporarily?'. What does 'hitting CPU limits' suggest in terms of cloud cost optimization?
'Hitting CPU limits' means the database server is consistently using almost all of its processing power. This usually indicates an inefficient workload or insufficient resources for the current demand – both factors contribute to higher cloud costs. The key takeaway is that scaling up *might* be a temporary solution to address this immediate problem, but a deeper investigation into the application's resource needs is still necessary.
11 / 14
You're reviewing a PR description for a new serverless function deployment. The comment reads: 'Implemented a cost allocation tag to identify this specific function as part of the 'Production - Image Processing' service. This will allow us to track spending accurately and apply targeted optimizations later.' What is the primary benefit of using cost allocation tags in cloud cost management?
Cost allocation tags are crucial for understanding *where* your cloud spend is going. By tagging resources, you can segment your spending by service, environment, or any other relevant criteria – enabling you to pinpoint areas where costs can be optimized through strategies like rightsizing or adjusting resource allocations.
12 / 14
Ben, a FinOps analyst, is presenting a report showing a spike in unexpected costs. The report highlights 'High egress traffic' as a contributing factor. What does 'egress traffic' typically refer to in the context of cloud cost optimization?
'Egress traffic' refers specifically to data leaving your cloud infrastructure. This is often a significant cost driver because most cloud providers charge for data transferred *out* of their services – this can be significantly more expensive than internal data transfer. Reducing egress by optimizing data transfers and caching strategies is a key cost-saving tactic.
13 / 14
You're reviewing a proposed change to your application architecture. The team suggests using a reserved instance for their front-end servers. Considering cloud cost optimization, what's the main advantage of utilizing a reserved instance in this scenario?
The core benefit of reserved instances is the substantial cost savings they offer. By committing to a specific instance type and term (typically one or three years), you gain access to significantly reduced hourly rates compared to paying on-demand prices. This only makes sense if your usage patterns are predictable and consistent.
14 / 14
During a standup meeting, Chloe (a cloud architect) says: 'We need to implement a strategy to automatically scale down our development environment during off-peak hours.' Which of the following best describes what she's referring to in terms of cloud cost optimization?
Chloe's statement highlights the importance of *dynamic scaling*. This involves automatically adjusting resources – in this case, reducing the size of the development environment – based on demand. This ensures you only pay for what you actually need, significantly lowering costs during periods of low activity and avoiding wasted resources.
What will I practice in "Cloud Cost Optimization 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.