Courseiva

KCNA · topic practice

Cloud Native Application Delivery practice questions

Cloud Native Application Delivery covers how applications are packaged, deployed, and kept in sync on Kubernetes. Questions test Deployments, rollouts and rollbacks, troubleshooting Pods stuck in CrashLoopBackOff, GitOps reconciliation with Argo CD or Flux, and feature-flag tooling such as OpenFeature or Flagsmith. Expect drag-and-drop ordering, multi-select, and tool-identification items.

Courseiva uses original exam-style practice questions designed for learning and revision. The goal is to understand the concepts, recognise exam patterns, and improve through explanations — not memorise copied exam dumps.

Editorial oversight:Johnson Ajibi· MSc IT Security, IEEE Senior Member
20 questionsDomain: Cloud Native Application Delivery
Practice 10 questionsBrowse domain →

What the exam tests

What to know about Cloud Native Application Delivery

Be able to order CrashLoopBackOff troubleshooting, explain Deployment rollout and rollback behavior, and match GitOps and feature-flag tools to their use cases. The key is understanding that GitOps agents continuously reconcile live cluster state to the Git-declared desired state.

Deployment objects managing ReplicaSets, rolling updates, rollbacks, and declarative desired state

Ordering kubectl troubleshooting steps for a Pod in CrashLoopBackOff, from describe to logs to events

GitOps tools like Argo CD and Flux continuously reconciling cluster state with a Git repository

Feature-flag management for cloud-native microservices, including OpenFeature and dedicated flag services

Why learners struggle

Why Cloud Native Application Delivery questions are commonly missed

NAT questions are missed when learners confuse the four address types (inside local, inside global, outside local, outside global) or misapply the interface direction. A translation rule can look correct but still fail if the ACL, interface, or direction is wrong.

  • ·Inside local vs inside global — inside local is the private source, inside global is the translated public address
  • ·PAT overloads — many sources share one public IP using unique port numbers
  • ·Interface direction — ip nat inside and ip nat outside must be on the correct interfaces
  • ·Static NAT vs dynamic NAT vs PAT — each serves a different use case
  • ·The NAT ACL identifies traffic to translate, not traffic to permit or deny
  • ·A missing translation can look like a routing problem if the interfaces are misconfigured

Watch out for

Common Cloud Native Application Delivery exam traps

  • ▸Confusing Deployments with ReplicaSets or StatefulSets, and missing that Deployments own ReplicaSets and support rollback history.
  • ▸Troubleshooting CrashLoopBackOff by deleting the Pod first instead of inspecting describe, logs, and events to find the root cause.
  • ▸Assuming GitOps pushes changes with kubectl or CI, rather than an in-cluster agent pulling and reconciling desired state from Git.

Practice set

Cloud Native Application Delivery questions

20 questions · select your answer, then reveal the explanation

Question 1mediummultiple choice
Read the full Cloud Native Application Delivery explanation →

A user reports that a ConfigMap update is not reflected in running pods. Which action should be taken to ensure pods receive the updated configuration?

Question 2hardmultiple choice
Read the full Cloud Native Application Delivery explanation →

Refer to the exhibit. The deployment myapp is updated from image myapp:1.0 to myapp:2.0. During the rollout, what is the maximum number of pods that will be unavailable at any given time?

Exhibit

apiVersion: apps/v1
kind: Deployment
metadata:
  name: myapp
spec:
  replicas: 3
  strategy:
    type: RollingUpdate
    rollingUpdate:
      maxSurge: 1
      maxUnavailable: 0
  selector:
    matchLabels:
      app: myapp
  template:
    metadata:
      labels:
        app: myapp
    spec:
      containers:
      - name: myapp
        image: myapp:1.0
        resources:
          requests:
            cpu: 500m
            memory: 256Mi
          limits:
            cpu: 1
            memory: 512Mi
---
apiVersion: v1
kind: Service
metadata:
  name: myapp-svc
spec:
  type: ClusterIP
  selector:
    app: myapp
  ports:
  - port: 80
    targetPort: 8080
---
apiVersion: autoscaling/v2
kind: HorizontalPodAutoscaler
metadata:
  name: myapp-hpa
spec:
  scaleTargetRef:
    apiVersion: apps/v1
    kind: Deployment
    name: myapp
  minReplicas: 3
  maxReplicas: 10
  metrics:
  - type: Resource
    resource:
      name: cpu
      target:
        type: Utilization
        averageUtilization: 70
Question 3hardmultiple choice
Read the full Cloud Native Application Delivery explanation →

Your organization runs a microservices application on a Kubernetes cluster with 5 worker nodes (each with 4 vCPU, 16GB RAM). The application consists of 20 microservices, each deployed as a Deployment with 3 replicas. Recently, after a new microservice 'inventory' was deployed with resource requests of 2 CPU and 4GB memory per pod, the cluster started experiencing pod scheduling failures. Many existing pods are in 'Pending' state with events indicating 'Insufficient cpu' or 'Insufficient memory'. The cluster has cluster autoscaling enabled (node pool ranging from 3 to 10 nodes), but new nodes are not being added quickly enough, and the existing nodes are heavily utilized. You need to resolve the scheduling failures while ensuring the inventory service can scale. Which course of action should you take?

Question 4hardmultiple choice
Read the full Cloud Native Application Delivery explanation →

A financial services company runs a critical trading application on Kubernetes. The application is deployed as a Deployment with 3 replicas. Each pod exposes metrics on port 8080 and uses a ConfigMap to load configuration. Recently, after a configuration change via a ConfigMap update, two of the three pods started crashing with an out-of-memory (OOM) error, while the third pod continues to run fine. The team verified that the ConfigMap was updated correctly and that the application code did not change. The pods have resource limits set: memory limit of 512Mi and request of 256Mi. The application's memory usage before the change was around 200Mi. The new configuration increases the in-memory cache size. The team suspects the issue is related to the configuration change. What is the best course of action?

Question 5easymultiple choice
Read the full Cloud Native Application Delivery explanation →

Refer to the exhibit. The deployment above is created, but the pods are not receiving traffic from the associated Service. The Service selector matches 'app: web'. The Service endpoints list is empty. What is the most likely cause?

Exhibit

Refer to the exhibit.

```
apiVersion: apps/v1
kind: Deployment
metadata:
  name: web-app
spec:
  replicas: 3
  selector:
    matchLabels:
      app: web
  template:
    metadata:
      labels:
        app: web
    spec:
      containers:
      - name: app
        image: nginx:1.21
        ports:
        - containerPort: 80
        readinessProbe:
          httpGet:
            path: /health
            port: 80
          initialDelaySeconds: 5
          periodSeconds: 10
```
Question 6mediummatching
Read the full Cloud Native Application Delivery explanation →

Match each Kubernetes resource to its primary purpose.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts
Matches

Smallest deployable unit containing one or more containers

Stable network endpoint to access a set of Pods

Stores non-sensitive configuration data as key-value pairs

Cluster-wide storage resource provisioned by an administrator

Manages external access to services, typically HTTP

Question 7mediummatching
Read the full Cloud Native Application Delivery explanation →

Match each CNCF project to its primary function.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts
Matches

Monitoring and alerting toolkit

High-performance proxy for service mesh

Package manager for Kubernetes

Distributed key-value store for cluster state

DNS server for service discovery in Kubernetes

Question 8mediummatching
Read the full Cloud Native Application Delivery explanation →

Match each Kubernetes networking concept to its description.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts
Matches

Default service type; exposes service on a cluster-internal IP

Exposes service on each node's IP at a static port

Exposes service externally using a cloud provider's load balancer

Service without a cluster IP; used for direct pod-to-pod communication

Implements traffic routing rules defined by Ingress resources

Question 9hardmultiple choice
Read the full Cloud Native Application Delivery explanation →

A team uses Helm to manage a complex application. They want to perform a release upgrade but keep a record of the previous release so they can roll back if needed. Which Helm command should they use?

Question 10mediummultiple choice
Read the full Cloud Native Application Delivery explanation →

In Flux, which controller is responsible for reconciling the desired state defined in a Git repository to the cluster?

Question 11mediummultiple choice
Read the full Cloud Native Application Delivery explanation →

A developer runs 'helm upgrade --install myapp ./mychart' and sees the release status is 'failed'. What is the most likely cause?

Question 12mediummulti select
Read the full Cloud Native Application Delivery explanation →

Which TWO statements are true about ArgoCD's health status?

Question 13mediummultiple choice
Read the full Cloud Native Application Delivery explanation →

In Kustomize, what is the purpose of an overlay?

Question 14mediummultiple choice
Read the full Cloud Native Application Delivery explanation →

Which DORA metric measures the percentage of deployments that cause a failure in production?

Question 15mediummultiple choice
Read the full Cloud Native Application Delivery explanation →

An application deployment in Kubernetes uses a Deployment object. During a rolling update, the new ReplicaSet fails to become healthy. What is the default behavior of the Deployment controller?

Question 16mediummultiple choice
Read the full Cloud Native Application Delivery explanation →

Which tool can be used to implement feature flags in a Kubernetes-native progressive delivery setup?

Question 17hardmulti select
Read the full Cloud Native Application Delivery explanation →

Which THREE of the following are key capabilities of progressive delivery tools like Argo Rollouts?

Question 18hardmultiple choice
Read the full Cloud Native Application Delivery explanation →

A team uses Argo Rollouts for progressive delivery. They configure a canary rollout with a traffic split of 20% to the new version. After verification, the rollout automatically increases traffic to 100%. Which Argo Rollout manifest field controls this gradual traffic increase?

Question 19mediummultiple choice
Read the full Cloud Native Application Delivery explanation →

A team uses Flux to manage GitOps. Which Flux component is responsible for reconciling the cluster state with the desired state defined in a Git repository?

Question 20easymultiple choice
Read the full Cloud Native Application Delivery explanation →

What is the primary purpose of a container registry in a CI/CD pipeline?

Continue with 20-question session →

Free account

Track your progress over time

Create a free account to save your results and see which topics improve across sessions.

Sign up freeLog in

Focused Cloud Native Application Delivery sessions

Start a Cloud Native Application Delivery only practice session

Every question in these sessions is drawn from the Cloud Native Application Delivery domain — nothing else.

10 questions20 questions30 questions50 questions
Browse all Cloud Native Application Delivery questions →Mixed KCNA session

Related practice questions

Related KCNA topic practice pages

Move into related areas when this topic feels solid.

Kubernetes Fundamentals practice questions

Work through KCNA questions on Kubernetes Fundamentals.

Container Orchestration practice questions

Practise KCNA questions linked to Container Orchestration.

Cloud Native Architecture practice questions

Cloud Native Architecture practice questions for KCNA.

Cloud Native Observability practice questions

Cloud Native Observability practice questions for KCNA.

Cloud Native Application Delivery practice questions

Work through KCNA questions on Cloud Native Application Delivery.

KCNA fundamentals practice questions

Targeted KCNA practice covering KCNA fundamentals.

KCNA scenario practice questions

KCNA scenario practice questions for KCNA.

KCNA troubleshooting practice questions

Work through KCNA questions on KCNA troubleshooting.

Frequently asked questions

What does the KCNA exam test about Cloud Native Application Delivery?
Be able to order CrashLoopBackOff troubleshooting, explain Deployment rollout and rollback behavior, and match GitOps and feature-flag tools to their use cases. The key is understanding that GitOps agents continuously reconcile live cluster state to the Git-declared desired state.
How should I use these practice questions?
Select your answer before revealing the explanation. Then read why each option is right or wrong — this active recall approach builds retention far faster than re-reading notes.
Can I practise just Cloud Native Application Delivery questions in a focused session?
Yes — the session launcher on this page draws every question from the Cloud Native Application Delivery domain. Use a 10-question session first to gauge your baseline, then move to 20 or 30 once the weak spots are clear.
Where can I practise other KCNA topics?
Use the topic links above to move to related areas, or go back to the KCNA question bank to see all topics.
Are these real exam questions or dumps?
These are original practice questions written to test the same concepts the KCNA exam covers. They are not copied from any real exam or dump site.