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 14

Question 130

A campus project renames Pods but does not update labels referenced by its existing Service. Which engineering change and test jointly addresses the scenario?

  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. 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.
  3. Apply stable application labels and ensure Services and controllers select the intended Pods by equality or set-based matching. Acceptance evidence: Compare kubectl get pods -l app=inventory with Service selectors and EndpointSlices for a test workload.
  4. Use a Deployment for a replicated stateless application requiring rolling updates and replacement of failed Pods. Acceptance evidence: Scale a test Deployment and inspect its ReplicaSet and owned Pods, then compare deleting a standalone Pod.

Explanation

Correct Answer

C:

The situation is that a campus project renames Pods but does not update labels referenced by its existing Service. Apply stable application labels and ensure Services and controllers select the intended Pods by equality or set-based matching. Acceptance evidence: Compare kubectl get pods -l app=inventory with Service selectors and EndpointSlices for a test workload. This pairing is justified because Kubernetes labels are queryable object metadata, while selectors connect controllers and Services to matching endpoints; names alone do not create these relationships.

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 apply stable application labels and ensure Services and controllers select the intended Pods by equality or set-based matching. Its confirming test is to compare kubectl get pods -l app=inventory with Service selectors and EndpointSlices for a test workload.

B:

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 apply stable application labels and ensure Services and controllers select the intended Pods by equality or set-based matching. Its confirming test is to compare kubectl get pods -l app=inventory with Service selectors and EndpointSlices for a test workload.

D:

This action and check address the distinct objective “Distinguish Deployment desired state from a manually created Pod” instead of the stated acceptance requirement. The matching action is to apply stable application labels and ensure Services and controllers select the intended Pods by equality or set-based matching. Its confirming test is to compare kubectl get pods -l app=inventory with Service selectors and EndpointSlices for a test workload.

Question 131

A compliance collector needs read-only access to its own namespace metadata. Which supported Kubernetes practice directly addresses the stated requirement?

  1. Choose a CRI-compatible container runtime on worker nodes and investigate image and container creation separately from API scheduling.
  2. Route a measured fraction of traffic to a canary or switch between separately verified blue and green environments using an appropriate routing controller.
  3. Inspect the active kubeconfig context and namespace before applying manifests to staging or production.
  4. Give each workload an appropriate Kubernetes ServiceAccount and narrow RBAC permissions rather than embedding an administrator kubeconfig in its image.

Explanation

Correct Answer

D:

Give each workload an appropriate Kubernetes ServiceAccount and narrow RBAC permissions rather than embedding an administrator kubeconfig in its image. This resolves the issue because serviceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets. To verify, run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.

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, serviceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets.

B:

This option addresses the distinct objective “Distinguish canary and blue-green delivery strategies from Kubernetes Deployment defaults”, not the immediate requirement. Canary release needs traffic steering and metrics for a subset; blue-green shifts a complete traffic target after validation, and neither is automatically provided by a plain Deployment update. For the stated case, serviceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets.

C:

This option addresses the distinct objective “Manage kubectl contexts to avoid changes in the wrong cluster”, not the immediate requirement. A kubeconfig context binds cluster, identity and default namespace, so command syntax can be valid yet target the wrong environment. For the stated case, serviceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets.

Question 132

A compliance collector needs read-only access to its own namespace metadata. Which causal explanation supports the intended design choice?

  1. ServiceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets.
  2. The scheduler selects a suitable node for an unscheduled Pod; kubelet on that node uses the runtime to start and monitor containers.
  3. CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.
  4. StatefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.

Explanation

Correct Answer

A:

ServiceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets. It supports this action: Give each workload an appropriate Kubernetes ServiceAccount and narrow RBAC permissions rather than embedding an administrator kubeconfig in its image. To confirm, run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.

Incorrect Answers

B:

That statement explains the distinct objective “Separate kube-scheduler decisions from kubelet execution” rather than the cause in this case. The deciding mechanism here is that serviceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets.

C:

That statement explains the distinct objective “Distinguish memory limits from CPU throttling for scheduling and runtime symptoms” rather than the cause in this case. The deciding mechanism here is that serviceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets.

D:

That statement explains the distinct objective “Use StatefulSet for stable ordinal identity and persistent per-replica claims” rather than the cause in this case. The deciding mechanism here is that serviceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets.

Question 133

A compliance collector needs read-only access to its own namespace metadata. Which test provides the strongest evidence of a correct implementation?

  1. Deploy a matching replica set across two labeled zones and inspect skew after adding a new Pod.
  2. In a lab add a read-only debug container, inspect network conditions and verify audit logs record the ephemeral container action.
  3. Set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.
  4. Run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.

Explanation

Correct Answer

D:

Run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list. This is the relevant test because serviceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Spread replicas across failure domains with topologySpreadConstraints”, but not the required result. For this case, run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.

B:

This check would help evaluate the distinct objective “Use ephemeral debugging containers only with appropriate permission and safeguards”, but not the required result. For this case, run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.

C:

This check would help evaluate the distinct objective “Explain desired state versus observed status in Kubernetes objects”, but not the required result. For this case, run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.

Question 134

A compliance collector needs read-only access to its own namespace metadata. A shortcut is proposed: “Bake a cluster-admin kubeconfig into a reusable public container image so workloads can discover any object.” Which technical consequence follows most closely?

  1. The command can mutate production objects although the operator intended a disposable laboratory cluster.
  2. Requests fail after a replica is replaced because the client bypassed the Service abstraction.
  3. A control-plane restore might recover resource metadata while losing application records that were never backed up.
  4. Credential reuse could expose all namespaces and persist after the original developer loses access.

Explanation

Correct Answer

D:

Credential reuse could expose all namespaces and persist after the original developer loses access. The shortcut creates this risk because serviceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets.

Incorrect Answers

A:

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 credential reuse could expose all namespaces and persist after the original developer loses access.

B:

That outcome concerns the distinct objective “Distinguish Pod IPs from stable Services during rescheduling”; it is not the most direct consequence of this shortcut. The relevant consequence is that credential reuse could expose all namespaces and persist after the original developer loses access.

C:

That outcome concerns the distinct objective “Distinguish etcd persistence from running workload data”; it is not the most direct consequence of this shortcut. The relevant consequence is that credential reuse could expose all namespaces and persist after the original developer loses access.

Question 135

A compliance collector needs read-only access to its own namespace metadata. Which combined solution and independent check are most directly justified?

  1. Grant operators only required API verbs and resources using RBAC, then test with kubectl auth can-i and separate synthetic identities. Acceptance evidence: With restricted identities, check get pods succeeds while delete secrets and create clusterroles are denied.
  2. Require reviewed image provenance, admission policy checks and staged traffic validation before promoting a cloud-native application. Acceptance evidence: Insert a deliberately unsigned test image into staging and confirm the release gate blocks production promotion while logging a reason.
  3. 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.
  4. Send cluster changes through the authenticated Kubernetes API and inspect the object returned by the API server rather than changing node processes directly. Acceptance evidence: Create a namespaced ConfigMap with kubectl, read it back through the API, and confirm no manual edit of a worker-node process was required.

Explanation

Correct Answer

C:

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. This pairing is justified because serviceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets.

Incorrect Answers

A:

This action and check address the distinct objective “Use least-privilege kubectl authentication and authorization during routine administration” instead of the stated acceptance requirement. The matching action is to give each workload an appropriate Kubernetes ServiceAccount and narrow RBAC permissions rather than embedding an administrator kubeconfig in its image. Its confirming test is to run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.

B:

This action and check address the distinct objective “Define secure release governance with staged approvals and policy verification” instead of the stated acceptance requirement. The matching action is to give each workload an appropriate Kubernetes ServiceAccount and narrow RBAC permissions rather than embedding an administrator kubeconfig in its image. Its confirming test is to run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.

D:

This action and check address the distinct objective “Trace Kubernetes API requests through the kube-apiserver entry point” instead of the stated acceptance requirement. The matching action is to give each workload an appropriate Kubernetes ServiceAccount and narrow RBAC permissions rather than embedding an administrator kubeconfig in its image. Its confirming test is to run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.

Question 136

A student wants to understand why kubectl credentials on a laptop differ from a Pod's in-cluster identity. What technical action should the platform team take in this situation?

  1. Apply stable application labels and ensure Services and controllers select the intended Pods by equality or set-based matching.
  2. Give each workload an appropriate Kubernetes ServiceAccount and narrow RBAC permissions rather than embedding an administrator kubeconfig in its image.
  3. Use metrics for measurable trends, logs for event detail and distributed traces for individual transaction paths while sharing correlation identifiers.
  4. Use narrowly scoped imagePullSecrets or an approved node identity to authorize the runtime to pull a private image.

Explanation

Correct Answer

B:

The situation is that a student wants to understand why kubectl credentials on a laptop differ from a Pod's in-cluster identity. Give each workload an appropriate Kubernetes ServiceAccount and narrow RBAC permissions rather than embedding an administrator kubeconfig in its image. This resolves the issue because serviceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets. To verify, run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.

Incorrect Answers

A:

This option addresses the distinct objective “Use labels and selectors to connect resources predictably”, not the immediate requirement. Kubernetes labels are queryable object metadata, while selectors connect controllers and Services to matching endpoints; names alone do not create these relationships. For the stated case, serviceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets.

C:

This option addresses the distinct objective “Explain metrics, logs and traces as complementary observability signals”, not the immediate requirement. Each telemetry type represents a different view of runtime state and links through context can connect a symptom to a specific service hop. For the stated case, serviceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets.

D:

This option addresses the distinct objective “Handle private registry pulls with dedicated credentials instead of embedding secrets in images”, not the immediate requirement. Image-pull credentials are consumed before the application starts and should not be hardcoded into container layers or app logs. For the stated case, serviceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets.

Question 137

A student wants to understand why kubectl credentials on a laptop differ from a Pod's in-cluster identity. What underlying Kubernetes behavior is most relevant to this technical decision?

  1. ServiceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets.
  2. NetworkPolicies select Pods and define allowed flows; when a Pod becomes isolated, traffic is allowed only as permitted by applicable rules and plugin behavior.
  3. Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds.
  4. A Deployment owns ReplicaSets that manage matching Pods and supports declarative rollout history, unlike an independent Pod object.

Explanation

Correct Answer

A:

The situation is that a student wants to understand why kubectl credentials on a laptop differ from a Pod's in-cluster identity. ServiceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets. It supports this action: Give each workload an appropriate Kubernetes ServiceAccount and narrow RBAC permissions rather than embedding an administrator kubeconfig in its image. To confirm, run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.

Incorrect Answers

B:

That statement explains the distinct objective “Limit workload-to-workload access with explicit NetworkPolicy allow rules” rather than the cause in this case. The deciding mechanism here is that serviceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets.

C:

That statement explains the distinct objective “Read the API resource model using namespaces and names rather than guessing ownership” rather than the cause in this case. The deciding mechanism here is that serviceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets.

D:

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 serviceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets.

Question 138

A student wants to understand why kubectl credentials on a laptop differ from a Pod's in-cluster identity. What acceptance check most directly confirms this requirement is met?

  1. Run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.
  2. Change a test Deployment field outside Git, observe drift and confirm reconciliation restores the reviewed Git value.
  3. Inspect the cluster backup policy for etcd snapshots and separately restore synthetic application data from its own backup.
  4. Apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.

Explanation

Correct Answer

A:

The situation is that a student wants to understand why kubectl credentials on a laptop differ from a Pod's in-cluster identity. Run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list. This is the relevant test because serviceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets.

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, run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.

C:

This check would help evaluate the distinct objective “Distinguish etcd persistence from running workload data”, but not the required result. For this case, run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.

D:

This check would help evaluate the distinct objective “Interpret Kubernetes spec and status fields without confusing intent with condition”, but not the required result. For this case, run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.

Question 139

A student wants to understand why kubectl credentials on a laptop differ from a Pod's in-cluster identity. The team suggests: “Bake a cluster-admin kubeconfig into a reusable public container image so workloads can discover any object.” Which failure should the reviewer anticipate?

  1. A working dataplane may be needlessly modified, disrupting traffic that was already being forwarded correctly.
  2. Credential reuse could expose all namespaces and persist after the original developer loses access.
  3. A migration fails because backend volume classes and cloud authentication semantics differ.
  4. Controllers may fail to recognize intended Pods or adopt unwanted matches, producing confusing replacement behavior.

Explanation

Correct Answer

B:

The situation is that a student wants to understand why kubectl credentials on a laptop differ from a Pod's in-cluster identity. Credential reuse could expose all namespaces and persist after the original developer loses access. The shortcut creates this risk because serviceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets.

Incorrect Answers

A:

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 credential reuse could expose all namespaces and persist after the original developer loses access.

C:

That outcome concerns the distinct objective “Apply cloud-native portability and immutable infrastructure principles pragmatically”; it is not the most direct consequence of this shortcut. The relevant consequence is that credential reuse could expose all namespaces and persist after the original developer loses access.

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 credential reuse could expose all namespaces and persist after the original developer loses access.

Question 140

A student wants to understand why kubectl credentials on a laptop differ from a Pod's in-cluster identity. Which engineering change and test jointly addresses the scenario?

  1. Choose an available StorageClass with a compatible CSI provisioner and appropriate binding behavior when creating a PVC. Acceptance evidence: Create a claim using a named test StorageClass and compare provisioner events and binding timing with a non-existent class.
  2. Apply stable application labels and ensure Services and controllers select the intended Pods by equality or set-based matching. Acceptance evidence: Compare kubectl get pods -l app=inventory with Service selectors and EndpointSlices for a test workload.
  3. 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.
  4. 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.

Explanation

Correct Answer

C:

The situation is that a student wants to understand why kubectl credentials on a laptop differ from a Pod's in-cluster identity. 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. This pairing is justified because serviceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets.

Incorrect Answers

A:

This action and check address the distinct objective “Use StorageClass for dynamic volume provisioning rather than handcrafting every disk” instead of the stated acceptance requirement. The matching action is to give each workload an appropriate Kubernetes ServiceAccount and narrow RBAC permissions rather than embedding an administrator kubeconfig in its image. Its confirming test is to run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.

B:

This action and check address the distinct objective “Use labels and selectors to connect resources predictably” instead of the stated acceptance requirement. The matching action is to give each workload an appropriate Kubernetes ServiceAccount and narrow RBAC permissions rather than embedding an administrator kubeconfig in its image. Its confirming test is to run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.

D:

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 give each workload an appropriate Kubernetes ServiceAccount and narrow RBAC permissions rather than embedding an administrator kubeconfig in its image. Its confirming test is to run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests