KCNA Cloud Native Architecture Practice Test 12 — 15 Questions

Question 1

Which THREE of the following are components of the GitOps workflow? (Choose three.)

Accepted Answer

A CI/CD pipeline that validates changes before merging. GitOps relies on a Git repository as single source of truth, a CI/CD pipeline to validate changes, and an operator to sync the cluster.

Answer

A configuration management database (CMDB)

Answer

A manual approval process for every change

Question 2

Which THREE of the following are resiliency patterns commonly used in cloud native applications? (Choose three.)

Accepted Answer

Retry. The Retry pattern is a fundamental resiliency mechanism in cloud-native applications. When a transient failure occurs (e.g., a network timeout or a temporary database unavailability), the application automatically reattempts the failed operation. This pattern is often implemented with exponential backoff and jitter to avoid overwhelming the downstream service, as seen in libraries like Netflix Hystrix or Kubernetes client-go retry logic.

Answer

Singleton pattern

Answer

Round-robin load balancing

Question 3

Which TWO of the following are examples of Infrastructure as Code (IaC) tools? (Choose two.)

Accepted Answer

Terraform. Terraform (B) is an Infrastructure as Code (IaC) tool that uses declarative configuration files (HashiCorp Configuration Language, HCL) to define and provision cloud and on-premises resources. It manages the full lifecycle of infrastructure through a state file and provider plugins, enabling version-controlled, repeatable deployments.

Answer

Docker

Answer

Kubernetes

Answer

Prometheus

Question 4

Which TWO of the following are core principles of cloud native architecture according to the CNCF?

Accepted Answer

Microservices architecture. Options B and C are correct. Microservices architecture and dynamic orchestration are core principles of cloud native architecture according to the CNCF. Option A (static scaling) is not a core principle; cloud native emphasizes dynamic scaling. Option D (manual infrastructure management) contradicts the principle of automation. Option E (monolithic deployment) is antithetical to the microservices principle. Thus, the correct answers are B and C.

Answer

Static scaling based on predefined thresholds

Answer

Manual infrastructure management

Answer

Monolithic deployment

Question 5

Which THREE of the following are benefits of using a service mesh in a cloud native architecture?

Accepted Answer

Traffic management capabilities like canary deployments. Option B is correct because a service mesh provides layer-7 traffic management (e.g., weighted routing, header-based routing) that enables canary deployments and blue/green releases without changing application code. Option D is correct because service meshes like Istio and Linkerd automatically provision and rotate mutual TLS (mTLS) certificates between sidecar proxies, giving strong service-to-service authentication and encryption. Option E is correct because sidecar proxies emit uniform telemetry—request metrics, distributed traces, and access logs—across all services, improving observability without per-service instrumentation. Option A is not a service mesh benefit: application state management is handled by databases, caches, or stateful orchestration, not by the mesh's data plane. Option C is also incorrect because the mesh adds sidecar proxies and control-plane components, which tend to increase rather than reduce container image sizes.

Answer

Management of application state across services

Answer

Reduction of container image sizes

Question 6

An organization uses GitOps with ArgoCD to manage Kubernetes deployments. What is the PRIMARY advantage of this approach over traditional imperative deployment methods?

Accepted Answer

It provides a single source of truth for cluster state through Git. GitOps uses a Git repository as the single source of truth, enabling declarative configuration, version control, and automated reconciliation. This is the primary advantage over traditional imperative methods. Option A is incorrect because manual approval processes can still be part of a GitOps workflow. Option C is incorrect because GitOps does not eliminate the need for access controls. Option D is incorrect because GitOps does not directly reduce container count.

Answer

It eliminates the need for any manual approval processes

Answer

It allows developers to directly access the Kubernetes cluster

Answer

It reduces the number of containers needed in a deployment

Question 7

A platform team is adopting cloud-native principles for a new microservices application. They want to ensure that each service can be independently deployed and scaled without affecting other services. Which design principle BEST supports this goal?

Accepted Answer

Loose coupling between services. Loose coupling is fundamental to cloud-native architecture because it allows each microservice to evolve, deploy, and scale independently. When services communicate through stable, well-defined interfaces and avoid shared state, teams can release changes without coordinating across the entire system. This autonomy is essential for rapid iteration and resilience in distributed environments.

Answer

Shared monolithic database for all services

Answer

Centralized orchestration of all service workflows

Answer

Synchronous request-response communication only

Question 8

A team is designing a cloud-native application and wants to ensure that the failure of a single availability zone does not cause a full outage. They deploy the application across multiple zones and configure the orchestrator to distribute replicas evenly. Which cloud-native architecture principle does this scenario primarily demonstrate?

Accepted Answer

Design for failure. The scenario describes spreading replicas across multiple availability zones so that a single zone failure does not cause a full outage. This is the essence of designing for failure, where redundancy and fault isolation are built into the architecture. While other principles like declarative configuration or loose coupling may also be present, they do not directly address surviving a zone-level failure.

Answer

Loose coupling

Answer

Declarative configuration

Answer

Immutable infrastructure

Question 9

A startup is building a cloud-native application and wants to adopt a packaging format that bundles application code and its dependencies into a single immutable artifact that can run consistently across environments. Which technology BEST meets this requirement?

Accepted Answer

Container image. Container images are the standard cloud-native packaging format because they encapsulate the application and its dependencies in an immutable, portable unit. This eliminates environment drift and ensures that what is tested is what runs in production. Orchestrators like Kubernetes can then schedule these images consistently across clusters.

Answer

Configuration management script

Answer

Virtual machine snapshot

Answer

Source code repository

Question 10

A startup is building a cloud-native application and wants to ensure that its services can be discovered and communicated with dynamically as they scale up and down. Which CNCF project provides a distributed key-value store that is commonly used for service discovery and configuration management in Kubernetes?

Accepted Answer

etcd. etcd is the correct choice because it is a distributed key-value store designed for reliable data storage, often used for service discovery and configuration management. In Kubernetes, etcd stores the entire cluster state, and many cloud-native applications use it directly for dynamic configuration and service registration. Its strong consistency and watch capabilities make it ideal for these tasks.

Answer

Prometheus

Answer

Jaeger

Answer

Fluentd

Question 11

A platform engineer is explaining the role of the Kubernetes API server in a cloud-native architecture. Which statement BEST describes its primary function?

Accepted Answer

It serves as the central management endpoint that validates and processes REST requests for cluster resources.. The Kubernetes API server acts as the central management endpoint for the cluster. It exposes the Kubernetes API, authenticates and authorizes requests, validates resource configurations, and persists state to etcd. Other control plane components and user tools like kubectl communicate exclusively through it, so it is the single point of interaction for cluster operations.

Answer

It schedules pods to nodes based on resource availability.

Answer

It provides a distributed key-value store for cluster state.

Answer

It monitors the health of nodes and restarts failed containers.

Question 12

A platform team is designing a system that must continue serving requests for a product catalog even if the recommendation service becomes unavailable. The recommendation service calls the catalog service to fetch item details, and when it fails, the catalog service should keep responding to user traffic. Which cloud-native architecture principle BEST describes the required behavior for the catalog service?

Accepted Answer

Design for failure and graceful degradation of non-critical dependencies. The catalog service must remain available even when the recommendation service fails. That requires treating the recommendation dependency as non-critical and designing for failure, so the catalog service can degrade gracefully rather than propagate the failure. The other choices either change communication style, scale the wrong service, or introduce tighter coupling, none of which satisfies the requirement.

Answer

Storing all catalog and recommendation data in a single shared relational database

Answer

Vertical scaling of the recommendation service to handle peak load

Answer

Loose coupling through asynchronous, queue-based communication

Question 13

A team is deploying a microservices application on Kubernetes. They want to ensure that each microservice can be updated independently without affecting others, and that the application can tolerate the failure of a single microservice. Which cloud-native architecture principle are they applying?

Accepted Answer

Microservices architecture. Microservices architecture is the correct principle because it structures an application as a collection of loosely coupled services, each independently deployable and scalable. This allows teams to update one service without redeploying others, and a failure in one service can be isolated, preventing cascading failures. The scenario highlights these exact benefits, aligning with microservices principles.

Answer

Monolithic architecture

Answer

Serverless architecture

Answer

Service mesh

Question 14

A team is designing a cloud-native system that must remain available even if an entire availability zone fails. They want to distribute workloads across multiple zones and automatically recover from failures. Which cloud-native architectural approach BEST addresses this requirement?

Accepted Answer

Use a multi-zone cluster with anti-affinity rules and health checks. Spreading workloads across multiple availability zones with anti-affinity and health checks enables the system to tolerate a zone failure. Kubernetes can reschedule pods from a failed zone onto nodes in healthy zones, maintaining service. This design is a standard cloud-native pattern for high availability.

Answer

Rely on vertical scaling of a single large node

Answer

Store all state in a single-zone database

Answer

Deploy all replicas in a single zone with a load balancer

Question 15

A company is adopting cloud-native architecture and wants to improve the resilience of its applications. Which TWO of the following are core principles of cloud-native architecture that directly contribute to resilience? (Choose two.)

Accepted Answer

Design for failure and automate recovery.. Designing for failure and automating recovery, along with implementing observability, are core cloud-native principles that directly enhance resilience. Designing for failure ensures that systems can withstand component outages and recover automatically, while observability provides the visibility needed to detect and respond to issues. Together, they enable applications to maintain availability and performance in dynamic environments.

Answer

Store all application state in a single centralized database.

Answer

Manually scale resources based on peak load forecasts.

Answer

Use monolithic deployments to simplify troubleshooting.