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 36

Question 350

A retail company adds branch Kubernetes nodes and wants a node-local metrics exporter automatically installed. Which implementation together with matching acceptance evidence best meets this case?

  1. Read a workload's spec and status separately and inspect conditions when determining whether an API change became healthy. Acceptance evidence: Apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.
  2. Run a logging or node monitoring agent as a DaemonSet when every eligible worker needs its own instance. Acceptance evidence: Add a test worker node and inspect the corresponding DaemonSet agent Pod without scaling a Deployment.
  3. Give clients a Service DNS name rather than hardcoding Pod IP addresses that can change when replicas are replaced. Acceptance evidence: Delete and replace a Deployment Pod and verify a client continues to reach its Service DNS name despite changed backend Pod addresses.
  4. 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.

Explanation

Correct Answer

B:

The situation is that a retail company adds branch Kubernetes nodes and wants a node-local metrics exporter automatically installed. Run a logging or node monitoring agent as a DaemonSet when every eligible worker needs its own instance. Acceptance evidence: Add a test worker node and inspect the corresponding DaemonSet agent Pod without scaling a Deployment. This pairing is justified because a DaemonSet controller targets eligible nodes for a Pod each, adapting to node additions and labels rather than maintaining a global arbitrary replica count.

Incorrect Answers

A:

This action and check address the distinct objective “Interpret Kubernetes spec and status fields without confusing intent with condition” instead of the stated acceptance requirement. The matching action is to run a logging or node monitoring agent as a DaemonSet when every eligible worker needs its own instance. Its confirming test is to add a test worker node and inspect the corresponding DaemonSet agent Pod without scaling a Deployment.

C:

This action and check address the distinct objective “Distinguish Pod IPs from stable Services during rescheduling” instead of the stated acceptance requirement. The matching action is to run a logging or node monitoring agent as a DaemonSet when every eligible worker needs its own instance. Its confirming test is to add a test worker node and inspect the corresponding DaemonSet agent Pod without scaling a Deployment.

D:

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 run a logging or node monitoring agent as a DaemonSet when every eligible worker needs its own instance. Its confirming test is to add a test worker node and inspect the corresponding DaemonSet agent Pod without scaling a Deployment.

Question 351

A student edits an application configuration file inside a Pod and loses the change after rollout. Which Kubernetes or cloud-native implementation decision best solves the stated problem?

  1. Pin validated production images by registry digest and promote the same signed artifact across environments.
  2. Label eligible nodes for a test hardware property and use nodeSelector when a Pod must run only on matching nodes.
  3. Build an OCI-compatible image with immutable packaged artifacts and treat running container writable state as ephemeral.
  4. 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.

Explanation

Correct Answer

C:

Build an OCI-compatible image with immutable packaged artifacts and treat running container writable state as ephemeral. This resolves the issue because an image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage. To verify, build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.

Incorrect Answers

A:

This option addresses the distinct objective “Use an immutable image digest for exact deployment provenance”, not the immediate requirement. Tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label. For the stated case, an image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage.

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, an image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage.

D:

This option addresses the distinct objective “Choose ReadWriteOnce and ReadWriteMany access modes by backend capability”, not the immediate requirement. PV access modes express volume mount constraints and driver support; ReadWriteOnce normally restricts writable use to one node, while ReadWriteMany requires a capable backend. For the stated case, an image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage.

Question 352

A student edits an application configuration file inside a Pod and loses the change after rollout. Which platform mechanism explains why the suitable approach works?

  1. kube-proxy can maintain node networking rules for Services, but supported network implementations may replace this function.
  2. An image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage.
  3. Kubernetes expects a Pod network providing Pod-to-Pod connectivity; the CNI implementation configures networking while Services provide stable virtual access to changing endpoints.
  4. Image-pull credentials are consumed before the application starts and should not be hardcoded into container layers or app logs.

Explanation

Correct Answer

B:

An image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage. It supports this action: Build an OCI-compatible image with immutable packaged artifacts and treat running container writable state as ephemeral. To confirm, build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.

Incorrect Answers

A:

That statement explains the distinct objective “Understand service proxy implementations without assuming kube-proxy is mandatory” rather than the cause in this case. The deciding mechanism here is that an image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage.

C:

That statement explains the distinct objective “Distinguish the CNI Pod network from Service discovery and routing” rather than the cause in this case. The deciding mechanism here is that an image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage.

D:

That statement explains the distinct objective “Handle private registry pulls with dedicated credentials instead of embedding secrets in images” rather than the cause in this case. The deciding mechanism here is that an image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage.

Question 353

A student edits an application configuration file inside a Pod and loses the change after rollout. 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. Build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.
  3. Resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.
  4. Write a synthetic temporary file into emptyDir, restart a container and then recreate the Pod to compare lifetime semantics.

Explanation

Correct Answer

B:

Build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears. This is the relevant test because an image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage.

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, build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.

C:

This check would help evaluate the distinct objective “Use an immutable image digest for exact deployment provenance”, but not the required result. For this case, build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.

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, build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.

Question 354

A student edits an application configuration file inside a Pod and loses the change after rollout. An engineer proposes: “Patch binaries manually inside a running container and assume the same patched bits automatically appear in newly started Pods.” What adverse outcome would be most direct?

  1. Replacing the Pod destroys the only copy of business state unless independent durable storage exists.
  2. The operator can interrupt healthy networking while the original admission or image problem persists.
  3. Replacement containers return to the unmodified image and reintroduce a fixed vulnerability or behavior.
  4. A leaked image layer or build log can disclose credentials and grant unwanted registry access.

Explanation

Correct Answer

C:

Replacement containers return to the unmodified image and reintroduce a fixed vulnerability or behavior. The shortcut creates this risk because an image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage.

Incorrect Answers

A:

That outcome concerns the distinct objective “Understand emptyDir as Pod-lifetime shared storage, not durable application persistence”; it is not the most direct consequence of this shortcut. The relevant consequence is that replacement containers return to the unmodified image and reintroduce a fixed vulnerability or behavior.

B:

That outcome concerns the distinct objective “Use describe and Events to distinguish admission, scheduling and execution errors”; it is not the most direct consequence of this shortcut. The relevant consequence is that replacement containers return to the unmodified image and reintroduce a fixed vulnerability or behavior.

D:

That outcome concerns the distinct objective “Handle private registry pulls with dedicated credentials instead of embedding secrets in images”; it is not the most direct consequence of this shortcut. The relevant consequence is that replacement containers return to the unmodified image and reintroduce a fixed vulnerability or behavior.

Question 355

A student edits an application configuration file inside a Pod and loses the change after rollout. What pair of supported action and practical verification should be approved?

  1. Build an OCI-compatible image with immutable packaged artifacts and treat running container writable state as ephemeral. Acceptance evidence: Build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.
  2. Use container runtime namespaces to isolate views of processes and networks while using cgroups to account for and constrain resources. Acceptance evidence: In a training namespace inspect PID views and a controlled memory limit, noting which mechanism changes identity or resource behavior.
  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. Combine a default-deny baseline with narrow app-label and namespace-label NetworkPolicy rules for approved traffic. Acceptance evidence: Test synthetic frontend-to-backend reachability and deny a third unauthorized namespace while verifying DNS access is still deliberately allowed.

Explanation

Correct Answer

A:

Build an OCI-compatible image with immutable packaged artifacts and treat running container writable state as ephemeral. Acceptance evidence: Build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears. This pairing is justified because an image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage.

Incorrect Answers

B:

This action and check address the distinct objective “Explain Linux namespaces and cgroups as distinct container isolation mechanisms” instead of the stated acceptance requirement. The matching action is to build an OCI-compatible image with immutable packaged artifacts and treat running container writable state as ephemeral. Its confirming test is to build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.

C:

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 build an OCI-compatible image with immutable packaged artifacts and treat running container writable state as ephemeral. Its confirming test is to build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.

D:

This action and check address the distinct objective “Limit workload-to-workload access with explicit NetworkPolicy allow rules” instead of the stated acceptance requirement. The matching action is to build an OCI-compatible image with immutable packaged artifacts and treat running container writable state as ephemeral. Its confirming test is to build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.

Question 356

A retail site ships a signed image and wants equivalent runtime contents across nodes. What technical action should the platform team take in this situation?

  1. Build an OCI-compatible image with immutable packaged artifacts and treat running container writable state as ephemeral.
  2. Use kubectl get for concise resource lists and kubectl describe for detailed status, conditions and Events when triaging a workload.
  3. Define post-release checks for readiness, error rate and latency, and revert an unhealthy revision using an approved rollout mechanism.
  4. Use emptyDir for temporary sharing between containers within a Pod, and PVC-backed storage when data must survive Pod replacement.

Explanation

Correct Answer

A:

The situation is that a retail site ships a signed image and wants equivalent runtime contents across nodes. Build an OCI-compatible image with immutable packaged artifacts and treat running container writable state as ephemeral. This resolves the issue because an image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage. To verify, build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.

Incorrect Answers

B:

This option addresses the distinct objective “Use kubectl get and describe for distinct inspection needs”, not the immediate requirement. Get returns selected object information, while describe adds human-readable state and related Events helpful for initial diagnosis. For the stated case, an image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage.

C:

This option addresses the distinct objective “Design a release rollback trigger from measurable service signals”, not the immediate requirement. A rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible. For the stated case, an image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage.

D:

This option addresses the distinct objective “Understand emptyDir as Pod-lifetime shared storage, not durable application persistence”, not the immediate requirement. EmptyDir is initialized for a Pod and its contents can be shared among containers but do not survive the Pod's removal. For the stated case, an image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage.

Question 357

A retail site ships a signed image and wants equivalent runtime contents across nodes. What underlying Kubernetes behavior is most relevant to this technical decision?

  1. Image-pull credentials are consumed before the application starts and should not be hardcoded into container layers or app logs.
  2. Image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.
  3. An image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage.
  4. Tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label.

Explanation

Correct Answer

C:

The situation is that a retail site ships a signed image and wants equivalent runtime contents across nodes. An image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage. It supports this action: Build an OCI-compatible image with immutable packaged artifacts and treat running container writable state as ephemeral. To confirm, build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.

Incorrect Answers

A:

The situation is that a retail site ships a signed image and wants equivalent runtime contents across nodes. That statement explains the distinct objective “Handle private registry pulls with dedicated credentials instead of embedding secrets in images” rather than the cause in this case. The deciding mechanism here is that an image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage.

B:

That statement explains the distinct objective “Use image provenance and policy controls without trusting mutable tags” rather than the cause in this case. The deciding mechanism here is that an image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage.

D:

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 an image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage.

Question 358

A retail site ships a signed image and wants equivalent runtime contents across nodes. What acceptance check most directly confirms this requirement is met?

  1. Build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.
  2. Change a test Deployment field outside Git, observe drift and confirm reconciliation restores the reviewed Git value.
  3. Create a controlled test namespace with a tiny quota and verify a request exceeding aggregate limits is rejected.
  4. Inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting.

Explanation

Correct Answer

A:

The situation is that a retail site ships a signed image and wants equivalent runtime contents across nodes. Build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears. This is the relevant test because an image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage.

Incorrect Answers

B:

This check would help evaluate the distinct objective “Apply GitOps reconciliation with a version-controlled desired state”, but not the required result. For this case, build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.

C:

This check would help evaluate the distinct objective “Understand resource quotas and LimitRanges for namespace capacity governance”, but not the required result. For this case, build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.

D:

This check would help evaluate the distinct objective “Understand ENTRYPOINT and command overrides when a container exits immediately”, but not the required result. For this case, build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.

Question 359

A retail site ships a signed image and wants equivalent runtime contents across nodes. The team suggests: “Patch binaries manually inside a running container and assume the same patched bits automatically appear in newly started Pods.” Which failure should the reviewer anticipate?

  1. The container may enter a restart loop before completing initialization, prolonging unavailability.
  2. Replacement containers return to the unmodified image and reintroduce a fixed vulnerability or behavior.
  3. The reported reliability can look excellent while customer transactions routinely fail or exceed acceptable latency.
  4. A working dataplane may be needlessly modified, disrupting traffic that was already being forwarded correctly.

Explanation

Correct Answer

B:

The situation is that a retail site ships a signed image and wants equivalent runtime contents across nodes. Replacement containers return to the unmodified image and reintroduce a fixed vulnerability or behavior. The shortcut creates this risk because an image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage.

Incorrect Answers

A:

That outcome concerns the distinct objective “Understand readiness, liveness and startup probes as different signals”; it is not the most direct consequence of this shortcut. The relevant consequence is that replacement containers return to the unmodified image and reintroduce a fixed vulnerability or behavior.

C:

That outcome concerns the distinct objective “Use SLI and SLO measures to focus reliability objectives”; it is not the most direct consequence of this shortcut. The relevant consequence is that replacement containers return to the unmodified image and reintroduce a fixed vulnerability or behavior.

D:

That outcome concerns the distinct objective “Understand service proxy implementations without assuming kube-proxy is mandatory”; it is not the most direct consequence of this shortcut. The relevant consequence is that replacement containers return to the unmodified image and reintroduce a fixed vulnerability or behavior.

Question 360

A retail site ships a signed image and wants equivalent runtime contents across nodes. Which engineering change and test jointly addresses the scenario?

  1. Read a workload's spec and status separately and inspect conditions when determining whether an API change became healthy. Acceptance evidence: Apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.
  2. Build an OCI-compatible image with immutable packaged artifacts and treat running container writable state as ephemeral. Acceptance evidence: Build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.
  3. Recognize Kubernetes for orchestration, Prometheus for metrics, Envoy for data-plane proxying and Fluentd for log collection in the cloud-native landscape. Acceptance evidence: Build a study architecture diagram that connects each tool to its documented function and verify the expected data flow in a sample environment.
  4. Pin validated production images by registry digest and promote the same signed artifact across environments. Acceptance evidence: Resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.

Explanation

Correct Answer

B:

The situation is that a retail site ships a signed image and wants equivalent runtime contents across nodes. Build an OCI-compatible image with immutable packaged artifacts and treat running container writable state as ephemeral. Acceptance evidence: Build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears. This pairing is justified because an image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage.

Incorrect Answers

A:

This action and check address the distinct objective “Interpret Kubernetes spec and status fields without confusing intent with condition” instead of the stated acceptance requirement. The matching action is to build an OCI-compatible image with immutable packaged artifacts and treat running container writable state as ephemeral. Its confirming test is to build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.

C:

This action and check address the distinct objective “Identify CNCF ecosystem projects by their role rather than assuming all are Kubernetes core” instead of the stated acceptance requirement. The matching action is to build an OCI-compatible image with immutable packaged artifacts and treat running container writable state as ephemeral. Its confirming test is to build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.

D:

This action and check address the distinct objective “Use an immutable image digest for exact deployment provenance” instead of the stated acceptance requirement. The matching action is to build an OCI-compatible image with immutable packaged artifacts and treat running container writable state as ephemeral. Its confirming test is to build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests