Practice Exams:

Linux Foundation KCNA Dumps

EXAM: Kubernetes and Cloud Native Associate
Verified By Experts
Premium Bundle
$40.00
$59.97 $99.97

KCNA Premium Bundle


  • Premium File 333 Questions & Answers
  • Training Course 54 Lectures
  • Study Guide 410 Pages

Linux Foundation KCNA Practice Test 3

Question 20

A regional hospital confuses control-plane state snapshots with backups of its medical application files. What pair of supported action and practical verification should be approved?

  1. Inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count. Acceptance evidence: Run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.
  2. Select an access mode supported by the actual storage driver and workload placement requirements rather than assuming every volume supports concurrent writes from every node. Acceptance evidence: Use a synthetic two-node workload and compare expected attach behavior for an RWO volume with a documented RWX shared filesystem.
  3. Choose Pod affinity only when co-locating related workloads is beneficial and verify independent network policies still govern traffic. Acceptance evidence: Apply a preferred Pod affinity against a cache Pod label and inspect node placement while testing access policy separately.
  4. Treat etcd as Kubernetes control-plane state storage and protect its snapshots, keys, and access separately from an application's database or PVC. Acceptance evidence: Inspect the cluster backup policy for etcd snapshots and separately restore synthetic application data from its own backup.

Explanation

Correct Answer

D:

The situation is that a regional hospital confuses control-plane state snapshots with backups of its medical application files. Treat etcd as Kubernetes control-plane state storage and protect its snapshots, keys, and access separately from an application's database or PVC. Acceptance evidence: Inspect the cluster backup policy for etcd snapshots and separately restore synthetic application data from its own backup. This pairing is justified because etcd persists Kubernetes API objects and cluster configuration, while application records ordinarily live in workload-specific storage outside etcd.

Incorrect Answers

A:

This action and check address the distinct objective “Interpret ReplicaSet ownership and selectors in a Deployment” instead of the stated acceptance requirement. The matching action is to treat etcd as Kubernetes control-plane state storage and protect its snapshots, keys, and access separately from an application's database or PVC. Its confirming test is to inspect the cluster backup policy for etcd snapshots and separately restore synthetic application data from its own backup.

B:

This action and check address the distinct objective “Choose ReadWriteOnce and ReadWriteMany access modes by backend capability” instead of the stated acceptance requirement. The matching action is to treat etcd as Kubernetes control-plane state storage and protect its snapshots, keys, and access separately from an application's database or PVC. Its confirming test is to inspect the cluster backup policy for etcd snapshots and separately restore synthetic application data from its own backup.

C:

This action and check address the distinct objective “Use Pod affinity for co-location without assuming it creates networking permissions” instead of the stated acceptance requirement. The matching action is to treat etcd as Kubernetes control-plane state storage and protect its snapshots, keys, and access separately from an application's database or PVC. Its confirming test is to inspect the cluster backup policy for etcd snapshots and separately restore synthetic application data from its own backup.

Question 21

An online school wants three front-end replicas restored automatically after a worker disruption. What technical action should the platform team take in this situation?

  1. Assign related namespaced resources to a project namespace and enforce authorization and network isolation with separate policies.
  2. Label eligible nodes for a test hardware property and use nodeSelector when a Pod must run only on matching nodes.
  3. Use Kubernetes controllers to keep replicas and other managed resources aligned with their declared specifications rather than manually re-creating each missing pod.
  4. Verify that the installed Container Storage Interface driver supports the requested persistent storage and inspect driver controller/node components when mounting fails.

Explanation

Correct Answer

C:

Use Kubernetes controllers to keep replicas and other managed resources aligned with their declared specifications rather than manually re-creating each missing pod. This resolves the issue because the controller manager runs controllers that observe API resources and make changes so current state moves toward desired state. To verify, delete one test Deployment-owned Pod and observe a replacement appear without a new Deployment definition.

Incorrect Answers

A:

This option addresses the distinct objective “Use namespaces as organizational scopes without treating them as firewalls”, not the immediate requirement. A namespace scopes many API object names and administrative boundaries, but merely creating it does not deny network communication across namespaces. For the stated case, the controller manager runs controllers that observe API resources and make changes so current state moves toward desired state.

B:

This option addresses the distinct objective “Use nodeSelector to place a workload on nodes with required labels”, not the immediate requirement. The scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities. For the stated case, the controller manager runs controllers that observe API resources and make changes so current state moves toward desired state.

D:

This option addresses the distinct objective “Understand CSI drivers and volume attachment responsibilities”, not the immediate requirement. CSI separates storage vendor implementation from Kubernetes core and manages provisioning, attachment and node mounting through driver-defined capabilities. For the stated case, the controller manager runs controllers that observe API resources and make changes so current state moves toward desired state.

Question 22

An online school wants three front-end replicas restored automatically after a worker disruption. What underlying Kubernetes behavior is most relevant to this technical decision?

  1. The controller manager runs controllers that observe API resources and make changes so current state moves toward desired state.
  2. A deployment pipeline is a trust boundary; signed artifacts and automated policy tests reduce the risk of unreviewed configurations reaching production.
  3. Each kubelet watches assigned Pod specifications and coordinates the container runtime, volumes and health information on its node.
  4. Pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.

Explanation

Correct Answer

A:

The controller manager runs controllers that observe API resources and make changes so current state moves toward desired state. It supports this action: Use Kubernetes controllers to keep replicas and other managed resources aligned with their declared specifications rather than manually re-creating each missing pod. To confirm, delete one test Deployment-owned Pod and observe a replacement appear without a new Deployment definition.

Incorrect Answers

B:

That statement explains the distinct objective “Define secure release governance with staged approvals and policy verification” rather than the cause in this case. The deciding mechanism here is that the controller manager runs controllers that observe API resources and make changes so current state moves toward desired state.

C:

That statement explains the distinct objective “Recognize the kubelet role in local Pod lifecycle management” rather than the cause in this case. The deciding mechanism here is that the controller manager runs controllers that observe API resources and make changes so current state moves toward desired state.

D:

That statement explains the distinct objective “Use Pod affinity for co-location without assuming it creates networking permissions” rather than the cause in this case. The deciding mechanism here is that the controller manager runs controllers that observe API resources and make changes so current state moves toward desired state.

Question 23

An online school wants three front-end replicas restored automatically after a worker disruption. What acceptance check most directly confirms this requirement is met?

  1. Delete one test Deployment-owned Pod and observe a replacement appear without a new Deployment definition.
  2. Scale a test Deployment and inspect its ReplicaSet and owned Pods, then compare deleting a standalone Pod.
  3. Create two controlled faulty workloads, one requiring an impossible node label and one referencing a missing image tag, then compare Events.
  4. Write a synthetic temporary file into emptyDir, restart a container and then recreate the Pod to compare lifetime semantics.

Explanation

Correct Answer

A:

Delete one test Deployment-owned Pod and observe a replacement appear without a new Deployment definition. This is the relevant test because the controller manager runs controllers that observe API resources and make changes so current state moves toward desired state.

Incorrect Answers

B:

This check would help evaluate the distinct objective “Distinguish Deployment desired state from a manually created Pod”, but not the required result. For this case, delete one test Deployment-owned Pod and observe a replacement appear without a new Deployment definition.

C:

This check would help evaluate the distinct objective “Separate Pending scheduling failures from ImagePullBackOff errors”, but not the required result. For this case, delete one test Deployment-owned Pod and observe a replacement appear without a new Deployment definition.

D:

This check would help evaluate the distinct objective “Understand emptyDir as Pod-lifetime shared storage, not durable application persistence”, but not the required result. For this case, delete one test Deployment-owned Pod and observe a replacement appear without a new Deployment definition.

Question 24

An online school wants three front-end replicas restored automatically after a worker disruption. The team suggests: “Create unmanaged one-off pods and claim they automatically replace themselves after a node fails.” Which failure should the reviewer anticipate?

  1. A later registry push can change deployed bits unexpectedly, defeating reproducible approval and rollback.
  2. The service can remain under capacity because a standalone Pod has no ReplicaSet controller to recreate it.
  3. Independent rollout, scaling and failure isolation become difficult because the services are coupled to one scheduling unit.
  4. The Pod continues restarting because Service DNS configuration is not the cause of the process exit.

Explanation

Correct Answer

B:

The service can remain under capacity because a standalone Pod has no ReplicaSet controller to recreate it. The shortcut creates this risk because the controller manager runs controllers that observe API resources and make changes so current state moves toward desired state.

Incorrect Answers

A:

That outcome concerns the distinct objective “Use an immutable image digest for exact deployment provenance”; it is not the most direct consequence of this shortcut. The relevant consequence is that the service can remain under capacity because a standalone Pod has no ReplicaSet controller to recreate it.

C:

That outcome concerns the distinct objective “Use Pods as the shared network and storage execution unit”; it is not the most direct consequence of this shortcut. The relevant consequence is that the service can remain under capacity because a standalone Pod has no ReplicaSet controller to recreate it.

D:

That outcome concerns the distinct objective “Diagnose CrashLoopBackOff from restart history and previous logs”; it is not the most direct consequence of this shortcut. The relevant consequence is that the service can remain under capacity because a standalone Pod has no ReplicaSet controller to recreate it.

Question 25

An online school wants three front-end replicas restored automatically after a worker disruption. Which engineering change and test jointly addresses the scenario?

  1. Change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation. Acceptance evidence: Set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.
  2. Verify that the installed Container Storage Interface driver supports the requested persistent storage and inspect driver controller/node components when mounting fails. Acceptance evidence: Inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload.
  3. Configure anti-affinity against other Pods with a specific label so replicas prefer or require separate failure domains as appropriate. Acceptance evidence: Deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.
  4. Use Kubernetes controllers to keep replicas and other managed resources aligned with their declared specifications rather than manually re-creating each missing pod. Acceptance evidence: Delete one test Deployment-owned Pod and observe a replacement appear without a new Deployment definition.

Explanation

Correct Answer

D:

Use Kubernetes controllers to keep replicas and other managed resources aligned with their declared specifications rather than manually re-creating each missing pod. Acceptance evidence: Delete one test Deployment-owned Pod and observe a replacement appear without a new Deployment definition. This pairing is justified because the controller manager runs controllers that observe API resources and make changes so current state moves toward desired state.

Incorrect Answers

A:

This action and check address the distinct objective “Explain desired state versus observed status in Kubernetes objects” instead of the stated acceptance requirement. The matching action is to use Kubernetes controllers to keep replicas and other managed resources aligned with their declared specifications rather than manually re-creating each missing pod. Its confirming test is to delete one test Deployment-owned Pod and observe a replacement appear without a new Deployment definition.

B:

This action and check address the distinct objective “Understand CSI drivers and volume attachment responsibilities” instead of the stated acceptance requirement. The matching action is to use Kubernetes controllers to keep replicas and other managed resources aligned with their declared specifications rather than manually re-creating each missing pod. Its confirming test is to delete one test Deployment-owned Pod and observe a replacement appear without a new Deployment definition.

C:

This action and check address the distinct objective “Use Pod anti-affinity to reduce correlated replica failure” instead of the stated acceptance requirement. The matching action is to use Kubernetes controllers to keep replicas and other managed resources aligned with their declared specifications rather than manually re-creating each missing pod. Its confirming test is to delete one test Deployment-owned Pod and observe a replacement appear without a new Deployment definition.

Question 26

A community health portal loses one managed application pod and needs to understand which component restores replica count. Which Kubernetes or cloud-native implementation decision best solves the stated problem?

  1. Choose a CRI-compatible container runtime on worker nodes and investigate image and container creation separately from API scheduling.
  2. Inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count.
  3. Use Kubernetes controllers to keep replicas and other managed resources aligned with their declared specifications rather than manually re-creating each missing pod.
  4. Use an authorized kubectl debug ephemeral container when an application image lacks troubleshooting tools and policy permits ephemeral containers.

Explanation

Correct Answer

C:

The situation is that a community health portal loses one managed application pod and needs to understand which component restores replica count. Use Kubernetes controllers to keep replicas and other managed resources aligned with their declared specifications rather than manually re-creating each missing pod. This resolves the issue because the controller manager runs controllers that observe API resources and make changes so current state moves toward desired state. To verify, delete one test Deployment-owned Pod and observe a replacement appear without a new Deployment definition.

Incorrect Answers

A:

This option addresses the distinct objective “Explain the container runtime interface without conflating it with the control plane”, not the immediate requirement. A supported runtime such as containerd executes container operations requested through kubelet using the Container Runtime Interface. For the stated case, the controller manager runs controllers that observe API resources and make changes so current state moves toward desired state.

B:

This option addresses the distinct objective “Interpret ReplicaSet ownership and selectors in a Deployment”, not the immediate requirement. A Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts. For the stated case, the controller manager runs controllers that observe API resources and make changes so current state moves toward desired state.

D:

This option addresses the distinct objective “Use ephemeral debugging containers only with appropriate permission and safeguards”, not the immediate requirement. An ephemeral container can join a Pod's namespaces for observation but is not a substitute for repairing the owning Deployment's desired configuration. For the stated case, the controller manager runs controllers that observe API resources and make changes so current state moves toward desired state.

Question 27

A community health portal loses one managed application pod and needs to understand which component restores replica count. Which platform mechanism explains why the suitable approach works?

  1. Containers in a Pod share a network namespace and IP address and can coordinate on localhost, while the Pod is scheduled as one unit.
  2. A Deployment owns ReplicaSets that manage matching Pods and supports declarative rollout history, unlike an independent Pod object.
  3. The controller manager runs controllers that observe API resources and make changes so current state moves toward desired state.
  4. CoreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains.

Explanation

Correct Answer

C:

The situation is that a community health portal loses one managed application pod and needs to understand which component restores replica count. The controller manager runs controllers that observe API resources and make changes so current state moves toward desired state. It supports this action: Use Kubernetes controllers to keep replicas and other managed resources aligned with their declared specifications rather than manually re-creating each missing pod. To confirm, delete one test Deployment-owned Pod and observe a replacement appear without a new Deployment definition.

Incorrect Answers

A:

That statement explains the distinct objective “Use Pods as the shared network and storage execution unit” rather than the cause in this case. The deciding mechanism here is that the controller manager runs controllers that observe API resources and make changes so current state moves toward desired state.

B:

That statement explains the distinct objective “Distinguish Deployment desired state from a manually created Pod” rather than the cause in this case. The deciding mechanism here is that the controller manager runs controllers that observe API resources and make changes so current state moves toward desired state.

D:

That statement explains the distinct objective “Verify CoreDNS resolution and namespace-qualified Service names” rather than the cause in this case. The deciding mechanism here is that the controller manager runs controllers that observe API resources and make changes so current state moves toward desired state.

Question 28

A community health portal loses one managed application pod and needs to understand which component restores replica count. Which controlled observation would best validate the intended improvement?

  1. Deploy a test sidecar and main container, verify localhost communication and compare their shared Pod IP with a separate Pod.
  2. Verify a synthetic exporter is listed UP in Prometheus target status and query its request counter after generating traffic.
  3. Delete one test Deployment-owned Pod and observe a replacement appear without a new Deployment definition.
  4. Deploy a test Pod with runAsNonRoot and verify its effective user and capability sets while confirming app file permissions work.

Explanation

Correct Answer

C:

The situation is that a community health portal loses one managed application pod and needs to understand which component restores replica count. Delete one test Deployment-owned Pod and observe a replacement appear without a new Deployment definition. This is the relevant test because the controller manager runs controllers that observe API resources and make changes so current state moves toward desired state.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Use Pods as the shared network and storage execution unit”, but not the required result. For this case, delete one test Deployment-owned Pod and observe a replacement appear without a new Deployment definition.

B:

This check would help evaluate the distinct objective “Understand Prometheus pull-based metrics collection and exporters”, but not the required result. For this case, delete one test Deployment-owned Pod and observe a replacement appear without a new Deployment definition.

D:

This check would help evaluate the distinct objective “Run images with least-privilege runtime security contexts”, but not the required result. For this case, delete one test Deployment-owned Pod and observe a replacement appear without a new Deployment definition.

Question 29

A community health portal loses one managed application pod and needs to understand which component restores replica count. An engineer proposes: “Create unmanaged one-off pods and claim they automatically replace themselves after a node fails.” What adverse outcome would be most direct?

  1. Replacing a Pod can destroy state because no independent persistent volume was requested.
  2. The service can remain under capacity because a standalone Pod has no ReplicaSet controller to recreate it.
  3. Independent rollout, scaling and failure isolation become difficult because the services are coupled to one scheduling unit.
  4. Sensitive workloads may remain reachable until actual identity and traffic controls are installed.

Explanation

Correct Answer

B:

The situation is that a community health portal loses one managed application pod and needs to understand which component restores replica count. The service can remain under capacity because a standalone Pod has no ReplicaSet controller to recreate it. The shortcut creates this risk because the controller manager runs controllers that observe API resources and make changes so current state moves toward desired state.

Incorrect Answers

A:

That outcome concerns the distinct objective “Understand PersistentVolumeClaim binding to persistent storage resources”; it is not the most direct consequence of this shortcut. The relevant consequence is that the service can remain under capacity because a standalone Pod has no ReplicaSet controller to recreate it.

C:

The situation is that a community health portal loses one managed application pod and needs to understand which component restores replica count. That outcome concerns the distinct objective “Use Pods as the shared network and storage execution unit”; it is not the most direct consequence of this shortcut. The relevant consequence is that the service can remain under capacity because a standalone Pod has no ReplicaSet controller to recreate it.

D:

That outcome concerns the distinct objective “Use namespaces as organizational scopes without treating them as firewalls”; it is not the most direct consequence of this shortcut. The relevant consequence is that the service can remain under capacity because a standalone Pod has no ReplicaSet controller to recreate it.

Question 30

A community health portal loses one managed application pod and needs to understand which component restores replica count. What pair of supported action and practical verification should be approved?

  1. Use the scheduler's node-binding decision to explain initial Pod placement, then inspect the chosen node's kubelet for local container lifecycle status. Acceptance evidence: Inspect a new Pod's nodeName and Events, then compare scheduling events with kubelet-reported container status.
  2. Use metrics for measurable trends, logs for event detail and distributed traces for individual transaction paths while sharing correlation identifiers. Acceptance evidence: Send a synthetic request with a correlation ID and confirm it appears in the trace and relevant logs while latency metrics change.
  3. Treat etcd as Kubernetes control-plane state storage and protect its snapshots, keys, and access separately from an application's database or PVC. Acceptance evidence: Inspect the cluster backup policy for etcd snapshots and separately restore synthetic application data from its own backup.
  4. Use Kubernetes controllers to keep replicas and other managed resources aligned with their declared specifications rather than manually re-creating each missing pod. Acceptance evidence: Delete one test Deployment-owned Pod and observe a replacement appear without a new Deployment definition.

Explanation

Correct Answer

D:

The situation is that a community health portal loses one managed application pod and needs to understand which component restores replica count. Use Kubernetes controllers to keep replicas and other managed resources aligned with their declared specifications rather than manually re-creating each missing pod. Acceptance evidence: Delete one test Deployment-owned Pod and observe a replacement appear without a new Deployment definition. This pairing is justified because the controller manager runs controllers that observe API resources and make changes so current state moves toward desired state.

Incorrect Answers

A:

This action and check address the distinct objective “Separate kube-scheduler decisions from kubelet execution” instead of the stated acceptance requirement. The matching action is to use Kubernetes controllers to keep replicas and other managed resources aligned with their declared specifications rather than manually re-creating each missing pod. Its confirming test is to delete one test Deployment-owned Pod and observe a replacement appear without a new Deployment definition.

B:

This action and check address the distinct objective “Explain metrics, logs and traces as complementary observability signals” instead of the stated acceptance requirement. The matching action is to use Kubernetes controllers to keep replicas and other managed resources aligned with their declared specifications rather than manually re-creating each missing pod. Its confirming test is to delete one test Deployment-owned Pod and observe a replacement appear without a new Deployment definition.

C:

This action and check address the distinct objective “Distinguish etcd persistence from running workload data” instead of the stated acceptance requirement. The matching action is to use Kubernetes controllers to keep replicas and other managed resources aligned with their declared specifications rather than manually re-creating each missing pod. Its confirming test is to delete one test Deployment-owned Pod and observe a replacement appear without a new Deployment definition.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests