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 18

Question 170

A hotel service team keeps modifying a live Pod shell instead of changing its Deployment definition. Which engineering change and test jointly addresses the scenario?

  1. Store approved declarative cluster manifests in Git and let a GitOps controller reconcile differences while keeping sensitive access appropriately scoped. Acceptance evidence: Change a test Deployment field outside Git, observe drift and confirm reconciliation restores the reviewed Git value.
  2. Label eligible nodes for a test hardware property and use nodeSelector when a Pod must run only on matching nodes. Acceptance evidence: Label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.
  3. Keep desired workload YAML in version control and use kubectl apply to reconcile supported object fields through the API. Acceptance evidence: Edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.
  4. Put non-sensitive application settings in ConfigMaps and put credentials in Secret objects with RBAC, encryption and external secret-management safeguards where appropriate. Acceptance evidence: Inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.

Explanation

Correct Answer

C:

The situation is that a hotel service team keeps modifying a live Pod shell instead of changing its Deployment definition. Keep desired workload YAML in version control and use kubectl apply to reconcile supported object fields through the API. Acceptance evidence: Edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change. This pairing is justified because declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.

Incorrect Answers

A:

This action and check address the distinct objective “Apply GitOps reconciliation with a version-controlled desired state” instead of the stated acceptance requirement. The matching action is to keep desired workload YAML in version control and use kubectl apply to reconcile supported object fields through the API. Its confirming test is to edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.

B:

This action and check address the distinct objective “Use nodeSelector to place a workload on nodes with required labels” instead of the stated acceptance requirement. The matching action is to keep desired workload YAML in version control and use kubectl apply to reconcile supported object fields through the API. Its confirming test is to edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.

D:

This action and check address the distinct objective “Distinguish ConfigMaps from Secrets and avoid storing credentials in public configuration” instead of the stated acceptance requirement. The matching action is to keep desired workload YAML in version control and use kubectl apply to reconcile supported object fields through the API. Its confirming test is to edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.

Question 171

A municipal data team creates a Deployment whose Pods cannot find matching nodes. Which engineering approach is the most appropriate for this cloud-native case?

  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.
  2. Read a workload's spec and status separately and inspect conditions when determining whether an API change became healthy.
  3. Grant operators only required API verbs and resources using RBAC, then test with kubectl auth can-i and separate synthetic identities.
  4. Require reviewed image provenance, admission policy checks and staged traffic validation before promoting a cloud-native application.

Explanation

Correct Answer

B:

Read a workload's spec and status separately and inspect conditions when determining whether an API change became healthy. This resolves the issue because the spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors. To verify, apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.

Incorrect Answers

A:

This option addresses the distinct objective “Separate kube-scheduler decisions from kubelet execution”, not the immediate requirement. The scheduler selects a suitable node for an unscheduled Pod; kubelet on that node uses the runtime to start and monitor containers. For the stated case, the spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.

C:

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 spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.

D:

This option addresses the distinct objective “Define secure release governance with staged approvals and policy verification”, not the immediate requirement. A deployment pipeline is a trust boundary; signed artifacts and automated policy tests reduce the risk of unreviewed configurations reaching production. For the stated case, the spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.

Question 172

A municipal data team creates a Deployment whose Pods cannot find matching nodes. What infrastructure principle makes the correct treatment effective?

  1. The spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.
  2. Deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings.
  3. An image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage.
  4. A deployment pipeline is a trust boundary; signed artifacts and automated policy tests reduce the risk of unreviewed configurations reaching production.

Explanation

Correct Answer

A:

The spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors. It supports this action: Read a workload's spec and status separately and inspect conditions when determining whether an API change became healthy. To confirm, apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.

Incorrect Answers

B:

That statement explains the distinct objective “Use rollout status and undo to validate and recover a Deployment release” rather than the cause in this case. The deciding mechanism here is that the spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.

C:

That statement explains the distinct objective “Distinguish a container image from a running container and its writable layer” rather than the cause in this case. The deciding mechanism here is that the spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.

D:

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 spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.

Question 173

A municipal data team creates a Deployment whose Pods cannot find matching nodes. What verification result would most convincingly distinguish a working solution from a claim?

  1. Apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.
  2. Inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting.
  3. Simulate an unavailable lab worker, inspect Ready condition and Pod Events, then confirm managed workloads are rescheduled where feasible.
  4. Create a controlled test namespace with a tiny quota and verify a request exceeding aggregate limits is rejected.

Explanation

Correct Answer

A:

Apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events. This is the relevant test because the spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.

Incorrect Answers

B:

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, apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.

C:

This check would help evaluate the distinct objective “Use node conditions and allocatable capacity to diagnose NotReady workloads”, but not the required result. For this case, apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.

D:

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, apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.

Question 174

A municipal data team creates a Deployment whose Pods cannot find matching nodes. The change review contains this proposal: “Conclude that successful API object creation guarantees successful container execution on a worker.” What risk matters most?

  1. The scheduler may legally use a non-preferred node, violating the policy that was mistakenly assumed mandatory.
  2. The command can mutate production objects although the operator intended a disposable laboratory cluster.
  3. A resource can remain Pending indefinitely even while its desired configuration is stored correctly.
  4. Replacing a Pod can destroy state because no independent persistent volume was requested.

Explanation

Correct Answer

C:

A resource can remain Pending indefinitely even while its desired configuration is stored correctly. The shortcut creates this risk because the spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.

Incorrect Answers

A:

That outcome concerns the distinct objective “Distinguish preferred node affinity from required scheduling rules”; it is not the most direct consequence of this shortcut. The relevant consequence is that a resource can remain Pending indefinitely even while its desired configuration is stored correctly.

B:

That outcome concerns the distinct objective “Manage kubectl contexts to avoid changes in the wrong cluster”; it is not the most direct consequence of this shortcut. The relevant consequence is that a resource can remain Pending indefinitely even while its desired configuration is stored correctly.

D:

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 a resource can remain Pending indefinitely even while its desired configuration is stored correctly.

Question 175

A municipal data team creates a Deployment whose Pods cannot find matching nodes. 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. Inspect FailedMount and PVC events, then verify StorageClass, PVC binding and node driver prerequisites before rewriting application code. Acceptance evidence: Reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim.
  3. Apply appropriate ResourceQuota and LimitRange policy to bound namespace consumption and guide default container resource requests or limits. Acceptance evidence: Create a controlled test namespace with a tiny quota and verify a request exceeding aggregate limits is rejected.
  4. Choose a CRI-compatible container runtime on worker nodes and investigate image and container creation separately from API scheduling. Acceptance evidence: Inspect node runtime information and compare a Pod's scheduling success with a runtime-reported image or sandbox failure.

Explanation

Correct Answer

A:

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. This pairing is justified because the spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.

Incorrect Answers

B:

This action and check address the distinct objective “Use Events and pod describe for failed volume mounting” instead of the stated acceptance requirement. The matching action is to read a workload's spec and status separately and inspect conditions when determining whether an API change became healthy. Its confirming test is to apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.

C:

This action and check address the distinct objective “Understand resource quotas and LimitRanges for namespace capacity governance” instead of the stated acceptance requirement. The matching action is to read a workload's spec and status separately and inspect conditions when determining whether an API change became healthy. Its confirming test is to apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.

D:

This action and check address the distinct objective “Explain the container runtime interface without conflating it with the control plane” instead of the stated acceptance requirement. The matching action is to read a workload's spec and status separately and inspect conditions when determining whether an API change became healthy. Its confirming test is to apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.

Question 176

A medical lab sees an updated Deployment specification but its available replicas remain zero. What technical action should the platform team take in this situation?

  1. Use kubectl get for concise resource lists and kubectl describe for detailed status, conditions and Events when triaging a workload.
  2. Read a workload's spec and status separately and inspect conditions when determining whether an API change became healthy.
  3. Send cluster changes through the authenticated Kubernetes API and inspect the object returned by the API server rather than changing node processes directly.
  4. Use a supported service mesh when fine-grained internal service-to-service security and telemetry are needed, while separately configuring north-south ingress or gateway exposure.

Explanation

Correct Answer

B:

The situation is that a medical lab sees an updated Deployment specification but its available replicas remain zero. Read a workload's spec and status separately and inspect conditions when determining whether an API change became healthy. This resolves the issue because the spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors. To verify, apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.

Incorrect Answers

A:

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, the spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.

C:

This option addresses the distinct objective “Trace Kubernetes API requests through the kube-apiserver entry point”, not the immediate requirement. The kube-apiserver validates authorized API requests and exposes the declarative resource interface; kubelets and controllers subsequently reconcile the saved desired state. For the stated case, the spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.

D:

This option addresses the distinct objective “Distinguish service mesh traffic management from external ingress routing”, not the immediate requirement. Service meshes commonly use proxies or ambient dataplanes to control east-west traffic; ingress/gateway handling addresses entry routes and can integrate with the mesh. For the stated case, the spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.

Question 177

A medical lab sees an updated Deployment specification but its available replicas remain zero. What underlying Kubernetes behavior is most relevant to this technical decision?

  1. The spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.
  2. A Deployment owns ReplicaSets that manage matching Pods and supports declarative rollout history, unlike an independent Pod object.
  3. ConfigMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.
  4. A failed readiness probe removes a Pod from ready Service endpoints, while failed liveness checks can restart a process; their operational consequences differ.

Explanation

Correct Answer

A:

The situation is that a medical lab sees an updated Deployment specification but its available replicas remain zero. The spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors. It supports this action: Read a workload's spec and status separately and inspect conditions when determining whether an API change became healthy. To confirm, apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.

Incorrect Answers

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 spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.

C:

That statement explains the distinct objective “Distinguish ConfigMaps from Secrets and avoid storing credentials in public configuration” rather than the cause in this case. The deciding mechanism here is that the spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.

D:

That statement explains the distinct objective “Investigate readiness failures separately from liveness-related restarts” rather than the cause in this case. The deciding mechanism here is that the spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.

Question 178

A medical lab sees an updated Deployment specification but its available replicas remain zero. What acceptance check most directly confirms this requirement is met?

  1. Compare kubectl get pods -o wide with kubectl describe pod for a test image-pull failure and note which output shows recent Events.
  2. Apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.
  3. Run kubectl config current-context and kubectl config view --minify, then perform a read-only lookup in the expected namespace.
  4. Simulate an unavailable lab worker, inspect Ready condition and Pod Events, then confirm managed workloads are rescheduled where feasible.

Explanation

Correct Answer

B:

The situation is that a medical lab sees an updated Deployment specification but its available replicas remain zero. Apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events. This is the relevant test because the spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Use kubectl get and describe for distinct inspection needs”, but not the required result. For this case, apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.

C:

This check would help evaluate the distinct objective “Manage kubectl contexts to avoid changes in the wrong cluster”, but not the required result. For this case, apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.

D:

The situation is that a medical lab sees an updated Deployment specification but its available replicas remain zero. This check would help evaluate the distinct objective “Use node conditions and allocatable capacity to diagnose NotReady workloads”, but not the required result. For this case, apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.

Question 179

A medical lab sees an updated Deployment specification but its available replicas remain zero. The team suggests: “Conclude that successful API object creation guarantees successful container execution on a worker.” Which failure should the reviewer anticipate?

  1. Sensitive traffic may remain allowed because the networking implementation does not enforce the declared policy.
  2. Containers gain broad host exposure and compromise blast radius becomes larger than the application's needs.
  3. A resource can remain Pending indefinitely even while its desired configuration is stored correctly.
  4. An unrelated object may be targeted or the intended workload may remain untouched and unavailable.

Explanation

Correct Answer

C:

The situation is that a medical lab sees an updated Deployment specification but its available replicas remain zero. A resource can remain Pending indefinitely even while its desired configuration is stored correctly. The shortcut creates this risk because the spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.

Incorrect Answers

A:

That outcome concerns the distinct objective “Recognize NetworkPolicy isolation only when the CNI enforces it”; it is not the most direct consequence of this shortcut. The relevant consequence is that a resource can remain Pending indefinitely even while its desired configuration is stored correctly.

B:

That outcome concerns the distinct objective “Run images with least-privilege runtime security contexts”; it is not the most direct consequence of this shortcut. The relevant consequence is that a resource can remain Pending indefinitely even while its desired configuration is stored correctly.

D:

That outcome concerns the distinct objective “Read the API resource model using namespaces and names rather than guessing ownership”; it is not the most direct consequence of this shortcut. The relevant consequence is that a resource can remain Pending indefinitely even while its desired configuration is stored correctly.

Question 180

A medical lab sees an updated Deployment specification but its available replicas remain zero. 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. Use requiredDuringSchedulingIgnoredDuringExecution for mandatory constraints and preferredDuringSchedulingIgnoredDuringExecution for a soft placement preference. Acceptance evidence: Test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.
  3. Review Retain versus Delete behavior for data-bearing PVs and test cleanup policy using synthetic non-sensitive data. Acceptance evidence: Create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.
  4. Record non-identifying build or audit metadata as annotations and use labels for indexing, grouping and selector-based routing. Acceptance evidence: Annotate a Deployment with release notes and verify its Service still selects Pods using explicit app labels.

Explanation

Correct Answer

A:

The situation is that a medical lab sees an updated Deployment specification but its available replicas remain zero. 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. This pairing is justified because the spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.

Incorrect Answers

B:

This action and check address the distinct objective “Distinguish preferred node affinity from required scheduling rules” instead of the stated acceptance requirement. The matching action is to read a workload's spec and status separately and inspect conditions when determining whether an API change became healthy. Its confirming test is to apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.

C:

This action and check address the distinct objective “Compare PV reclaim policies and explain data retention on PVC deletion” instead of the stated acceptance requirement. The matching action is to read a workload's spec and status separately and inspect conditions when determining whether an API change became healthy. Its confirming test is to apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.

D:

This action and check address the distinct objective “Use annotations for tool metadata rather than workload selection” instead of the stated acceptance requirement. The matching action is to read a workload's spec and status separately and inspect conditions when determining whether an API change became healthy. Its confirming test is to apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests