- Published on
[Golden Kubestronaut] KCNA Extra 30 Practice Questions - Advanced Cloud Native
- Authors

- Name
- Youngju Kim
- @fjvbn20031
- KCNA Extra 30 Practice Questions
- Question 1. CNCF Graduated Projects
- Question 2. 12-Factor App Principles
- Question 3. Sidecar Pattern
- Question 4. Ambassador Pattern
- Question 5. Service Mesh Concepts
- Question 6. GitOps vs Traditional CI/CD
- Question 7. eBPF Technology
- Question 8. WebAssembly (Wasm) and Kubernetes
- Question 9. Backstage
- Question 10. Crossplane
- Question 11. Dapr
- Question 12. CNCF Landscape Categories
- Question 13. OCI (Open Container Initiative)
- Question 14. Serverless and Kubernetes
- Question 15. Flux vs ArgoCD Comparison
- Question 16. CNCF Project Maturity Levels
- Question 17. Three Pillars of Observability
- Question 18. OpenTelemetry
- Question 19. Adapter Pattern
- Question 20. Init Container Pattern
- Question 21. CNCF's Cloud Native Definition
- Question 22. Helm vs Kustomize
- Question 23. CRI (Container Runtime Interface)
- Question 24. CNI (Container Network Interface)
- Question 25. CSI (Container Storage Interface)
- Question 26. Istio Ambient Mesh
- Question 27. Platform Engineering
- Question 28. Cilium's Core Technology
- Question 29. Serverless on Kubernetes
- Question 30. CNCF TAG (Technical Advisory Group)
- Summary
KCNA Extra 30 Practice Questions
These 30 additional questions cover the key KCNA exam domains: CNCF ecosystem, cloud native architecture patterns, service mesh, GitOps, and modern technology trends.
Question 1. CNCF Graduated Projects
Which of the following is NOT a CNCF Graduated project?
- A) Prometheus
- B) Envoy
- C) Backstage
- D) containerd
Answer and Explanation
Answer: C) Backstage
Backstage is a CNCF Incubating project. Prometheus, Envoy, and containerd are all Graduated projects. CNCF projects progress through three maturity levels: Sandbox, Incubating, and Graduated.
Question 2. 12-Factor App Principles
According to the 12-Factor App methodology, what is the correct approach to "Config"?
- A) Config should be stored in version control alongside code
- B) Config should be injected through environment variables
- C) Config should only be managed in XML files
- D) Config should be embedded in the application binary
Answer and Explanation
Answer: B) Config should be injected through environment variables
The 12-Factor App's III. Config principle recommends completely separating config from code and injecting it through environment variables. This allows the same codebase to be deployed across different environments (development, staging, production).
Question 3. Sidecar Pattern
What is the representative use case of the Sidecar pattern in Kubernetes?
- A) Doubles the CPU of the main container
- B) Deploys log collection, proxy, and monitoring agents alongside the main container
- C) Automatically migrates the Pod to another node
- D) Automatically restarts the main container
Answer and Explanation
Answer: B) Deploys log collection, proxy, and monitoring agents alongside the main container
The Sidecar pattern deploys auxiliary containers in the same Pod as the main application container to provide supplementary features like logging, proxying, and config synchronization. Istio's Envoy proxy is a classic example.
Question 4. Ambassador Pattern
What is the primary role of the Ambassador pattern?
- A) Acts as a proxy mediating the application's external communication
- B) Performs load balancing between Pods
- C) Manages cluster DNS
- D) Mounts storage volumes
Answer and Explanation
Answer: A) Acts as a proxy mediating the application's external communication
The Ambassador pattern mediates communication with external services on behalf of the application. It handles connection retries, logging, authentication, and is used for legacy protocol translation or circuit breaker implementation.
Question 5. Service Mesh Concepts
What role does the Data Plane of a service mesh perform?
- A) Policy definition and service discovery configuration
- B) Actually processes network traffic beside each service instance
- C) Performs certificate issuance and key management
- D) Automates cluster upgrades
Answer and Explanation
Answer: B) Actually processes network traffic beside each service instance
A service mesh consists of a control plane and data plane. The data plane (e.g., Envoy proxy) is deployed beside each service instance to handle actual network traffic routing, load balancing, mTLS, and observability.
Question 6. GitOps vs Traditional CI/CD
What is the key difference between GitOps and traditional push-based CI/CD?
- A) It uses Jenkins
- B) It uses Git as the single source of truth and synchronizes to the cluster using a Pull-based approach
- C) It only allows manual deployments
- D) It does not build container images
Answer and Explanation
Answer: B) It uses Git as the single source of truth and synchronizes to the cluster using a Pull-based approach
GitOps uses the Git repository as the Single Source of Truth for the desired state, and agents (e.g., Flux, ArgoCD) continuously synchronize cluster state with Git. Unlike push-based CI/CD, the cluster itself pulls the desired state.
Question 7. eBPF Technology
Which statement about eBPF (extended Berkeley Packet Filter) is correct?
- A) It is a type of container runtime
- B) It is a technology that enables running programs safely inside the Linux kernel
- C) It is a Kubernetes storage driver
- D) It is a DNS server implementation
Answer and Explanation
Answer: B) It is a technology that enables running programs safely inside the Linux kernel
eBPF enables running sandboxed programs within the Linux kernel without modifying kernel source code or loading kernel modules. It allows implementing networking, security, and observability features. Cilium, Falco, and Tetragon leverage eBPF.
Question 8. WebAssembly (Wasm) and Kubernetes
What is the benefit of using WebAssembly in Kubernetes?
- A) Image sizes are always larger than traditional containers
- B) Provides millisecond-level cold starts and sandbox isolation
- C) Only works on x86 architecture
- D) Cannot use network functionality
Answer and Explanation
Answer: B) Provides millisecond-level cold starts and sandbox isolation
Wasm provides millisecond cold starts, small binary sizes, and strong sandbox isolation. Through SpinKube, WasmEdge, and similar tools, Wasm workloads can run on Kubernetes, making it ideal for serverless and edge computing.
Question 9. Backstage
What is the core feature of Backstage?
- A) Container image build tool
- B) Internal Developer Portal (IDP) that provides unified management of service catalogs, templates, and documentation
- C) Kubernetes cluster monitoring tool
- D) CI/CD pipeline execution engine
Answer and Explanation
Answer: B) Internal Developer Portal (IDP) that provides unified management of service catalogs, templates, and documentation
Backstage is a CNCF Incubating project started at Spotify, serving as a framework for building internal developer portals. It provides core features like the Software Catalog, Software Templates, and TechDocs, and is extensible through a plugin system.
Question 10. Crossplane
What is the primary role of Crossplane?
- A) Service mesh implementation
- B) Declaratively provisions and manages cloud infrastructure through the Kubernetes API
- C) Log collection and analysis tool
- D) Container image registry
Answer and Explanation
Answer: B) Declaratively provisions and manages cloud infrastructure through the Kubernetes API
Crossplane extends Kubernetes as a universal control plane to manage cloud resources from AWS, GCP, Azure, and others as Kubernetes custom resources. Through Compositions, it can provide team-specific infrastructure abstractions.
Question 11. Dapr
What is the core concept of Dapr (Distributed Application Runtime)?
- A) Container orchestration tool
- B) Provides building blocks (state management, Pub/Sub, service invocation) for distributed applications as a sidecar
- C) Kubernetes cluster installation tool
- D) Static code analysis tool
Answer and Explanation
Answer: B) Provides building blocks (state management, Pub/Sub, service invocation) for distributed applications as a sidecar
Dapr is a runtime that simplifies microservice development using the sidecar pattern to provide language-agnostic building blocks for state management, Pub/Sub messaging, service invocation, bindings, and the actor model.
Question 12. CNCF Landscape Categories
Which tool belongs to the "Provisioning" category in the CNCF Landscape?
- A) Prometheus
- B) Terraform
- C) Jaeger
- D) Fluentd
Answer and Explanation
Answer: B) Terraform
The Provisioning category in the CNCF Landscape includes infrastructure automation, container registries, security, and compliance tools. Terraform is an infrastructure provisioning tool, while Prometheus is for monitoring, Jaeger for distributed tracing, and Fluentd for logging.
Question 13. OCI (Open Container Initiative)
Which is NOT an OCI specification?
- A) Image Spec
- B) Runtime Spec
- C) Distribution Spec
- D) Orchestration Spec
Answer and Explanation
Answer: D) Orchestration Spec
OCI defines three specifications: Image Spec (container image format), Runtime Spec (container runtime behavior), and Distribution Spec (image distribution API). Orchestration is not within OCI's scope.
Question 14. Serverless and Kubernetes
Which CNCF project enables running serverless workloads on Kubernetes?
- A) Knative
- B) Longhorn
- C) Thanos
- D) Harbor
Answer and Explanation
Answer: A) Knative
Knative is a platform for deploying, managing, and scaling serverless workloads on Kubernetes. It consists of Serving (auto-scaling, scale-to-zero) and Eventing (event-driven architecture) components and is a CNCF Incubating project.
Question 15. Flux vs ArgoCD Comparison
What feature do both Flux and ArgoCD support?
- A) Helm chart and Kustomize-based GitOps deployment
- B) Container image building
- C) Log collection and analysis
- D) Cluster provisioning
Answer and Explanation
Answer: A) Helm chart and Kustomize-based GitOps deployment
Both Flux and ArgoCD are GitOps tools that synchronize Helm charts, Kustomize, and plain YAML manifests to Kubernetes clusters based on Git repositories. ArgoCD provides a web UI by default, while Flux focuses on Git-based automation.
Question 16. CNCF Project Maturity Levels
What is a requirement for a CNCF project to be promoted to Graduated status?
- A) Over 1,000 GitHub stars
- B) Completed security audit and at least 2 production use cases
- C) Only one company needs to provide maintainers
- D) Must be at least 1 year since project inception
Answer and Explanation
Answer: B) Completed security audit and at least 2 production use cases
CNCF Graduated projects must complete an independent security audit and demonstrate production use cases across diverse organizations. They also require multi-organization maintainers, healthy governance structure, and community engagement.
Question 17. Three Pillars of Observability
What are the three core signals (Three Pillars) of cloud native observability?
- A) CPU, Memory, Disk
- B) Metrics, Logs, Distributed Traces
- C) Availability, Scalability, Security
- D) DNS, HTTP, gRPC
Answer and Explanation
Answer: B) Metrics, Logs, Distributed Traces
The three pillars of observability are Metrics (numerical measurements of system state), Logs (event records), and Distributed Traces (tracking the full path of requests). OpenTelemetry is the CNCF project that unifies these three.
Question 18. OpenTelemetry
Which statement about OpenTelemetry is correct?
- A) It is a metrics storage backend
- B) It is a vendor-neutral observability data collection framework
- C) It is a log visualization tool
- D) It is a service mesh implementation
Answer and Explanation
Answer: B) It is a vendor-neutral observability data collection framework
OpenTelemetry (OTel) is a vendor-neutral framework for generating, collecting, and transmitting metrics, logs, and distributed traces. It provides SDKs, APIs, and Collectors, and is one of the most active CNCF projects after Kubernetes.
Question 19. Adapter Pattern
What is the purpose of the cloud native Adapter pattern?
- A) Adjusts resource limits of containers
- B) Transforms the main container's output into a standard format
- C) Automatically replicates Pods
- D) Manages cluster network policies
Answer and Explanation
Answer: B) Transforms the main container's output into a standard format
The Adapter pattern uses a sidecar container to transform the main container's output (logs, metrics, etc.) into a standard format required by external systems. For example, it can convert custom application logs to JSON format or expose them in Prometheus metric format.
Question 20. Init Container Pattern
Which statement about Init Containers is correct?
- A) They run simultaneously with the main container
- B) They run sequentially before the main container starts, and must complete before the main container can begin
- C) They run after the main container terminates
- D) They are identical to Sidecar containers
Answer and Explanation
Answer: B) They run sequentially before the main container starts, and must complete before the main container can begin
Init Containers run in order before main containers, and each must complete successfully before proceeding to the next step. They are used for database migrations, configuration file generation, dependency waiting, and more.
Question 21. CNCF's Cloud Native Definition
Which is NOT a core characteristic of Cloud Native as defined by CNCF?
- A) Loosely Coupled systems
- B) Resilient and Manageable
- C) Monolithic Architecture Required
- D) Observable
Answer and Explanation
Answer: C) Monolithic Architecture Required
CNCF defines Cloud Native as an approach to building systems that are loosely coupled, resilient, manageable, and observable, leveraging containers, service mesh, microservices, immutable infrastructure, and declarative APIs.
Question 22. Helm vs Kustomize
What is the key difference between Helm and Kustomize?
- A) Helm is template-based, Kustomize is overlay (patch) based
- B) Only Kustomize can be used with Kubernetes
- C) Helm does not support YAML
- D) Both tools use the same approach
Answer and Explanation
Answer: A) Helm is template-based, Kustomize is overlay (patch) based
Helm creates parameterized charts using Go templates, while Kustomize applies overlays (patches) on top of base YAML to manage environment-specific configurations. Kustomize is built into kubectl, and both tools can be used together.
Question 23. CRI (Container Runtime Interface)
Which statement about Kubernetes CRI is correct?
- A) An interface for building container images
- B) An interface that standardizes communication between kubelet and container runtimes
- C) An interface for network plugins
- D) An interface for storage drivers
Answer and Explanation
Answer: B) An interface that standardizes communication between kubelet and container runtimes
CRI defines a standardized gRPC interface for kubelet to communicate with various container runtimes (containerd, CRI-O, etc.). Since Kubernetes 1.24, Docker no longer directly implements CRI, so dockershim was removed.
Question 24. CNI (Container Network Interface)
What is the role of a CNI plugin?
- A) Container image storage
- B) Assigns network interfaces and IP addresses to Pods
- C) Manages container runtimes
- D) Mounts storage volumes
Answer and Explanation
Answer: B) Assigns network interfaces and IP addresses to Pods
CNI (Container Network Interface) is a standard for managing container network connectivity. CNI plugins like Calico, Cilium, Flannel, and Weave assign network interfaces to Pods, provide IP addresses, and enable Pod-to-Pod communication.
Question 25. CSI (Container Storage Interface)
What is the primary purpose of CSI?
- A) Enhances container security
- B) Enables storage vendors to develop storage plugins independently from Kubernetes
- C) Defines network policies
- D) Replaces container runtimes
Answer and Explanation
Answer: B) Enables storage vendors to develop storage plugins independently from Kubernetes
CSI is a standard interface that allows storage vendors to develop and deploy their own storage drivers without modifying Kubernetes core code. Longhorn, Rook-Ceph, and EBS CSI Driver implement CSI.
Question 26. Istio Ambient Mesh
What is the key feature of Istio Ambient Mesh?
- A) Requires sidecar proxies
- B) Provides service mesh functionality without sidecars through ztunnel and waypoint proxies
- C) Works without Kubernetes
- D) Only supports TCP traffic
Answer and Explanation
Answer: B) Provides service mesh functionality without sidecars through ztunnel and waypoint proxies
Istio Ambient Mesh is a new data plane mode without sidecars. It uses node-level ztunnel (L4 processing, mTLS) and optional waypoint proxies (L7 processing) to reduce resource overhead and simplify operations.
Question 27. Platform Engineering
What is the core goal of Platform Engineering?
- A) Making all developers manage infrastructure directly
- B) Building self-service Internal Developer Platforms (IDPs) to improve developer experience and productivity
- C) Completely eliminating the role of operations teams
- D) Forcing the use of a single programming language
Answer and Explanation
Answer: B) Building self-service Internal Developer Platforms (IDPs) to improve developer experience and productivity
Platform Engineering abstracts infrastructure and tool complexity to build Internal Developer Platforms (IDPs) where developers can use needed resources via self-service. Backstage, Crossplane, and ArgoCD are components used in IDPs.
Question 28. Cilium's Core Technology
What core technology differentiates Cilium from traditional CNI plugins?
- A) iptables-based packet filtering
- B) Kernel-level networking and observability using eBPF
- C) Userspace proxy-based processing
- D) VLAN-based network segmentation
Answer and Explanation
Answer: B) Kernel-level networking and observability using eBPF
Cilium leverages eBPF technology to handle networking, security, and observability at the kernel level. Instead of using iptables, it performs packet processing with eBPF programs, providing high performance and fine-grained policy control.
Question 29. Serverless on Kubernetes
What does "Scale to Zero" mean in serverless on Kubernetes?
- A) Shuts down all cluster nodes
- B) Scales down the workload's Pod count to 0 when there are no requests to save resources
- C) Reduces memory usage to 0
- D) Blocks all network traffic
Answer and Explanation
Answer: B) Scales down the workload's Pod count to 0 when there are no requests to save resources
Scale to Zero means reducing the number of Pods to 0 when there is no traffic, and automatically starting Pods when new requests arrive. Knative Serving provides this feature, and KEDA also supports similar functionality for specific event sources.
Question 30. CNCF TAG (Technical Advisory Group)
What is the role of CNCF TAGs?
- A) Directly develops code for CNCF projects
- B) Provides guidelines, recommendations, and ecosystem direction for specific technical domains
- C) Sells tickets for CNCF events
- D) Manages Kubernetes releases
Answer and Explanation
Answer: B) Provides guidelines, recommendations, and ecosystem direction for specific technical domains
CNCF TAGs (Technical Advisory Groups) provide guidelines and recommendations to the community for specific technical domains such as security, observability, network, runtime, and app delivery. Examples include TAG Security, TAG Observability, and TAG Network.
Summary
These 30 questions are designed for in-depth study of the core KCNA exam domains: Kubernetes Fundamentals, Container Orchestration, Cloud Native Architecture, Cloud Native Observability, and Cloud Native Application Delivery. Since the actual exam requires a broad understanding of the CNCF ecosystem, be sure to thoroughly review the CNCF Landscape and the roles of each project.