Practice cloud and infrastructure abbreviations: VPC, IAM, CDN, CIDR, NAT, TLS, mTLS, JWT, OAuth, OIDC, SAML, SSO, and managed Kubernetes service acronyms.
0 / 13 completed
1 / 13
GKE, AKS, and EKS are all managed Kubernetes services. Which clouds do they belong to?
GKE (Google Kubernetes Engine) is Google Cloud's managed Kubernetes. AKS (Azure Kubernetes Service) is Microsoft Azure's offering. EKS (Elastic Kubernetes Service) is AWS's. All three manage the Kubernetes control plane so you only manage worker nodes.
2 / 13
What does IAM stand for and what is its function in cloud platforms?
IAM (Identity and Access Management) is the system that controls authentication and authorization in cloud platforms. IAM policies define which users, roles, or services can perform which actions on which resources.
3 / 13
What is the difference between TLS and mTLS?
Standard TLS lets the client verify the server's identity (via certificate). mTLS (mutual TLS) requires both sides to present certificates — the server also verifies the client. mTLS is widely used in zero-trust service mesh architectures (e.g., Istio).
4 / 13
What does CIDR stand for and what does a notation like '10.0.0.0/16' mean?
CIDR (Classless Inter-Domain Routing) notation describes IP address ranges. '10.0.0.0/16' means the first 16 bits are fixed (10.0.x.x), giving 65,536 addresses. VPC and subnet sizes are always expressed in CIDR notation.
5 / 13
What is the difference between OAuth 2.0 and OIDC?
OAuth 2.0 handles authorization — delegating access to resources without sharing passwords. OIDC (OpenID Connect) is a thin identity layer on top of OAuth 2.0 that adds authentication — an ID token that tells you who the user is. Most SSO implementations use OIDC.
During a code review of a PR that deploys our new microservice to AWS CloudFormation, Sarah comments: 'Looks like we're using Serverless for the API Gateway. Is that what you mean by Lambda@Edge?' David replies, 'No, I'm deploying the backend directly via CloudFormation and using API Gateway as a standard HTTP endpoint.' What does David actually mean when he refers to 'Lambda@Edge'?
This question tests understanding of a common misinterpretation. 'Lambda@Edge' is a specific deployment pattern – running Lambda functions at edge locations using services like AWS Global Accelerator. David correctly identifies that he's deploying the backend directly through CloudFormation and utilizing API Gateway as an HTTP endpoint, not implying a complex edge computing setup. Option A describes a distinct service; B refers to scaling, not deployment location; and D is too broad.
During a code review of a PR that deploys our new microservice to AWS CloudFormation, Sarah comments: 'Looks like we're using Serverless for the API Gateway. Is that what you mean by Lambda@Edge?' David replies, 'No, I'm deploying the backend directly via CloudFormation and using API Gateway as a standard HTTP endpoint.' What does David actually mean when he refers to 'Lambda@Edge'?
This question tests understanding of a common misinterpretation. 'Lambda@Edge' is a specific deployment pattern – running Lambda functions at edge locations using services like AWS Global Accelerator. David correctly identifies that he's deploying the backend directly through CloudFormation and utilizing API Gateway as an HTTP endpoint, not implying a complex edge computing setup. Option A describes a distinct service; B refers to scaling, not deployment location; and D is too broad.
During a code review of a PR that deploys our new microservice to AWS CloudFormation, Sarah comments: 'Looks like we're using Serverless for the API Gateway. Is that what you mean by Lambda@Edge?' David replies, 'No, I'm deploying the backend directly via CloudFormation and using API Gateway as a standard HTTP endpoint.' What does David actually mean when he refers to 'Lambda@Edge'?
This question tests understanding of a common misinterpretation. 'Lambda@Edge' is a specific deployment pattern – running Lambda functions at edge locations using services like AWS Global Accelerator. David correctly identifies that he's deploying the backend directly through CloudFormation and utilizing API Gateway as an HTTP endpoint, not implying a complex edge computing setup. Option A describes a distinct service; B refers to scaling, not deployment location; and D is too broad.
During a code review of a PR that deploys our new microservice to AWS CloudFormation, Sarah comments: 'Looks like we're using Serverless for the API Gateway. Is that what you mean by Lambda@Edge?' David replies, 'No, I'm deploying the backend directly via CloudFormation and using API Gateway as a standard HTTP endpoint.' What does David actually mean when he refers to 'Lambda@Edge'?
This question tests understanding of a common misinterpretation. 'Lambda@Edge' is a specific deployment pattern – running Lambda functions at edge locations using services like AWS Global Accelerator. David correctly identifies that he's deploying the backend directly through CloudFormation and utilizing API Gateway as an HTTP endpoint, not implying a complex edge computing setup. Option A describes a distinct service; B refers to scaling, not deployment location; and D is too broad.
During a code review of a PR that deploys our new microservice to AWS CloudFormation, Sarah comments: 'Looks like we're using Serverless for the API Gateway. Is that what you mean by Lambda@Edge?' David replies, 'No, I'm deploying the backend directly via CloudFormation and using API Gateway as a standard HTTP endpoint.' What does David actually mean when he refers to 'Lambda@Edge'?
This question tests understanding of a common misinterpretation. 'Lambda@Edge' is a specific deployment pattern – running Lambda functions at edge locations using services like AWS Global Accelerator. David correctly identifies that he's deploying the backend directly through CloudFormation and utilizing API Gateway as an HTTP endpoint, not implying a complex edge computing setup. Option A describes a distinct service; B refers to scaling, not deployment location; and D is too broad.
During a code review of a PR that deploys our new microservice to AWS CloudFormation, Sarah comments: 'Looks like we're using Serverless for the API Gateway. Is that what you mean by Lambda@Edge?' David replies, 'No, I'm deploying the backend directly via CloudFormation and using API Gateway as a standard HTTP endpoint.' What does David actually mean when he refers to 'Lambda@Edge'?
This question tests understanding of a common misinterpretation. 'Lambda@Edge' is a specific deployment pattern – running Lambda functions at edge locations using services like AWS Global Accelerator. David correctly identifies that he's deploying the backend directly through CloudFormation and utilizing API Gateway as an HTTP endpoint, not implying a complex edge computing setup. Option A describes a distinct service; B refers to scaling, not deployment location; and D is too broad.
During a code review of a PR that deploys our new microservice to AWS CloudFormation, Sarah comments: 'Looks like we're using Serverless for the API Gateway. Is that what you mean by Lambda@Edge?' David replies, 'No, I'm deploying the backend directly via CloudFormation and using API Gateway as a standard HTTP endpoint.' What does David actually mean when he refers to 'Lambda@Edge'?
This question tests understanding of a common misinterpretation. 'Lambda@Edge' is a specific deployment pattern – running Lambda functions at edge locations using services like AWS Global Accelerator. David correctly identifies that he's deploying the backend directly through CloudFormation and utilizing API Gateway as an HTTP endpoint, not implying a complex edge computing setup. Option A describes a distinct service; B refers to scaling, not deployment location; and D is too broad.
During a code review of a PR that deploys our new microservice to AWS CloudFormation, Sarah comments: 'Looks like we're using Serverless for the API Gateway. Is that what you mean by Lambda@Edge?' David replies, 'No, I'm deploying the backend directly via CloudFormation and using API Gateway as a standard HTTP endpoint.' What does David actually mean when he refers to 'Lambda@Edge'?
This question tests understanding of a common misinterpretation. 'Lambda@Edge' is a specific deployment pattern – running Lambda functions at edge locations using services like AWS Global Accelerator. David correctly identifies that he's deploying the backend directly through CloudFormation and utilizing API Gateway as an HTTP endpoint, not implying a complex edge computing setup. Option A describes a distinct service; B refers to scaling, not deployment location; and D is too broad.
What will I practice in "Cloud & Infrastructure Abbreviations"?
This is an IT Abbreviations exercise set. It walks through 13 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 13 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.