Kubernetes and Cloud Native Associate (KCNA)Cloud Native ArchitectureEasy
A startup is building a new application and wants to minimize operational overhead for managing servers and scaling infrastructure, while only paying for the compute resources consumed during actual code execution. Which cloud native architectural paradigm aligns best with these goals?
- AService mesh
- BServerless computing
- CMicroservices
- DContainerization
Show answer & explanationAnswer & explanation
Correct answer: B. Serverless computing
Serverless computing allows developers to deploy code without managing servers, automatically scales based on demand, and charges only for the compute time consumed, directly addressing the goals of minimal operational overhead and pay-per-execution.
Why the other options are wrong
- A. A service mesh manages inter-service communication, unrelated to server management or billing model.
- C. Microservices is an architectural style, not directly about server management or billing model.
- D. Containerization packages applications but still requires managing the underlying container runtime and infrastructure.
Serverless Computing
A cloud-native execution model where the cloud provider dynamically manages the allocation and provisioning of servers, allowing developers to focus solely on writing code.
- No server management required.
- Automatic scaling.
- Pay-per-execution billing model.
- Event-driven architecture is common.
Memory trick: Serverless: No servers, no worries, just code and pay for what you use.