LFCA 126 🐧 LFCA Practice Questions — Domain 3
Domain 3, Cloud Computing Fundamentals, is 18% of the LFCA exam—roughly 11 questions. It is the second-largest domain, and it is entirely conceptual. There are no commands to memorize, no configurations to build. The questions test whether you understand what the cloud is, how it is delivered, how it is deployed, and how it is priced. The vocabulary—IaaS, PaaS, SaaS, FaaS, public, private, hybrid, multi-cloud, vertical scaling, horizontal scaling—is the content.
This chapter is a set of practice questions in the style of the LFCA exam. Each question presents a scenario and asks for the best answer among four choices. The answers are explained, and the distractors are identified so you can see why the wrong answers are wrong. The questions cover the specific competencies in Domain 3: cloud service models, deployment models, virtualization versus containers, scalability, availability, budgeting, and serverless computing.
Key point: Domain 3 is about vocabulary and concepts, not implementation. It tests whether you can distinguish IaaS from PaaS, public from private, VMs from containers, and vertical from horizontal scaling. The correct answer is the one that matches the definition, not the one that sounds most technical.
Why Domain 3 matters
The ubiquity problem. Cloud computing is not a niche topic. Most new applications are deployed to a cloud provider. Most organizations use at least one cloud service, even if it is just email. The LFCA treats cloud fundamentals as a core competency because it is now part of the baseline knowledge for anyone working in IT.
The vocabulary problem. Cloud terminology is dense and overlapping. IaaS, PaaS, SaaS, and FaaS describe how much of the stack the provider manages. Public, private, hybrid, and multi-cloud describe where the infrastructure lives. Scalability, elasticity, and availability describe how the system behaves under load. The exam tests whether you can keep these categories distinct.
The comparison problem. The most common cloud questions are comparisons. What is the difference between a virtual machine and a container? What is the difference between vertical and horizontal scaling? What is the difference between a public cloud and a private cloud? The exam asks you to identify which option matches the scenario, not to define the terms in isolation.
The shared responsibility problem. The shared responsibility model defines what the cloud provider manages and what the customer manages. In IaaS, the provider manages the hardware and virtualization, and the customer manages the OS and everything above it. In PaaS, the provider manages the runtime and the customer manages the application. In SaaS, the provider manages everything. The exam tests whether you know where the boundary lies.
The cost problem. Cloud pricing is usage-based. On-demand pricing charges per hour or per second. Reserved instances offer a discount for a commitment. Spot instances offer a deeper discount for interruptible workloads. The exam tests the conceptual difference, not the specific prices.
a. Cloud service models and deployment models
Question 1. Which cloud service model provides virtual machines, storage, and networking, while the customer manages the operating system and applications?
A. SaaS
B. PaaS
C. IaaS
D. FaaS
Answer: C. Infrastructure as a Service (IaaS) provides the foundational infrastructure—compute, storage, and networking—while the customer manages the operating system, middleware, and applications. Examples include Amazon EC2, Azure Virtual Machines, and Google Compute Engine. Option A, SaaS, provides a complete application. Option B, PaaS, provides a platform for deploying applications without managing the underlying infrastructure. Option D, FaaS, provides a function execution environment.
Question 2. A development team wants to deploy code without managing servers, operating systems, or runtimes. Which service model is most appropriate?
A. IaaS
B. PaaS
C. On-premises
D. Colocation
Answer: B. Platform as a Service (PaaS) provides a managed platform where the customer deploys code and the provider manages the servers, operating systems, and runtimes. Examples include Heroku, Google App Engine, and AWS Elastic Beanstalk. Option A, IaaS, requires the customer to manage the operating system and runtime. Option C, on-premises, requires managing everything. Option D, colocation, provides physical space and power but not a managed platform.
Question 3. Which cloud deployment model combines on-premises infrastructure with public cloud resources?
A. Public cloud
B. Private cloud
C. Hybrid cloud
D. Multi-cloud
Answer: C. A hybrid cloud combines on-premises infrastructure with public cloud resources, allowing workloads to move between them. Option A, public cloud, is entirely hosted by a provider. Option B, private cloud, is dedicated to a single organization. Option D, multi-cloud, uses two or more public cloud providers.
Question 4. An organization uses AWS for its primary workloads and Azure for its disaster recovery site. Which deployment model is this?
A. Hybrid cloud
B. Multi-cloud
C. Private cloud
D. Public cloud
Answer: B. Multi-cloud means using two or more public cloud providers. The organization uses AWS and Azure, both public clouds. Option A, hybrid cloud, combines on-premises with public cloud. Option C, private cloud, is dedicated infrastructure. Option D, public cloud, is a single provider’s shared infrastructure.
Question 5. Which of the following is an example of SaaS?
A. Amazon EC2
B. Google App Engine
C. Gmail
D. AWS Lambda
Answer: C. Gmail is Software as a Service. The user accesses the application through a browser, and Google manages everything—infrastructure, platform, and application. Option A, EC2, is IaaS. Option B, App Engine, is PaaS. Option D, Lambda, is FaaS.
Question 6. In the shared responsibility model for IaaS, which of the following is the customer’s responsibility?
A. Physical security of the data center
B. Hypervisor patching
C. Operating system patching
D. Network hardware maintenance
Answer: C. In IaaS, the customer is responsible for the operating system, including patching, configuration, and security. The provider is responsible for the physical infrastructure, the hypervisor, and the network hardware. Options A, B, and D are provider responsibilities in IaaS.
Question 7. What does FaaS stand for, and what is its primary characteristic?
A. File as a Service; provides file storage
B. Function as a Service; runs individual functions without server management
C. Framework as a Service; provides application frameworks
D. Firewall as a Service; provides network security
Answer: B. Function as a Service (FaaS) runs individual functions in response to events, without the customer managing servers, runtimes, or scaling. Examples include AWS Lambda, Azure Functions, and Google Cloud Functions. The provider handles all infrastructure and scaling. The customer writes and deploys functions.
Question 8. Which cloud service model gives the customer the most control over the environment?
A. SaaS
B. PaaS
C. IaaS
D. FaaS
Answer: C. IaaS gives the customer the most control because the customer manages the operating system, the runtime, the middleware, and the application. PaaS, SaaS, and FaaS manage more of the stack for the customer, which means less control but also less operational burden.
b. Virtualization, containers, and scaling
Question 9. What is the primary difference between a virtual machine and a container?
A. Virtual machines are faster to start
B. Containers share the host kernel; virtual machines run a full guest OS
C. Containers require a hypervisor; virtual machines do not
D. Virtual machines use less memory
Answer: B. Containers share the host operating system’s kernel and isolate processes using namespaces and cgroups. Virtual machines run a complete guest operating system on top of a hypervisor. This is why containers start in seconds and VMs take minutes, and why containers have lower overhead. Option A is the reverse—containers start faster. Option C is the reverse—VMs require a hypervisor. Option D is the reverse—VMs use more memory because each runs a full OS.
Question 10. A workload needs to scale from 2 instances to 20 during peak hours. Which scaling approach is this?
A. Vertical scaling
B. Horizontal scaling
C. Diagonal scaling
D. Fixed scaling
Answer: B. Horizontal scaling adds more instances of the same size. Scaling from 2 to 20 instances is horizontal scaling, also called scaling out. Option A, vertical scaling, increases the resources of a single instance—more CPU, more memory. Option C is not a standard term. Option D describes a fixed capacity that does not change.
Question 11. An administrator upgrades a database server from 16 GB of RAM to 64 GB to handle increased load. Which type of scaling is this?
A. Horizontal scaling
B. Vertical scaling
C. Elastic scaling
D. Auto scaling
Answer: B. Vertical scaling increases the resources of a single machine. Adding RAM to a database server is vertical scaling, also called scaling up. Option A, horizontal scaling, would add more database servers. Options C and D describe automated scaling behavior, not the direction of the scaling.
Question 12. Which characteristic of cloud computing allows resources to be added or removed automatically based on demand?
A. Elasticity
B. Durability
C. Redundancy
D. Federation
Answer: A. Elasticity is the ability to automatically scale resources up or down based on demand. Option B, durability, refers to data persistence. Option C, redundancy, refers to duplicate components for fault tolerance. Option D, federation, refers to combining multiple systems.
Question 13. What is the primary benefit of using containers over virtual machines for a microservices application?
A. Stronger isolation
B. Lower resource overhead and faster startup
C. Better support for Windows applications
D. Simpler networking
Answer: B. Containers have lower resource overhead because they share the host kernel, and they start faster because there is no guest OS to boot. For a microservices application with many small services, this efficiency matters. Option A is incorrect—VMs provide stronger isolation because they run separate kernels. Option C is not a general advantage of containers. Option D is not accurate—container networking can be more complex than VM networking.
Question 14. Which of the following describes high availability?
A. A system that is always accessible with minimal downtime
B. A system that can scale to handle any load
C. A system that stores data in multiple formats
D. A system that uses the least expensive resources
Answer: A. High availability means a system is accessible and functional for a high percentage of time, typically achieved through redundancy and failover. Option B describes scalability. Option C describes data management, not availability. Option D describes cost optimization.
c. Budgeting and cloud economics
Question 15. Which cloud pricing model offers a discount in exchange for a commitment to a specific amount of usage over a period of time?
A. On-demand pricing
B. Reserved pricing
C. Spot pricing
D. Free tier
Answer: B. Reserved pricing offers a discount when the customer commits to a specific amount of usage—for example, one year or three years of a particular instance type. Option A, on-demand pricing, charges by the hour or second with no commitment. Option C, spot pricing, offers a deeper discount for interruptible workloads. Option D, free tier, provides limited usage at no cost.
Question 16. A company runs a batch processing job that can be interrupted and restarted. Which pricing model is most cost-effective?
A. On-demand
B. Reserved
C. Spot
D. Dedicated
Answer: C. Spot pricing offers the deepest discount for workloads that can tolerate interruption. The cloud provider can reclaim spot instances when capacity is needed, but the customer pays a fraction of the on-demand price. For batch jobs that can restart, this is the most cost-effective option. Option A, on-demand, is more expensive. Option B, reserved, requires a commitment and is not appropriate for interruptible workloads. Option D, dedicated, is the most expensive.
Question 17. Which of the following is a benefit of cloud computing over on-premises infrastructure?
A. Lower latency for all workloads
B. No need for any security controls
C. Elastic capacity without upfront capital investment
D. Complete control over physical hardware
Answer: C. Cloud computing provides elastic capacity that can be scaled up or down on demand, without the upfront capital investment required for on-premises hardware. Option A is not universally true—on-premises can have lower latency for local workloads. Option B is incorrect—security is still required in the cloud. Option D is incorrect—the customer does not control the physical hardware in a public cloud.
Question 18. What is the primary difference between cloud scalability and cloud elasticity?
A. Scalability is automatic; elasticity is manual
B. Scalability is the ability to grow; elasticity is the ability to grow and shrink automatically
C. Scalability applies to storage; elasticity applies to compute
D. Scalability is for private clouds; elasticity is for public clouds
Answer: B. Scalability is the ability of a system to handle growth. Elasticity is the ability to automatically scale up and down based on demand. A system can be scalable—capable of growing—without being elastic—automatically adjusting. Option A is the reverse. Option C is incorrect—both apply to all resource types. Option D is incorrect—both apply to all deployment models.
Complete Example Session
# ============================================
# PART 1: SERVICE MODELS
# ============================================
IaaS → infrastructure (VMs, storage, network)
PaaS → platform (runtime, middleware)
SaaS → software (complete application)
FaaS → functions (event-driven execution)
# ============================================
# PART 2: DEPLOYMENT MODELS
# ============================================
Public → shared infrastructure
Private → dedicated infrastructure
Hybrid → on-premises + public cloud
Multi-cloud → two or more public clouds
# ============================================
# PART 3: VMs VS CONTAINERS
# ============================================
VM → full guest OS, hypervisor, minutes to start, GBs
Container → shares kernel, namespaces, seconds to start, MBs
# ============================================
# PART 4: SCALING
# ============================================
Vertical → bigger machine (more CPU, RAM)
Horizontal → more machines
Elasticity → automatic scaling up and downThe four parts summarized the concepts tested in Domain 3: service models, deployment models, VMs versus containers, and scaling.
Quick Reference
Service Models
| Model | Provider Manages | Customer Manages | Examples |
|---|---|---|---|
| IaaS | Hardware, virtualization | OS, runtime, app | EC2, Azure VMs |
| PaaS | Hardware, runtime | Application | Heroku, App Engine |
| SaaS | Everything | Nothing (uses app) | Gmail, Salesforce |
| FaaS | Everything, scaling | Function code | Lambda, Cloud Functions |
Deployment Models
| Model | Description |
|---|---|
| Public | Shared infrastructure, provider-owned |
| Private | Dedicated infrastructure, single organization |
| Hybrid | On-premises + public cloud |
| Multi-cloud | Two or more public clouds |
VMs vs Containers
| Aspect | VM | Container |
|---|---|---|
| OS | Full guest OS | Shares host kernel |
| Startup | Minutes | Seconds |
| Size | Gigabytes | Megabytes |
| Isolation | Strong (separate kernel) | Process-level |
| Density | Lower | Higher |
Scaling
| Type | Description |
|---|---|
| Vertical | Bigger machine (scale up) |
| Horizontal | More machines (scale out) |
| Elasticity | Automatic scaling |
| Availability | Uptime and fault tolerance |
Pricing Models
| Model | Commitment | Discount | Interruption |
|---|---|---|---|
| On-demand | None | None | No |
| Reserved | 1–3 years | Moderate | No |
| Spot | None | Deep | Yes |
| Free tier | None | Limited usage | N/A |
Best Practices
✅ Do This:
# Match service model to the scenario
No server management → PaaS or FaaS # ✅
# Match deployment model to the architecture
On-prem + cloud → hybrid # ✅
Two public clouds → multi-cloud # ✅
# Match scaling direction to the action
More machines → horizontal # ✅
Bigger machine → vertical # ✅
# Match pricing to the workload
Interruptible batch → spot # ✅
Steady long-term → reserved # ✅❌ Don’t Do This:
# Don't confuse IaaS and PaaS
IaaS gives VMs; PaaS gives a platform # ❌
# Don't confuse hybrid and multi-cloud
Hybrid = on-prem + cloud; multi-cloud = multiple clouds # ❌
# Don't confuse vertical and horizontal
Vertical = bigger; horizontal = more # ❌
# Don't assume spot instances are always available
Spot can be reclaimed at any time # ⚠️Common Pitfalls
| Pitfall | Why It Happens | Fix |
|---|---|---|
| Confusing IaaS and PaaS | Both provide infrastructure | IaaS = VMs, PaaS = platform |
| Confusing hybrid and multi-cloud | Both involve multiple environments | Hybrid = on-prem + cloud |
| Confusing vertical and horizontal | Both are scaling | Vertical = bigger, horizontal = more |
| Assuming containers provide VM isolation | Both isolate | Containers share the kernel |
| Confusing scalability and elasticity | Both involve growth | Elasticity is automatic |
Real-World Examples
1. IaaS Example
EC2 instance: customer manages OS, runtime, app
Provider manages hardware, hypervisor, network2. PaaS Example
Heroku: customer deploys code
Provider manages OS, runtime, scaling3. SaaS Example
Gmail: customer uses application
Provider manages everything4. FaaS Example
Lambda: customer writes function
Provider manages runtime, scaling, infrastructure5. Hybrid Cloud
On-premises database + cloud web tier
Data stays local; compute scales in cloud6. Multi-Cloud
AWS for primary + Azure for disaster recovery
Two public providers, independent infrastructure7. Vertical Scaling
Database server: 16 GB RAM → 64 GB RAM
Same machine, more resources8. Horizontal Scaling
Web tier: 2 instances → 20 instances
More machines, same size9. Spot Instance
Batch processing job that can restart
Deep discount, may be interrupted10. Reserved Instance
Production web server, steady load
1-year commitment, moderate discountVisual
Service Model Stack
┌─────────────────────────────────────────────────────────────┐
│ CLOUD SERVICE MODELS │
│ │
│ On-Premises IaaS PaaS SaaS FaaS │
│ ┌──────────┐ ┌────────┐ ┌────────┐ ┌────────┐ ┌────────┐ │
│ │Application│ │App │ │App │ │App │ │Function│ │
│ ├──────────┤ ├────────┤ ├────────┤ ├────────┤ ├────────┤ │
│ │Data │ │Data │ │Data │ │Data │ │Data │ │
│ ├──────────┤ ├────────┤ ├────────┤ ├────────┤ ├────────┤ │
│ │Runtime │ │Runtime │ │Runtime │ │Runtime │ │Runtime │ │
│ ├──────────┤ ├────────┤ ├────────┤ ├────────┤ ├────────┤ │
│ │OS │ │OS │ │OS │ │OS │ │OS │ │
│ ├──────────┤ ├────────┤ ├────────┤ ├────────┤ ├────────┤ │
│ │Virtual- │ │Virtual-│ │Virtual-│ │Virtual-│ │Virtual-│ │
│ │ization │ │ization │ │ization │ │ization │ │ization │ │
│ ├──────────┤ ├────────┤ ├────────┤ ├────────┤ ├────────┤ │
│ │Hardware │ │Hardware│ │Hardware│ │Hardware│ │Hardware│ │
│ └──────────┘ └────────┘ └────────┘ └────────┘ └────────┘ │
│ │
│ ◀── Customer manages ──▶ ◀── Provider manages ──▶ │
│ │
│ On-prem: customer manages everything │
│ IaaS: provider manages hardware, customer manages OS+ │
│ PaaS: provider manages OS and runtime, customer app │
│ SaaS: provider manages everything │
│ FaaS: provider manages everything, customer function only │
│ │
└─────────────────────────────────────────────────────────────┘Deployment Models
┌─────────────────────────────────────────────────────────────┐
│ DEPLOYMENT MODELS │
│ │
│ PUBLIC CLOUD │
│ ┌─────────────────────────────────────────────────────┐ │
│ │ Shared infrastructure │ │
│ │ Provider owns and operates │ │
│ │ Multiple tenants │ │
│ │ Pay for what you use │ │
│ └─────────────────────────────────────────────────────┘ │
│ │
│ PRIVATE CLOUD │
│ ┌─────────────────────────────────────────────────────┐ │
│ │ Dedicated infrastructure │ │
│ │ Single organization │ │
│ │ On-premises or hosted │ │
│ │ More control, higher cost │ │
│ └─────────────────────────────────────────────────────┘ │
│ │
│ HYBRID CLOUD │
│ ┌─────────────────────────────────────────────────────┐ │
│ │ On-premises + public cloud │ │
│ │ Workloads move between them │ │
│ │ Data locality + cloud elasticity │ │
│ └─────────────────────────────────────────────────────┘ │
│ │
│ MULTI-CLOUD │
│ ┌─────────────────────────────────────────────────────┐ │
│ │ Two or more public clouds │ │
│ │ Avoid vendor lock-in │ │
│ │ Best-of-breed services │ │
│ └─────────────────────────────────────────────────────┘ │
│ │
└─────────────────────────────────────────────────────────────┘VM vs Container
┌─────────────────────────────────────────────────────────────┐
│ VIRTUAL MACHINE │
│ │
│ ┌─────────────────────────────────────────────────────┐ │
│ │ App A │ App B │ App C │ │
│ │ Libs │ Libs │ Libs │ │
│ │ Guest OS │ Guest OS │ Guest OS │ │
│ │ (full kernel per VM) │ │
│ │ Hypervisor │ │
│ │ Host OS │ │
│ │ Hardware │ │
│ └─────────────────────────────────────────────────────┘ │
│ │
│ Heavy, strong isolation, minutes to start │
│ │
├─────────────────────────────────────────────────────────────┤
│ │
│ CONTAINERS │
│ │
│ ┌─────────────────────────────────────────────────────┐ │
│ │ App A │ App B │ App C │ │
│ │ Libs │ Libs │ Libs │ │
│ │ (shares host kernel) │ │
│ │ Container runtime │ │
│ │ Host OS │ │
│ │ Hardware │ │
│ └─────────────────────────────────────────────────────┘ │
│ │
│ Light, process-level isolation, seconds to start │
│ │
└─────────────────────────────────────────────────────────────┘Scaling
┌─────────────────────────────────────────────────────────────┐
│ VERTICAL SCALING (Scale Up) │
│ │
│ Before: [2 CPU, 4 GB] │
│ After: [8 CPU, 32 GB] │
│ │
│ Same machine, more resources. │
│ Limited by hardware maximum. │
│ │
├─────────────────────────────────────────────────────────────┤
│ │
│ HORIZONTAL SCALING (Scale Out) │
│ │
│ Before: [2 CPU, 4 GB] │
│ After: [2 CPU, 4 GB] [2 CPU, 4 GB] [2 CPU, 4 GB] │
│ │
│ More machines, same size. │
│ Requires load balancing. │
│ │
├─────────────────────────────────────────────────────────────┤
│ │
│ ELASTICITY │
│ │
│ Automatic scaling up and down based on demand. │
│ Horizontal or vertical, but automated. │
│ │
└─────────────────────────────────────────────────────────────┘Summary
| Topic | Key Distinction |
|---|---|
| IaaS | Infrastructure: VMs, storage, network |
| PaaS | Platform: runtime, middleware |
| SaaS | Software: complete application |
| FaaS | Functions: event-driven execution |
| Public cloud | Shared infrastructure |
| Private cloud | Dedicated infrastructure |
| Hybrid cloud | On-premises + public cloud |
| Multi-cloud | Two or more public clouds |
| VM | Full guest OS, hypervisor, heavy |
| Container | Shares kernel, light, fast |
| Vertical scaling | Bigger machine |
| Horizontal scaling | More machines |
| Elasticity | Automatic scaling |
| Spot pricing | Interruptible, deep discount |
| Reserved pricing | Commitment, moderate discount |
Key takeaways:
- Service models describe how much of the stack the provider manages. IaaS provides infrastructure, PaaS provides a platform, SaaS provides an application, and FaaS provides a function execution environment. The customer manages less as the model moves from IaaS to SaaS.
- Deployment models describe where the infrastructure lives. Public cloud is shared and provider-owned. Private cloud is dedicated. Hybrid combines on-premises with public cloud. Multi-cloud uses two or more public providers.
- Containers share the host kernel; VMs run a full guest OS. This is why containers are lighter, faster to start, and more densely packed. VMs provide stronger isolation because each has its own kernel.
- Vertical scaling makes a machine bigger; horizontal scaling adds more machines. Vertical is simpler but limited by hardware maximums. Horizontal requires load balancing but can scale further.
- Elasticity is automatic scaling. Scalability is the ability to grow. Elasticity is the ability to grow and shrink automatically based on demand.
- Spot pricing is the cheapest but interruptible. Reserved pricing offers a discount for commitment. On-demand has no commitment and no discount. The right choice depends on the workload’s tolerance for interruption and its expected duration.
- The shared responsibility model defines the boundary. In IaaS, the customer manages the OS and above. In PaaS, the customer manages the application. In SaaS, the customer manages nothing. The provider’s responsibility grows as the service model moves from IaaS to SaaS.
Remember: Domain 3 is conceptual. It tests whether you understand the vocabulary of cloud computing and can apply it to scenarios. The questions are comparisons: which model fits this situation, which scaling approach is this, which pricing model is most cost-effective. The correct answer is the one that matches the definition. If you know what IaaS, PaaS, SaaS, and FaaS mean, if you can distinguish public from private from hybrid from multi-cloud, and if you know the difference between vertical and horizontal scaling, the domain is straightforward.
Stop using slow, ad-bloated tool sites! 🤮
🔎 Search “KandZ Tools” on Google to use many professional utilities for free.
KandZ.me is the ultimate minimalist hub for:
✅ Finance (Mortgage, Interest, Inflation)
✅ Tech (Base64, JSON, Dev Suite, IP)
✅ Health (BMI, BMR, TDEE)
✅ Productivity (Timer, Workspace, QR)
⚡️ Fast & Private
🔒 No data leaves your device
💎 100% Free
🔗 Use it now: https://tools.kandz.me
🔖 Bookmark it—you’ll need it later!