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 4

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.

Question 31

A retailer's Pod is assigned to node-b but cannot start an application container. Which engineering approach is the most appropriate for this cloud-native case?

  1. Inspect FailedMount and PVC events, then verify StorageClass, PVC binding and node driver prerequisites before rewriting application code.
  2. Use a Deployment for a replicated stateless application requiring rolling updates and replacement of failed Pods.
  3. Use the scheduler's node-binding decision to explain initial Pod placement, then inspect the chosen node's kubelet for local container lifecycle status.
  4. Build an OCI-compatible image with immutable packaged artifacts and treat running container writable state as ephemeral.

Explanation

Correct Answer

C:

Use the scheduler's node-binding decision to explain initial Pod placement, then inspect the chosen node's kubelet for local container lifecycle status. This resolves the issue because the scheduler selects a suitable node for an unscheduled Pod; kubelet on that node uses the runtime to start and monitor containers. To verify, inspect a new Pod's nodeName and Events, then compare scheduling events with kubelet-reported container status.

Incorrect Answers

A:

This option addresses the distinct objective “Use Events and pod describe for failed volume mounting”, not the immediate requirement. Kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure. For the stated case, the scheduler selects a suitable node for an unscheduled Pod; kubelet on that node uses the runtime to start and monitor containers.

B:

This option addresses the distinct objective “Distinguish Deployment desired state from a manually created Pod”, not the immediate requirement. A Deployment owns ReplicaSets that manage matching Pods and supports declarative rollout history, unlike an independent Pod object. For the stated case, the scheduler selects a suitable node for an unscheduled Pod; kubelet on that node uses the runtime to start and monitor containers.

D:

This option addresses the distinct objective “Distinguish a container image from a running container and its writable layer”, not the immediate requirement. An image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage. For the stated case, the scheduler selects a suitable node for an unscheduled Pod; kubelet on that node uses the runtime to start and monitor containers.

Question 32

A retailer's Pod is assigned to node-b but cannot start an application container. What infrastructure principle makes the correct treatment effective?

  1. A supported runtime such as containerd executes container operations requested through kubelet using the Container Runtime Interface.
  2. The scheduler selects a suitable node for an unscheduled Pod; kubelet on that node uses the runtime to start and monitor containers.
  3. Tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label.
  4. Microservices permit independent deployment and scaling but introduce network dependencies and data consistency challenges; a monolith can remain appropriate for smaller teams.

Explanation

Correct Answer

B:

The scheduler selects a suitable node for an unscheduled Pod; kubelet on that node uses the runtime to start and monitor containers. It supports this action: Use the scheduler's node-binding decision to explain initial Pod placement, then inspect the chosen node's kubelet for local container lifecycle status. To confirm, inspect a new Pod's nodeName and Events, then compare scheduling events with kubelet-reported container status.

Incorrect Answers

A:

That statement explains the distinct objective “Explain the container runtime interface without conflating it with the control plane” rather than the cause in this case. The deciding mechanism here is that the scheduler selects a suitable node for an unscheduled Pod; kubelet on that node uses the runtime to start and monitor containers.

C:

That statement explains the distinct objective “Use an immutable image digest for exact deployment provenance” rather than the cause in this case. The deciding mechanism here is that the scheduler selects a suitable node for an unscheduled Pod; kubelet on that node uses the runtime to start and monitor containers.

D:

That statement explains the distinct objective “Contrast cloud-native microservices with a monolith without treating either as inherently superior” rather than the cause in this case. The deciding mechanism here is that the scheduler selects a suitable node for an unscheduled Pod; kubelet on that node uses the runtime to start and monitor containers.

Question 33

A retailer's Pod is assigned to node-b but cannot start an application container. What verification result would most convincingly distinguish a working solution from a claim?

  1. Inspect a new Pod's nodeName and Events, then compare scheduling events with kubelet-reported container status.
  2. Apply a preferred Pod affinity against a cache Pod label and inspect node placement while testing access policy separately.
  3. Test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.
  4. Scale a test Deployment and inspect its ReplicaSet and owned Pods, then compare deleting a standalone Pod.

Explanation

Correct Answer

A:

Inspect a new Pod's nodeName and Events, then compare scheduling events with kubelet-reported container status. This is the relevant test because the scheduler selects a suitable node for an unscheduled Pod; kubelet on that node uses the runtime to start and monitor containers.

Incorrect Answers

B:

This check would help evaluate the distinct objective “Use Pod affinity for co-location without assuming it creates networking permissions”, but not the required result. For this case, inspect a new Pod's nodeName and Events, then compare scheduling events with kubelet-reported container status.

C:

This check would help evaluate the distinct objective “Distinguish a failed Service selector from broken DNS or a failing backend”, but not the required result. For this case, inspect a new Pod's nodeName and Events, then compare scheduling events with kubelet-reported container status.

D:

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, inspect a new Pod's nodeName and Events, then compare scheduling events with kubelet-reported container status.

Question 34

A retailer's Pod is assigned to node-b but cannot start an application container. The change review contains this proposal: “Assume kube-scheduler directly runs and restarts every container on each node without a kubelet.” What risk matters most?

  1. The change is repeatedly reverted, making incident response and audit history inconsistent.
  2. Incident diagnosis confuses placement failures with container startup errors and targets the wrong component.
  3. Users may encounter failed requests because readiness and application-level health remain unverified.
  4. Controllers may fail to recognize intended Pods or adopt unwanted matches, producing confusing replacement behavior.

Explanation

Correct Answer

B:

Incident diagnosis confuses placement failures with container startup errors and targets the wrong component. The shortcut creates this risk because the scheduler selects a suitable node for an unscheduled Pod; kubelet on that node uses the runtime to start and monitor containers.

Incorrect Answers

A:

That outcome concerns the distinct objective “Apply GitOps reconciliation with a version-controlled desired state”; it is not the most direct consequence of this shortcut. The relevant consequence is that incident diagnosis confuses placement failures with container startup errors and targets the wrong component.

C:

That outcome concerns the distinct objective “Use kubectl get and describe for distinct inspection needs”; it is not the most direct consequence of this shortcut. The relevant consequence is that incident diagnosis confuses placement failures with container startup errors and targets the wrong component.

D:

That outcome concerns the distinct objective “Interpret ReplicaSet ownership and selectors in a Deployment”; it is not the most direct consequence of this shortcut. The relevant consequence is that incident diagnosis confuses placement failures with container startup errors and targets the wrong component.

Question 35

A retailer's Pod is assigned to node-b but cannot start an application container. Which implementation together with matching acceptance evidence best meets this case?

  1. 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.
  2. Inspect the relevant object's conditions and timestamped Events to place the failure at API admission, scheduling, image pulling or runtime startup. Acceptance evidence: Create synthetic invalid quota, unschedulable node and missing-image cases and compare their event reasons and assigned node status.
  3. 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.
  4. Cordon a worker to prevent new scheduling and drain safely under PodDisruptionBudgets and DaemonSet rules before maintenance. Acceptance evidence: Observe a controlled drain with replica owners and a PDB, then verify workloads move and uncordon restores eligibility.

Explanation

Correct Answer

C:

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. This pairing is justified because the scheduler selects a suitable node for an unscheduled Pod; kubelet on that node uses the runtime to start and monitor containers.

Incorrect Answers

A:

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 the scheduler's node-binding decision to explain initial Pod placement, then inspect the chosen node's kubelet for local container lifecycle status. Its confirming test is to inspect a new Pod's nodeName and Events, then compare scheduling events with kubelet-reported container status.

B:

This action and check address the distinct objective “Use describe and Events to distinguish admission, scheduling and execution errors” instead of the stated acceptance requirement. The matching action is to use the scheduler's node-binding decision to explain initial Pod placement, then inspect the chosen node's kubelet for local container lifecycle status. Its confirming test is to inspect a new Pod's nodeName and Events, then compare scheduling events with kubelet-reported container status.

D:

This action and check address the distinct objective “Use cordon and drain with disruption considerations for planned node maintenance” instead of the stated acceptance requirement. The matching action is to use the scheduler's node-binding decision to explain initial Pod placement, then inspect the chosen node's kubelet for local container lifecycle status. Its confirming test is to inspect a new Pod's nodeName and Events, then compare scheduling events with kubelet-reported container status.

Question 36

A college trainee needs to separate scheduler placement from local container execution in an example cluster. Which Kubernetes or cloud-native implementation decision best solves the stated problem?

  1. Grant operators only required API verbs and resources using RBAC, then test with kubectl auth can-i and separate synthetic identities.
  2. Combine a default-deny baseline with narrow app-label and namespace-label NetworkPolicy rules for approved traffic.
  3. Use the scheduler's node-binding decision to explain initial Pod placement, then inspect the chosen node's kubelet for local container lifecycle status.
  4. Assign related namespaced resources to a project namespace and enforce authorization and network isolation with separate policies.

Explanation

Correct Answer

C:

The situation is that a college trainee needs to separate scheduler placement from local container execution in an example cluster. Use the scheduler's node-binding decision to explain initial Pod placement, then inspect the chosen node's kubelet for local container lifecycle status. This resolves the issue because the scheduler selects a suitable node for an unscheduled Pod; kubelet on that node uses the runtime to start and monitor containers. To verify, inspect a new Pod's nodeName and Events, then compare scheduling events with kubelet-reported container status.

Incorrect Answers

A:

This option addresses the distinct objective “Use least-privilege kubectl authentication and authorization during routine administration”, not the immediate requirement. Authentication establishes who calls the API; RBAC authorization checks requested verb, resource and namespace before the API permits it. For the stated case, the scheduler selects a suitable node for an unscheduled Pod; kubelet on that node uses the runtime to start and monitor containers.

B:

This option addresses the distinct objective “Limit workload-to-workload access with explicit NetworkPolicy allow rules”, not the immediate requirement. NetworkPolicies select Pods and define allowed flows; when a Pod becomes isolated, traffic is allowed only as permitted by applicable rules and plugin behavior. For the stated case, the scheduler selects a suitable node for an unscheduled Pod; kubelet on that node uses the runtime to start and monitor containers.

D:

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 scheduler selects a suitable node for an unscheduled Pod; kubelet on that node uses the runtime to start and monitor containers.

Question 37

A college trainee needs to separate scheduler placement from local container execution in an example cluster. Which platform mechanism explains why the suitable approach works?

  1. etcd persists Kubernetes API objects and cluster configuration, while application records ordinarily live in workload-specific storage outside etcd.
  2. A Deployment owns ReplicaSets that manage matching Pods and supports declarative rollout history, unlike an independent Pod object.
  3. Image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout.
  4. The scheduler selects a suitable node for an unscheduled Pod; kubelet on that node uses the runtime to start and monitor containers.

Explanation

Correct Answer

D:

The situation is that a college trainee needs to separate scheduler placement from local container execution in an example cluster. The scheduler selects a suitable node for an unscheduled Pod; kubelet on that node uses the runtime to start and monitor containers. It supports this action: Use the scheduler's node-binding decision to explain initial Pod placement, then inspect the chosen node's kubelet for local container lifecycle status. To confirm, inspect a new Pod's nodeName and Events, then compare scheduling events with kubelet-reported container status.

Incorrect Answers

A:

That statement explains the distinct objective “Distinguish etcd persistence from running workload data” rather than the cause in this case. The deciding mechanism here is that the scheduler selects a suitable node for an unscheduled Pod; kubelet on that node uses the runtime to start and monitor containers.

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 scheduler selects a suitable node for an unscheduled Pod; kubelet on that node uses the runtime to start and monitor containers.

C:

That statement explains the distinct objective “Externalize application configuration from an image while protecting secrets” rather than the cause in this case. The deciding mechanism here is that the scheduler selects a suitable node for an unscheduled Pod; kubelet on that node uses the runtime to start and monitor containers.

Question 38

A college trainee needs to separate scheduler placement from local container execution in an example cluster. Which controlled observation would best validate the intended improvement?

  1. Deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.
  2. Create a namespaced ConfigMap with kubectl, read it back through the API, and confirm no manual edit of a worker-node process was required.
  3. Inspect a new Pod's nodeName and Events, then compare scheduling events with kubelet-reported container status.
  4. Describe a scheduled Pod with ImagePullBackOff and compare its assigned node against kubelet-related Events.

Explanation

Correct Answer

C:

The situation is that a college trainee needs to separate scheduler placement from local container execution in an example cluster. Inspect a new Pod's nodeName and Events, then compare scheduling events with kubelet-reported container status. This is the relevant test because the scheduler selects a suitable node for an unscheduled Pod; kubelet on that node uses the runtime to start and monitor containers.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Use image provenance and policy controls without trusting mutable tags”, but not the required result. For this case, inspect a new Pod's nodeName and Events, then compare scheduling events with kubelet-reported container status.

B:

This check would help evaluate the distinct objective “Trace Kubernetes API requests through the kube-apiserver entry point”, but not the required result. For this case, inspect a new Pod's nodeName and Events, then compare scheduling events with kubelet-reported container status.

D:

This check would help evaluate the distinct objective “Recognize the kubelet role in local Pod lifecycle management”, but not the required result. For this case, inspect a new Pod's nodeName and Events, then compare scheduling events with kubelet-reported container status.

Question 39

A college trainee needs to separate scheduler placement from local container execution in an example cluster. An engineer proposes: “Assume kube-scheduler directly runs and restarts every container on each node without a kubelet.” What adverse outcome would be most direct?

  1. Incident diagnosis confuses placement failures with container startup errors and targets the wrong component.
  2. The Pod continues restarting because Service DNS configuration is not the cause of the process exit.
  3. The emergency fix disappears when the Pod is replaced and cannot be reproduced reliably.
  4. The Service receives no intended ready endpoints even when healthy Pods exist.

Explanation

Correct Answer

A:

The situation is that a college trainee needs to separate scheduler placement from local container execution in an example cluster. Incident diagnosis confuses placement failures with container startup errors and targets the wrong component. The shortcut creates this risk because the scheduler selects a suitable node for an unscheduled Pod; kubelet on that node uses the runtime to start and monitor containers.

Incorrect Answers

B:

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 incident diagnosis confuses placement failures with container startup errors and targets the wrong component.

C:

That outcome concerns the distinct objective “Apply resource manifests declaratively instead of depending on imperative drift”; it is not the most direct consequence of this shortcut. The relevant consequence is that incident diagnosis confuses placement failures with container startup errors and targets the wrong component.

D:

That outcome concerns the distinct objective “Use labels and selectors to connect resources predictably”; it is not the most direct consequence of this shortcut. The relevant consequence is that incident diagnosis confuses placement failures with container startup errors and targets the wrong component.

Question 40

A college trainee needs to separate scheduler placement from local container execution in an example cluster. What pair of supported action and practical verification should be approved?

  1. Follow a project's published governance, issue templates, contributor guides and code of conduct when reporting bugs or proposing changes. Acceptance evidence: Submit a reproducible synthetic issue and examine how maintainers triage, review and test a proposed patch before release.
  2. Group tightly coupled containers that require the same Pod networking identity and optionally shared volumes into one Pod while keeping independently scalable services separate. Acceptance evidence: Deploy a test sidecar and main container, verify localhost communication and compare their shared Pod IP with a separate Pod.
  3. 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.
  4. Give each workload an appropriate Kubernetes ServiceAccount and narrow RBAC permissions rather than embedding an administrator kubeconfig in its image. Acceptance evidence: Run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.

Explanation

Correct Answer

C:

The situation is that a college trainee needs to separate scheduler placement from local container execution in an example cluster. 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. This pairing is justified because the scheduler selects a suitable node for an unscheduled Pod; kubelet on that node uses the runtime to start and monitor containers.

Incorrect Answers

A:

This action and check address the distinct objective “Use open community governance and contribution processes for sustainable cloud-native projects” instead of the stated acceptance requirement. The matching action is to use the scheduler's node-binding decision to explain initial Pod placement, then inspect the chosen node's kubelet for local container lifecycle status. Its confirming test is to inspect a new Pod's nodeName and Events, then compare scheduling events with kubelet-reported container status.

B:

This action and check address the distinct objective “Use Pods as the shared network and storage execution unit” instead of the stated acceptance requirement. The matching action is to use the scheduler's node-binding decision to explain initial Pod placement, then inspect the chosen node's kubelet for local container lifecycle status. Its confirming test is to inspect a new Pod's nodeName and Events, then compare scheduling events with kubelet-reported container status.

D:

This action and check address the distinct objective “Differentiate ServiceAccounts from human kubeconfig identities” instead of the stated acceptance requirement. The matching action is to use the scheduler's node-binding decision to explain initial Pod placement, then inspect the chosen node's kubelet for local container lifecycle status. Its confirming test is to inspect a new Pod's nodeName and Events, then compare scheduling events with kubelet-reported container status.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests