Cloud Abbreviations
5 exercises — IaaS/PaaS/SaaS/FaaS/CaaS service models, SLA vs. SLO vs. SLI, CDN edge caching, and spot instance tradeoffs.
0 / 25 completed
1 / 25
A vendor comparison table lists "IaaS, PaaS, and SaaS" as three cloud service models. What do these three abbreviations mean, and how do they differ?
IaaS / PaaS / SaaS describe an increasing level of abstraction, and correspondingly, decreasing responsibility for the customer. The standard way to remember it: as you move from IaaS to SaaS, you manage less and the provider manages more. Each layer builds on the one below it — a SaaS product is typically built on top of PaaS or IaaS infrastructure that the vendor manages internally.
These abbreviations are foundational vocabulary for describing any cloud architecture decision — "should we run this ourselves on IaaS, or use a managed PaaS" is one of the most common early architecture conversations in any project.
These abbreviations are foundational vocabulary for describing any cloud architecture decision — "should we run this ourselves on IaaS, or use a managed PaaS" is one of the most common early architecture conversations in any project.
2 / 25
A newer term appears in a serverless architecture discussion: "FaaS" and "CaaS". How do these relate to the more familiar IaaS/PaaS/SaaS model?
FaaS (Function as a Service) is the technical foundation of "serverless" computing — you write a single function, it runs only when triggered (an HTTP request, a queue message, a scheduled event), scales automatically, and you're billed per invocation/execution time rather than for an always-running server.
CaaS (Container as a Service) gives you the flexibility of packaging your app as a container (more control than FaaS, since you're not limited to a single function's execution model) without managing the underlying servers or orchestration cluster yourself.
Recognising the full family — IaaS, PaaS, SaaS, FaaS, CaaS — and correctly slotting a new product announcement into the right category ("is this FaaS or PaaS?") is a common technical vocabulary test in architecture discussions and cloud certification exams alike.
CaaS (Container as a Service) gives you the flexibility of packaging your app as a container (more control than FaaS, since you're not limited to a single function's execution model) without managing the underlying servers or orchestration cluster yourself.
Recognising the full family — IaaS, PaaS, SaaS, FaaS, CaaS — and correctly slotting a new product announcement into the right category ("is this FaaS or PaaS?") is a common technical vocabulary test in architecture discussions and cloud certification exams alike.
3 / 25
A support ticket references "our SLA guarantees 99.95% uptime." What does SLA stand for, and how does this relate to the terms "SLO" and "SLI" that often appear alongside it?
SLA / SLO / SLI form a related trio that's frequently tested and frequently confused. The relationship, from most to least formal:
• SLA (Service Level Agreement) — an external, often contractual commitment made to customers, typically with defined consequences (service credits, refunds) if breached
• SLO (Service Level Objective) — an internal target the engineering team holds itself to, usually set stricter than the SLA to provide a safety margin before actually breaching the customer-facing commitment
• SLI (Service Level Indicator) — the actual, concrete measurement (e.g. "percentage of requests completed under 200ms," "percentage of successful requests") used to determine whether the SLO/SLA is currently being met
Memory aid: Agreement (external, legal) → Objective (internal, target) → Indicator (measured, real number) — moving from the most formal/external to the most concrete/measurable.
• SLA (Service Level Agreement) — an external, often contractual commitment made to customers, typically with defined consequences (service credits, refunds) if breached
• SLO (Service Level Objective) — an internal target the engineering team holds itself to, usually set stricter than the SLA to provide a safety margin before actually breaching the customer-facing commitment
• SLI (Service Level Indicator) — the actual, concrete measurement (e.g. "percentage of requests completed under 200ms," "percentage of successful requests") used to determine whether the SLO/SLA is currently being met
Memory aid: Agreement (external, legal) → Objective (internal, target) → Indicator (measured, real number) — moving from the most formal/external to the most concrete/measurable.
4 / 25
A content delivery discussion mentions "using a CDN to reduce latency for users in different regions." What does CDN stand for, and why does it reduce latency specifically?
CDN (Content Delivery Network) works by caching content (static files, images, sometimes API responses) at many "edge" locations around the world. When a user requests content, it's served from the nearest edge server rather than travelling all the way to a single origin server, which directly reduces round-trip network latency — the physical distance data has to travel is often the dominant factor in perceived load time for geographically distant users.
Related vocabulary commonly paired with CDN: edge location (a CDN's regional server), cache hit/miss (whether content was already cached at that edge location or had to be fetched from origin), origin server (the source server the CDN pulls from when content isn't cached), TTL (Time To Live) (how long cached content is considered valid before the CDN re-fetches it from origin).
Related vocabulary commonly paired with CDN: edge location (a CDN's regional server), cache hit/miss (whether content was already cached at that edge location or had to be fetched from origin), origin server (the source server the CDN pulls from when content isn't cached), TTL (Time To Live) (how long cached content is considered valid before the CDN re-fetches it from origin).
5 / 25
A cloud cost-optimisation discussion mentions "moving to spot instances could reduce our EC2 costs" alongside "we should check our SLA before switching." How would you explain the tradeoff being discussed?
This scenario tests whether you can connect two separate abbreviations (spot instances aren't technically an abbreviation, but the cost-vs-reliability tradeoff vocabulary and the SLA concept) into a coherent architecture decision — a common real-world pattern in cloud cost conversations.
Spot instances (AWS terminology; other clouds use similar concepts like "preemptible VMs" on GCP) offer significant discounts (often 60-90% off on-demand pricing) in exchange for the provider's right to reclaim the capacity with short notice when it's needed elsewhere.
Why the SLA connection matters: if a workload is running under a customer-facing SLA promising high availability, running it entirely on interruptible spot instances without a fallback strategy risks breaching that SLA when instances are reclaimed. The mature approach — often described as a mixed fleet — runs a baseline of on-demand (or reserved) instances to guarantee SLA-covered capacity, supplemented by spot instances for the elastic, interruption-tolerant portion of the workload.
Spot instances (AWS terminology; other clouds use similar concepts like "preemptible VMs" on GCP) offer significant discounts (often 60-90% off on-demand pricing) in exchange for the provider's right to reclaim the capacity with short notice when it's needed elsewhere.
Why the SLA connection matters: if a workload is running under a customer-facing SLA promising high availability, running it entirely on interruptible spot instances without a fallback strategy risks breaching that SLA when instances are reclaimed. The mature approach — often described as a mixed fleet — runs a baseline of on-demand (or reserved) instances to guarantee SLA-covered capacity, supplemented by spot instances for the elastic, interruption-tolerant portion of the workload.
6 / 25
PR #1234 is titled 'Refactor: Implement API Gateway Integration'. During a code review, Sarah comments: 'I'm seeing a lot of calls to the legacy authentication service. Can we leverage the new Auth0 SDK for this?' Mark replies: 'Yeah, we're aiming for full OIDC integration.' What does OIDC stand for in this context? OIDC (OpenID Connect) is a standard authentication protocol built on top of OAuth 2.0. It's frequently used for single sign-on and federated identity management – in this case, Mark is referring to using OIDC to securely authenticate users via Auth0. The term isn't just about 'open' identity; it describes the specific mechanism of exchanging information between services, which is why OpenID Connect is the correct answer.7 / 25
PR #5678 is titled 'Deploy: Migrate Database to RDS'. During a standup update, David says, 'We're using Lambda functions to orchestrate the data migration. We've configured DynamoDB Streams for change capture and then triggered a Lambda function on every change.' What does DynamoDB Streams primarily facilitate in this scenario? DynamoDB Streams is a key component of AWS's event-driven architecture. It allows you to capture changes made to DynamoDB tables in real-time and then react to those changes by triggering other services, like Lambda functions, as David describes. The crucial point here is that Streams facilitates the automated reaction *based on data change*, not encryption, backups, or full synchronization – which are handled by different AWS services.
8 / 25
PR #9012 is titled 'Update: Implement Serverless Backend with API Gateway'. During a Slack discussion about the changes, John writes: 'We're using AWS Lambda to handle requests and API Gateway for routing. We've configured an IAM role with permissions for Lambda to access S3.' What does IAM primarily facilitate in this context?
IAM (Identity and Access Management) is crucial for controlling who or what can access other AWS services. In this scenario, the IAM role grants the Lambda function the necessary permissions to read from and write to S3, ensuring only authorized actions are performed – preventing unauthorized data access. Options A, C, and D represent related functionalities but don't directly address the core purpose of IAM as a permission management system.
9 / 25
PR #7890 is titled 'Implement Monitoring with CloudWatch'. During a technical discussion, Emily says, 'We need to set up alarms based on CPU utilization and error rates. We'll use CloudWatch Metrics for this.' Mark replies, 'Sounds good – we should also consider using CloudWatch Logs Insights to analyze our log data.' What does CloudWatch primarily facilitate in this scenario?
CloudWatch is a comprehensive monitoring service. It's core functionality involves collecting and tracking metrics (like CPU utilization) and logs from various AWS resources, allowing for automated scaling and alerting based on defined thresholds—as Emily describes. While CloudWatch Logs Insights *does* analyze log data, the primary purpose of CloudWatch in this scenario is broader monitoring, not just log analysis. Option A is incorrect as CloudWatch doesn't provide direct hardware access.
10 / 25
During a Slack discussion about migrating to Kubernetes on AWS, Alex writes: 'We're going with EKS – it seems like the best way to manage our containers.' Ben replies: 'Good call! We'll also be using ECS for some of our legacy applications.' What is the primary difference between EKS and ECS in this context?
EKS (Elastic Kubernetes Service) and ECS (Elastic Container Service) are both container orchestration services offered by AWS, but they differ significantly in their complexity. EKS is a managed version of Kubernetes, offering the full power and flexibility of Kubernetes with reduced operational burden, while ECS is a simpler service focused on deploying and managing containers within an AWS environment. The key difference lies in the level of control and management required – EKS provides more granular control through Kubernetes primitives.
11 / 25
PR #1234 is titled 'Refactor: Implement API Gateway Integration'. During a code review, Sarah comments: 'I'm seeing a lot of calls to the legacy authentication service. Can we leverage the new Auth0 SDK for this?' Mark replies: 'Yeah, we're aiming for full OIDC integration.' What does OIDC stand for in this context? OIDC (OpenID Connect) is a standard authentication protocol built on top of OAuth 2.0. It's frequently used for single sign-on and federated identity management – in this case, Mark is referring to using OIDC to securely authenticate users via Auth0. The term isn't just about 'open' identity; it describes the specific mechanism of exchanging information between services, which is why OpenID Connect is the correct answer.12 / 25
PR #5678 is titled 'Deploy: Migrate Database to RDS'. During a standup update, David says, 'We're using Lambda functions to orchestrate the data migration. We've configured DynamoDB Streams for change capture and then triggered a Lambda function on every change.' What does DynamoDB Streams primarily facilitate in this scenario? DynamoDB Streams is a key component of AWS's event-driven architecture. It allows you to capture changes made to DynamoDB tables in real-time and then react to those changes by triggering other services, like Lambda functions, as David describes. The crucial point here is that Streams facilitates the automated reaction *based on data change*, not encryption, backups, or full synchronization – which are handled by different AWS services.
13 / 25
PR #9012 is titled 'Update: Implement Serverless Backend with API Gateway'. During a Slack discussion about the changes, John writes: 'We're using AWS Lambda to handle requests and API Gateway for routing. We've configured an IAM role with permissions for Lambda to access S3.' What does IAM primarily facilitate in this context?
IAM (Identity and Access Management) is crucial for controlling who or what can access other AWS services. In this scenario, the IAM role grants the Lambda function the necessary permissions to read from and write to S3, ensuring only authorized actions are performed – preventing unauthorized data access. Options A, C, and D represent related functionalities but don't directly address the core purpose of IAM as a permission management system.
14 / 25
PR #7890 is titled 'Implement Monitoring with CloudWatch'. During a technical discussion, Emily says, 'We need to set up alarms based on CPU utilization and error rates. We'll use CloudWatch Metrics for this.' Mark replies, 'Sounds good – we should also consider using CloudWatch Logs Insights to analyze our log data.' What does CloudWatch primarily facilitate in this scenario?
CloudWatch is a comprehensive monitoring service. It's core functionality involves collecting and tracking metrics (like CPU utilization) and logs from various AWS resources, allowing for automated scaling and alerting based on defined thresholds—as Emily describes. While CloudWatch Logs Insights *does* analyze log data, the primary purpose of CloudWatch in this scenario is broader monitoring, not just log analysis. Option A is incorrect as CloudWatch doesn't provide direct hardware access.
15 / 25
During a Slack discussion about migrating to Kubernetes on AWS, Alex writes: 'We're going with EKS – it seems like the best way to manage our containers.' Ben replies: 'Good call! We'll also be using ECS for some of our legacy applications.' What is the primary difference between EKS and ECS in this context?
EKS (Elastic Kubernetes Service) and ECS (Elastic Container Service) are both container orchestration services offered by AWS, but they differ significantly in their complexity. EKS is a managed version of Kubernetes, offering the full power and flexibility of Kubernetes with reduced operational burden, while ECS is a simpler service focused on deploying and managing containers within an AWS environment. The key difference lies in the level of control and management required – EKS provides more granular control through Kubernetes primitives.
16 / 25
PR #1234 is titled 'Refactor: Implement API Gateway Integration'. During a code review, Sarah comments: 'I'm seeing a lot of calls to the legacy authentication service. Can we leverage the new Auth0 SDK for this?' Mark replies: 'Yeah, we're aiming for full OIDC integration.' What does OIDC stand for in this context? OIDC (OpenID Connect) is a standard authentication protocol built on top of OAuth 2.0. It's frequently used for single sign-on and federated identity management – in this case, Mark is referring to using OIDC to securely authenticate users via Auth0. The term isn't just about 'open' identity; it describes the specific mechanism of exchanging information between services, which is why OpenID Connect is the correct answer.17 / 25
PR #5678 is titled 'Deploy: Migrate Database to RDS'. During a standup update, David says, 'We're using Lambda functions to orchestrate the data migration. We've configured DynamoDB Streams for change capture and then triggered a Lambda function on every change.' What does DynamoDB Streams primarily facilitate in this scenario? DynamoDB Streams is a key component of AWS's event-driven architecture. It allows you to capture changes made to DynamoDB tables in real-time and then react to those changes by triggering other services, like Lambda functions, as David describes. The crucial point here is that Streams facilitates the automated reaction *based on data change*, not encryption, backups, or full synchronization – which are handled by different AWS services.
18 / 25
PR #9012 is titled 'Update: Implement Serverless Backend with API Gateway'. During a Slack discussion about the changes, John writes: 'We're using AWS Lambda to handle requests and API Gateway for routing. We've configured an IAM role with permissions for Lambda to access S3.' What does IAM primarily facilitate in this context?
IAM (Identity and Access Management) is crucial for controlling who or what can access other AWS services. In this scenario, the IAM role grants the Lambda function the necessary permissions to read from and write to S3, ensuring only authorized actions are performed – preventing unauthorized data access. Options A, C, and D represent related functionalities but don't directly address the core purpose of IAM as a permission management system.
19 / 25
PR #7890 is titled 'Implement Monitoring with CloudWatch'. During a technical discussion, Emily says, 'We need to set up alarms based on CPU utilization and error rates. We'll use CloudWatch Metrics for this.' Mark replies, 'Sounds good – we should also consider using CloudWatch Logs Insights to analyze our log data.' What does CloudWatch primarily facilitate in this scenario?
CloudWatch is a comprehensive monitoring service. It's core functionality involves collecting and tracking metrics (like CPU utilization) and logs from various AWS resources, allowing for automated scaling and alerting based on defined thresholds—as Emily describes. While CloudWatch Logs Insights *does* analyze log data, the primary purpose of CloudWatch in this scenario is broader monitoring, not just log analysis. Option A is incorrect as CloudWatch doesn't provide direct hardware access.
20 / 25
During a Slack discussion about migrating to Kubernetes on AWS, Alex writes: 'We're going with EKS – it seems like the best way to manage our containers.' Ben replies: 'Good call! We'll also be using ECS for some of our legacy applications.' What is the primary difference between EKS and ECS in this context?
EKS (Elastic Kubernetes Service) and ECS (Elastic Container Service) are both container orchestration services offered by AWS, but they differ significantly in their complexity. EKS is a managed version of Kubernetes, offering the full power and flexibility of Kubernetes with reduced operational burden, while ECS is a simpler service focused on deploying and managing containers within an AWS environment. The key difference lies in the level of control and management required – EKS provides more granular control through Kubernetes primitives.
21 / 25
PR #1234 is titled 'Refactor: Implement API Gateway Integration'. During a code review, Sarah comments: 'I'm seeing a lot of calls to the legacy authentication service. Can we leverage the new Auth0 SDK for this?' Mark replies: 'Yeah, we're aiming for full OIDC integration.' What does OIDC stand for in this context? OIDC (OpenID Connect) is a standard authentication protocol built on top of OAuth 2.0. It's frequently used for single sign-on and federated identity management – in this case, Mark is referring to using OIDC to securely authenticate users via Auth0. The term isn't just about 'open' identity; it describes the specific mechanism of exchanging information between services, which is why OpenID Connect is the correct answer.22 / 25
PR #5678 is titled 'Deploy: Migrate Database to RDS'. During a standup update, David says, 'We're using Lambda functions to orchestrate the data migration. We've configured DynamoDB Streams for change capture and then triggered a Lambda function on every change.' What does DynamoDB Streams primarily facilitate in this scenario? DynamoDB Streams is a key component of AWS's event-driven architecture. It allows you to capture changes made to DynamoDB tables in real-time and then react to those changes by triggering other services, like Lambda functions, as David describes. The crucial point here is that Streams facilitates the automated reaction *based on data change*, not encryption, backups, or full synchronization – which are handled by different AWS services.
23 / 25
PR #9012 is titled 'Update: Implement Serverless Backend with API Gateway'. During a Slack discussion about the changes, John writes: 'We're using AWS Lambda to handle requests and API Gateway for routing. We've configured an IAM role with permissions for Lambda to access S3.' What does IAM primarily facilitate in this context?
IAM (Identity and Access Management) is crucial for controlling who or what can access other AWS services. In this scenario, the IAM role grants the Lambda function the necessary permissions to read from and write to S3, ensuring only authorized actions are performed – preventing unauthorized data access. Options A, C, and D represent related functionalities but don't directly address the core purpose of IAM as a permission management system.
24 / 25
PR #7890 is titled 'Implement Monitoring with CloudWatch'. During a technical discussion, Emily says, 'We need to set up alarms based on CPU utilization and error rates. We'll use CloudWatch Metrics for this.' Mark replies, 'Sounds good – we should also consider using CloudWatch Logs Insights to analyze our log data.' What does CloudWatch primarily facilitate in this scenario?
CloudWatch is a comprehensive monitoring service. It's core functionality involves collecting and tracking metrics (like CPU utilization) and logs from various AWS resources, allowing for automated scaling and alerting based on defined thresholds—as Emily describes. While CloudWatch Logs Insights *does* analyze log data, the primary purpose of CloudWatch in this scenario is broader monitoring, not just log analysis. Option A is incorrect as CloudWatch doesn't provide direct hardware access.
25 / 25
During a Slack discussion about migrating to Kubernetes on AWS, Alex writes: 'We're going with EKS – it seems like the best way to manage our containers.' Ben replies: 'Good call! We'll also be using ECS for some of our legacy applications.' What is the primary difference between EKS and ECS in this context?
EKS (Elastic Kubernetes Service) and ECS (Elastic Container Service) are both container orchestration services offered by AWS, but they differ significantly in their complexity. EKS is a managed version of Kubernetes, offering the full power and flexibility of Kubernetes with reduced operational burden, while ECS is a simpler service focused on deploying and managing containers within an AWS environment. The key difference lies in the level of control and management required – EKS provides more granular control through Kubernetes primitives.
Frequently Asked Questions
What will I practice in "Cloud Abbreviations — IT Abbreviations Exercises"?
This is an IT Abbreviations exercise set. It walks through 25 scenario-based multiple-choice questions built around real usage of IT Abbreviations 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 25 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 IT Abbreviations 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 IT Abbreviations exercises?
See the IT Abbreviations 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 — IT Abbreviations vocabulary comes up often in technical discussions and interviews. Pair this exercise with our dedicated Interview Preparation section for role-specific practice.