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 19

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.

Question 181

A bank's release process records a change-ticket URL on every Deployment. What technical action should the platform team take in this situation?

  1. Record non-identifying build or audit metadata as annotations and use labels for indexing, grouping and selector-based routing.
  2. Grant operators only required API verbs and resources using RBAC, then test with kubectl auth can-i and separate synthetic identities.
  3. Set realistic CPU and memory requests for Pods and investigate FailedScheduling when no node has sufficient allocatable resources.
  4. Inspect kubectl describe node and reported conditions, taints, disk pressure and kubelet health before moving workloads.

Explanation

Correct Answer

A:

Record non-identifying build or audit metadata as annotations and use labels for indexing, grouping and selector-based routing. This resolves the issue because labels are designed for selectors and filtering, whereas annotations hold descriptive metadata not intended as a resource-matching control. To verify, annotate a Deployment with release notes and verify its Service still selects Pods using explicit app labels.

Incorrect Answers

B:

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, labels are designed for selectors and filtering, whereas annotations hold descriptive metadata not intended as a resource-matching control.

C:

This option addresses the distinct objective “Use container resource requests to help the scheduler fit Pods on nodes”, not the immediate requirement. The scheduler evaluates requests against node allocatable capacity; limits govern runtime ceilings and do not substitute for scheduling requests. For the stated case, labels are designed for selectors and filtering, whereas annotations hold descriptive metadata not intended as a resource-matching control.

D:

This option addresses the distinct objective “Use node conditions and allocatable capacity to diagnose NotReady workloads”, not the immediate requirement. A NotReady or pressure-affected node can stop hosting healthy Pods even when their Deployment and Service definitions remain valid. For the stated case, labels are designed for selectors and filtering, whereas annotations hold descriptive metadata not intended as a resource-matching control.

Question 182

A bank's release process records a change-ticket URL on every Deployment. What underlying Kubernetes behavior is most relevant to this technical decision?

  1. Declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.
  2. Labels are designed for selectors and filtering, whereas annotations hold descriptive metadata not intended as a resource-matching control.
  3. CNCF maturity describes aspects of adoption and governance, not a blanket guarantee that every deployment or version is free of defects.
  4. etcd persists Kubernetes API objects and cluster configuration, while application records ordinarily live in workload-specific storage outside etcd.

Explanation

Correct Answer

B:

Labels are designed for selectors and filtering, whereas annotations hold descriptive metadata not intended as a resource-matching control. It supports this action: Record non-identifying build or audit metadata as annotations and use labels for indexing, grouping and selector-based routing. To confirm, annotate a Deployment with release notes and verify its Service still selects Pods using explicit app labels.

Incorrect Answers

A:

That statement explains the distinct objective “Apply resource manifests declaratively instead of depending on imperative drift” rather than the cause in this case. The deciding mechanism here is that labels are designed for selectors and filtering, whereas annotations hold descriptive metadata not intended as a resource-matching control.

C:

That statement explains the distinct objective “Understand CNCF project maturity stages without equating them to security approval” rather than the cause in this case. The deciding mechanism here is that labels are designed for selectors and filtering, whereas annotations hold descriptive metadata not intended as a resource-matching control.

D:

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 labels are designed for selectors and filtering, whereas annotations hold descriptive metadata not intended as a resource-matching control.

Question 183

A bank's release process records a change-ticket URL on every Deployment. What acceptance check most directly confirms this requirement is met?

  1. Run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable.
  2. Annotate a Deployment with release notes and verify its Service still selects Pods using explicit app labels.
  3. Apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.
  4. Run kubectl config current-context and kubectl config view --minify, then perform a read-only lookup in the expected namespace.

Explanation

Correct Answer

B:

Annotate a Deployment with release notes and verify its Service still selects Pods using explicit app labels. This is the relevant test because labels are designed for selectors and filtering, whereas annotations hold descriptive metadata not intended as a resource-matching control.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Enforce workload service account token boundaries and avoid needless mounts”, but not the required result. For this case, annotate a Deployment with release notes and verify its Service still selects Pods using explicit app labels.

C:

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, annotate a Deployment with release notes and verify its Service still selects Pods using explicit app labels.

D:

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, annotate a Deployment with release notes and verify its Service still selects Pods using explicit app labels.

Question 184

A bank's release process records a change-ticket URL on every Deployment. The team suggests: “Put the only application routing identifier in an annotation while leaving the Service selector empty.” Which failure should the reviewer anticipate?

  1. PersistentVolumeClaims remain Pending or Pods fail to mount because the required driver integration is missing.
  2. Operators can see the metadata but the Service cannot select the desired Pods using that annotation.
  3. Compromised credentials can perform widespread cluster changes without attribution or least privilege.
  4. Priority differentiation is lost and capacity shortages still prevent scheduling or trigger avoidable disruption.

Explanation

Correct Answer

B:

Operators can see the metadata but the Service cannot select the desired Pods using that annotation. The shortcut creates this risk because labels are designed for selectors and filtering, whereas annotations hold descriptive metadata not intended as a resource-matching control.

Incorrect Answers

A:

That outcome concerns the distinct objective “Understand CSI drivers and volume attachment responsibilities”; it is not the most direct consequence of this shortcut. The relevant consequence is that operators can see the metadata but the Service cannot select the desired Pods using that annotation.

C:

That outcome concerns the distinct objective “Use least-privilege kubectl authentication and authorization during routine administration”; it is not the most direct consequence of this shortcut. The relevant consequence is that operators can see the metadata but the Service cannot select the desired Pods using that annotation.

D:

That outcome concerns the distinct objective “Use PriorityClasses and understand preemption without assuming they guarantee availability”; it is not the most direct consequence of this shortcut. The relevant consequence is that operators can see the metadata but the Service cannot select the desired Pods using that annotation.

Question 185

A bank's release process records a change-ticket URL on every Deployment. Which engineering change and test jointly addresses the scenario?

  1. Inspect the active kubeconfig context and namespace before applying manifests to staging or production. Acceptance evidence: Run kubectl config current-context and kubectl config view --minify, then perform a read-only lookup in the expected namespace.
  2. 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.
  3. 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.
  4. 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.

Explanation

Correct Answer

B:

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. This pairing is justified because labels are designed for selectors and filtering, whereas annotations hold descriptive metadata not intended as a resource-matching control.

Incorrect Answers

A:

This action and check address the distinct objective “Manage kubectl contexts to avoid changes in the wrong cluster” instead of the stated acceptance requirement. The matching action is to record non-identifying build or audit metadata as annotations and use labels for indexing, grouping and selector-based routing. Its confirming test is to annotate a Deployment with release notes and verify its Service still selects Pods using explicit app labels.

C:

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 record non-identifying build or audit metadata as annotations and use labels for indexing, grouping and selector-based routing. Its confirming test is to annotate a Deployment with release notes and verify its Service still selects Pods using explicit app labels.

D:

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 record non-identifying build or audit metadata as annotations and use labels for indexing, grouping and selector-based routing. Its confirming test is to annotate a Deployment with release notes and verify its Service still selects Pods using explicit app labels.

Question 186

A university dashboard wants to find all application Pods by team while retaining long-form audit notes. What technical action should the platform team take in this situation?

  1. Choose an available StorageClass with a compatible CSI provisioner and appropriate binding behavior when creating a PVC.
  2. Identify whether the cluster uses kube-proxy or an alternative Service dataplane before diagnosing virtual Service IP forwarding behavior.
  3. Resolve an object's apiVersion, kind, metadata namespace and name before applying or deleting it.
  4. Record non-identifying build or audit metadata as annotations and use labels for indexing, grouping and selector-based routing.

Explanation

Correct Answer

D:

The situation is that a university dashboard wants to find all application Pods by team while retaining long-form audit notes. Record non-identifying build or audit metadata as annotations and use labels for indexing, grouping and selector-based routing. This resolves the issue because labels are designed for selectors and filtering, whereas annotations hold descriptive metadata not intended as a resource-matching control. To verify, annotate a Deployment with release notes and verify its Service still selects Pods using explicit app labels.

Incorrect Answers

A:

This option addresses the distinct objective “Use StorageClass for dynamic volume provisioning rather than handcrafting every disk”, not the immediate requirement. A StorageClass defines how storage is provisioned and may use WaitForFirstConsumer to delay provisioning until scheduling requirements are known. For the stated case, labels are designed for selectors and filtering, whereas annotations hold descriptive metadata not intended as a resource-matching control.

B:

This option addresses the distinct objective “Understand service proxy implementations without assuming kube-proxy is mandatory”, not the immediate requirement. Kube-proxy can maintain node networking rules for Services, but supported network implementations may replace this function. For the stated case, labels are designed for selectors and filtering, whereas annotations hold descriptive metadata not intended as a resource-matching control.

C:

This option addresses the distinct objective “Read the API resource model using namespaces and names rather than guessing ownership”, not the immediate requirement. Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds. For the stated case, labels are designed for selectors and filtering, whereas annotations hold descriptive metadata not intended as a resource-matching control.

Question 187

A university dashboard wants to find all application Pods by team while retaining long-form audit notes. What underlying Kubernetes behavior is most relevant to this technical decision?

  1. Declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.
  2. Labels are designed for selectors and filtering, whereas annotations hold descriptive metadata not intended as a resource-matching control.
  3. A PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory.
  4. Multistage builds reduce image contents and potential attack surface by keeping build toolchains and source artifacts out of the final runtime layer.

Explanation

Correct Answer

B:

The situation is that a university dashboard wants to find all application Pods by team while retaining long-form audit notes. Labels are designed for selectors and filtering, whereas annotations hold descriptive metadata not intended as a resource-matching control. It supports this action: Record non-identifying build or audit metadata as annotations and use labels for indexing, grouping and selector-based routing. To confirm, annotate a Deployment with release notes and verify its Service still selects Pods using explicit app labels.

Incorrect Answers

A:

The situation is that a university dashboard wants to find all application Pods by team while retaining long-form audit notes. That statement explains the distinct objective “Apply resource manifests declaratively instead of depending on imperative drift” rather than the cause in this case. The deciding mechanism here is that labels are designed for selectors and filtering, whereas annotations hold descriptive metadata not intended as a resource-matching control.

C:

That statement explains the distinct objective “Understand PersistentVolumeClaim binding to persistent storage resources” rather than the cause in this case. The deciding mechanism here is that labels are designed for selectors and filtering, whereas annotations hold descriptive metadata not intended as a resource-matching control.

D:

That statement explains the distinct objective “Build smaller images with multistage builds and remove unnecessary tooling” rather than the cause in this case. The deciding mechanism here is that labels are designed for selectors and filtering, whereas annotations hold descriptive metadata not intended as a resource-matching control.

Question 188

A university dashboard wants to find all application Pods by team while retaining long-form audit notes. What acceptance check most directly confirms this requirement is met?

  1. Annotate a Deployment with release notes and verify its Service still selects Pods using explicit app labels.
  2. Deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.
  3. Set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.
  4. Compare kubectl get pods -o wide with kubectl describe pod for a test image-pull failure and note which output shows recent Events.

Explanation

Correct Answer

A:

The situation is that a university dashboard wants to find all application Pods by team while retaining long-form audit notes. Annotate a Deployment with release notes and verify its Service still selects Pods using explicit app labels. This is the relevant test because labels are designed for selectors and filtering, whereas annotations hold descriptive metadata not intended as a resource-matching control.

Incorrect Answers

B:

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, annotate a Deployment with release notes and verify its Service still selects Pods using explicit app labels.

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, annotate a Deployment with release notes and verify its Service still selects Pods using explicit app labels.

D:

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, annotate a Deployment with release notes and verify its Service still selects Pods using explicit app labels.

Question 189

A university dashboard wants to find all application Pods by team while retaining long-form audit notes. The team suggests: “Put the only application routing identifier in an annotation while leaving the Service selector empty.” Which failure should the reviewer anticipate?

  1. The container may enter a restart loop before completing initialization, prolonging unavailability.
  2. Operators can see the metadata but the Service cannot select the desired Pods using that annotation.
  3. The Pod continues restarting because Service DNS configuration is not the cause of the process exit.
  4. Compromised credentials can perform widespread cluster changes without attribution or least privilege.

Explanation

Correct Answer

B:

The situation is that a university dashboard wants to find all application Pods by team while retaining long-form audit notes. Operators can see the metadata but the Service cannot select the desired Pods using that annotation. The shortcut creates this risk because labels are designed for selectors and filtering, whereas annotations hold descriptive metadata not intended as a resource-matching control.

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 operators can see the metadata but the Service cannot select the desired Pods using that annotation.

C:

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 operators can see the metadata but the Service cannot select the desired Pods using that annotation.

D:

The situation is that a university dashboard wants to find all application Pods by team while retaining long-form audit notes. That outcome concerns the distinct objective “Use least-privilege kubectl authentication and authorization during routine administration”; it is not the most direct consequence of this shortcut. The relevant consequence is that operators can see the metadata but the Service cannot select the desired Pods using that annotation.

Question 190

A university dashboard wants to find all application Pods by team while retaining long-form audit notes. Which engineering change and test jointly addresses the scenario?

  1. Use kubectl get for concise resource lists and kubectl describe for detailed status, conditions and Events when triaging a workload. Acceptance evidence: Compare kubectl get pods -o wide with kubectl describe pod for a test image-pull failure and note which output shows recent Events.
  2. Define post-release checks for readiness, error rate and latency, and revert an unhealthy revision using an approved rollout mechanism. Acceptance evidence: Deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.
  3. 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.
  4. Configure anti-affinity against other Pods with a specific label so replicas prefer or require separate failure domains as appropriate. Acceptance evidence: Deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.

Explanation

Correct Answer

C:

The situation is that a university dashboard wants to find all application Pods by team while retaining long-form audit notes. 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. This pairing is justified because labels are designed for selectors and filtering, whereas annotations hold descriptive metadata not intended as a resource-matching control.

Incorrect Answers

A:

This action and check address the distinct objective “Use kubectl get and describe for distinct inspection needs” instead of the stated acceptance requirement. The matching action is to record non-identifying build or audit metadata as annotations and use labels for indexing, grouping and selector-based routing. Its confirming test is to annotate a Deployment with release notes and verify its Service still selects Pods using explicit app labels.

B:

This action and check address the distinct objective “Design a release rollback trigger from measurable service signals” instead of the stated acceptance requirement. The matching action is to record non-identifying build or audit metadata as annotations and use labels for indexing, grouping and selector-based routing. Its confirming test is to annotate a Deployment with release notes and verify its Service still selects Pods using explicit app labels.

D:

This action and check address the distinct objective “Use Pod anti-affinity to reduce correlated replica failure” instead of the stated acceptance requirement. The matching action is to record non-identifying build or audit metadata as annotations and use labels for indexing, grouping and selector-based routing. Its confirming test is to annotate a Deployment with release notes and verify its Service still selects Pods using explicit app labels.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests