PR Title: Fix: Improved logging for API Gateway
During the code review, your teammate, Sarah, comments: "This change introduces a new Lambda function that handles requests to our API Gateway. It seems like we should be adding cost tracking for this specific component. I'm not sure if we're accounting for its usage in our FinOps reporting."
Which of the following best describes what Sarah is referring to, within the context of FinOps?
Sarah's comment highlights the importance of granular cost tracking within FinOps. While AWS provides some automated cost aggregation, truly understanding and optimizing cloud spend requires visibility into the usage patterns of individual services like Lambda functions. Tracking these components allows for targeted optimization efforts, such as right-sizing or identifying inefficient configurations – a core principle of FinOps. Option A is incorrect because it oversimplifies AWS's tracking capabilities; options C and D misrepresent the level of detail needed for effective FinOps analysis.
7 / 14
PR Title: Fix: Improved logging for API Gateway
During the code review, your teammate, Sarah, comments: "This change introduces a new Lambda function that handles requests to our API Gateway. It seems like we should be adding cost tracking for this specific component. I'm not sure if we're accounting for its usage in our FinOps reporting."
Which of the following best describes what Sarah is referring to, within the context of FinOps?
Sarah's comment highlights the importance of granular cost tracking within FinOps. While AWS provides some automated cost aggregation, truly understanding and optimizing cloud spend requires visibility into the usage patterns of individual services like Lambda functions. Tracking these components allows for targeted optimization efforts, such as right-sizing or identifying inefficient configurations – a core principle of FinOps. Option A is incorrect because it oversimplifies AWS's tracking capabilities; options C and D misrepresent the level of detail needed for effective FinOps analysis.
8 / 14
PR Title: Fix: Improved logging for API Gateway
During the code review, your teammate, Sarah, comments: "This change introduces a new Lambda function that handles requests to our API Gateway. It seems like we should be adding cost tracking for this specific component. I'm not sure if we're accounting for its usage in our FinOps reporting."
Which of the following best describes what Sarah is referring to, within the context of FinOps?
Sarah's comment highlights the importance of granular cost tracking within FinOps. While AWS provides some automated cost aggregation, truly understanding and optimizing cloud spend requires visibility into the usage patterns of individual services like Lambda functions. Tracking these components allows for targeted optimization efforts, such as right-sizing or identifying inefficient configurations – a core principle of FinOps. Option A is incorrect because it oversimplifies AWS's tracking capabilities; options C and D misrepresent the level of detail needed for effective FinOps analysis.
9 / 14
PR Title: Fix: Improved logging for API Gateway
During the code review, your teammate, Sarah, comments: "This change introduces a new Lambda function that handles requests to our API Gateway. It seems like we should be adding cost tracking for this specific component. I'm not sure if we're accounting for its usage in our FinOps reporting."
Which of the following best describes what Sarah is referring to, within the context of FinOps?
Sarah's comment highlights the importance of granular cost tracking within FinOps. While AWS provides some automated cost aggregation, truly understanding and optimizing cloud spend requires visibility into the usage patterns of individual services like Lambda functions. Tracking these components allows for targeted optimization efforts, such as right-sizing or identifying inefficient configurations – a core principle of FinOps. Option A is incorrect because it oversimplifies AWS's tracking capabilities; options C and D misrepresent the level of detail needed for effective FinOps analysis.
10 / 14
David (Senior FinOps Engineer) sends a Slack message: 'I'm seeing a lot of unpredictable spikes in our EC2 costs. We need to investigate whether we're over-provisioning instances or if there are unexpected usage patterns.' What does 'over-provisioning' likely refer to in this context?
Over-provisioning in cloud FinOps means assigning more resources (like EC2 instances) than are currently required. This leads to wasted spending because the resources remain idle or underutilized. Options B and C describe different cost optimization strategies, but aren't directly 'over-provisioning'. Option D relates to reserved instances which is a specific cost reduction technique.
11 / 14
Elena (Lead Developer) writes in a PR description: 'This change adds detailed logging around our API Gateway calls. We're now able to track the number of requests, response times, and error rates for each endpoint.' What is the primary benefit of this type of logging from a FinOps perspective?
Detailed logging around API Gateway calls allows FinOps teams to analyze request volume, response times, and error rates. This data is crucial for identifying cost drivers – such as slow endpoints or high error rates that might indicate inefficient code or excessive resource consumption. While performance and security are important, the core benefit here is cost analysis.
12 / 14
Mark (FinOps Analyst) notices a significant increase in Lambda function execution time during peak hours. He's investigating potential causes. Which of the following is *most* directly relevant to FinOps when analyzing this situation?
Lambda function execution time is a *direct* driver of cloud cost. Longer executions consume more compute resources (and therefore cost more). While user concurrency and code versions are relevant to overall application performance, they don't directly quantify the financial impact of Lambda execution duration. Option A is irrelevant to the core FinOps problem.
13 / 14
Jessica (Engineering Manager) asks her team to provide a 'showback' report for their projects. What does 'showback' mean in the context of FinOps?
'Showback' reporting is a key FinOps practice where cloud costs are directly allocated to the teams or projects that consume them. This transparency empowers teams to take ownership of their spending and identify opportunities for optimization. It's fundamentally about accountability – understanding *who* is responsible for *what* cost.
14 / 14
Tom (FinOps Consultant) presents a report to the client. The report highlights that 80% of their cloud spend is on DynamoDB storage. What's the MOST immediate action the team should consider based on this information?
While scaling instances might be a solution in some cases, the most critical first step is to investigate *why* so much cost is being incurred on DynamoDB storage. It's likely due to inefficient usage patterns – such as storing large amounts of data that isn't actively accessed or failing to implement lifecycle policies that automatically delete old data. This analysis will uncover potential optimizations before considering scaling.
What will I practice in "FinOps Vocabulary | Cloud FinOps Exercises"?
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.