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 71

Question 700

A hospital analytics service has three durable replicas that should not overwrite a shared data directory. Which engineering change and test jointly addresses the scenario?

  1. Request persistent storage with a PVC and examine the bound PersistentVolume capacity, class and access mode before deploying a data-bearing Pod. Acceptance evidence: Create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence.
  2. Select a StatefulSet with volumeClaimTemplates for a stateful clustered application requiring stable Pod names and individual durable volumes. Acceptance evidence: Scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod.
  3. 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.
  4. Require approved image registries, signature or digest verification and patch ownership when admitting production container images. Acceptance evidence: Deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.

Explanation

Correct Answer

B:

The situation is that a hospital analytics service has three durable replicas that should not overwrite a shared data directory. Select a StatefulSet with volumeClaimTemplates for a stateful clustered application requiring stable Pod names and individual durable volumes. Acceptance evidence: Scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod. This pairing is justified because statefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.

Incorrect Answers

A:

This action and check address the distinct objective “Understand PersistentVolumeClaim binding to persistent storage resources” instead of the stated acceptance requirement. The matching action is to select a StatefulSet with volumeClaimTemplates for a stateful clustered application requiring stable Pod names and individual durable volumes. Its confirming test is to scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod.

C:

The situation is that a hospital analytics service has three durable replicas that should not overwrite a shared data directory. 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 select a StatefulSet with volumeClaimTemplates for a stateful clustered application requiring stable Pod names and individual durable volumes. Its confirming test is to scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod.

D:

This action and check address the distinct objective “Use image provenance and policy controls without trusting mutable tags” instead of the stated acceptance requirement. The matching action is to select a StatefulSet with volumeClaimTemplates for a stateful clustered application requiring stable Pod names and individual durable volumes. Its confirming test is to scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod.

Question 701

A warehouse migrates to a managed storage driver and observes volume attachment errors during rollout. Which supported Kubernetes practice directly addresses the stated requirement?

  1. Select a StatefulSet with volumeClaimTemplates for a stateful clustered application requiring stable Pod names and individual durable volumes.
  2. Expose appropriately labeled /metrics endpoints or exporters and configure Prometheus scrape targets to collect time-series measurements.
  3. Verify that the installed Container Storage Interface driver supports the requested persistent storage and inspect driver controller/node components when mounting fails.
  4. Combine a default-deny baseline with narrow app-label and namespace-label NetworkPolicy rules for approved traffic.

Explanation

Correct Answer

C:

Verify that the installed Container Storage Interface driver supports the requested persistent storage and inspect driver controller/node components when mounting fails. This resolves the issue because CSI separates storage vendor implementation from Kubernetes core and manages provisioning, attachment and node mounting through driver-defined capabilities. To verify, inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload.

Incorrect Answers

A:

This option addresses the distinct objective “Use StatefulSet for stable ordinal identity and persistent per-replica claims”, not the immediate requirement. StatefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy. For the stated case, CSI separates storage vendor implementation from Kubernetes core and manages provisioning, attachment and node mounting through driver-defined capabilities.

B:

This option addresses the distinct objective “Understand Prometheus pull-based metrics collection and exporters”, not the immediate requirement. Prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples. For the stated case, CSI separates storage vendor implementation from Kubernetes core and manages provisioning, attachment and node mounting through driver-defined capabilities.

D:

This option addresses the distinct objective “Limit workload-to-workload access with explicit NetworkPolicy allow rules”, not the immediate requirement. NetworkPolicies select Pods and define allowed flows; when a Pod becomes isolated, traffic is allowed only as permitted by applicable rules and plugin behavior. For the stated case, CSI separates storage vendor implementation from Kubernetes core and manages provisioning, attachment and node mounting through driver-defined capabilities.

Question 702

A warehouse migrates to a managed storage driver and observes volume attachment errors during rollout. Which causal explanation supports the intended design choice?

  1. PV access modes express volume mount constraints and driver support; ReadWriteOnce normally restricts writable use to one node, while ReadWriteMany requires a capable backend.
  2. kube-proxy can maintain node networking rules for Services, but supported network implementations may replace this function.
  3. CSI separates storage vendor implementation from Kubernetes core and manages provisioning, attachment and node mounting through driver-defined capabilities.
  4. Mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse.

Explanation

Correct Answer

C:

CSI separates storage vendor implementation from Kubernetes core and manages provisioning, attachment and node mounting through driver-defined capabilities. It supports this action: Verify that the installed Container Storage Interface driver supports the requested persistent storage and inspect driver controller/node components when mounting fails. To confirm, inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload.

Incorrect Answers

A:

That statement explains the distinct objective “Choose ReadWriteOnce and ReadWriteMany access modes by backend capability” rather than the cause in this case. The deciding mechanism here is that CSI separates storage vendor implementation from Kubernetes core and manages provisioning, attachment and node mounting through driver-defined capabilities.

B:

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 CSI separates storage vendor implementation from Kubernetes core and manages provisioning, attachment and node mounting through driver-defined capabilities.

D:

That statement explains the distinct objective “Enforce workload service account token boundaries and avoid needless mounts” rather than the cause in this case. The deciding mechanism here is that CSI separates storage vendor implementation from Kubernetes core and manages provisioning, attachment and node mounting through driver-defined capabilities.

Question 703

A warehouse migrates to a managed storage driver and observes volume attachment errors during rollout. Which test provides the strongest evidence of a correct implementation?

  1. Test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.
  2. Delete and replace a Deployment Pod and verify a client continues to reach its Service DNS name despite changed backend Pod addresses.
  3. Inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload.
  4. Create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.

Explanation

Correct Answer

C:

Inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload. This is the relevant test because CSI separates storage vendor implementation from Kubernetes core and manages provisioning, attachment and node mounting through driver-defined capabilities.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Distinguish preferred node affinity from required scheduling rules”, but not the required result. For this case, inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload.

B:

This check would help evaluate the distinct objective “Distinguish Pod IPs from stable Services during rescheduling”, but not the required result. For this case, inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload.

D:

This check would help evaluate the distinct objective “Compare PV reclaim policies and explain data retention on PVC deletion”, but not the required result. For this case, inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload.

Question 704

A warehouse migrates to a managed storage driver and observes volume attachment errors during rollout. A shortcut is proposed: “Assume Kubernetes creates arbitrary cloud disks without a configured matching CSI provisioner or valid backend credentials.” Which technical consequence follows most closely?

  1. The route remains nonfunctional because nothing reconciles it into an application traffic proxy.
  2. PersistentVolumeClaims remain Pending or Pods fail to mount because the required driver integration is missing.
  3. Replicas can collide on storage ownership and application state ordering assumptions fail.
  4. A scheduled workload may violate performance expectations because the declared label was not backed by infrastructure inventory.

Explanation

Correct Answer

B:

PersistentVolumeClaims remain Pending or Pods fail to mount because the required driver integration is missing. The shortcut creates this risk because CSI separates storage vendor implementation from Kubernetes core and manages provisioning, attachment and node mounting through driver-defined capabilities.

Incorrect Answers

A:

That outcome concerns the distinct objective “Choose Ingress or Gateway API with an implementing controller for HTTP exposure”; it is not the most direct consequence of this shortcut. The relevant consequence is that persistentVolumeClaims remain Pending or Pods fail to mount because the required driver integration is missing.

C:

That outcome concerns the distinct objective “Use StatefulSet for stable ordinal identity and persistent per-replica claims”; it is not the most direct consequence of this shortcut. The relevant consequence is that persistentVolumeClaims remain Pending or Pods fail to mount because the required driver integration is missing.

D:

That outcome concerns the distinct objective “Use nodeSelector to place a workload on nodes with required labels”; it is not the most direct consequence of this shortcut. The relevant consequence is that persistentVolumeClaims remain Pending or Pods fail to mount because the required driver integration is missing.

Question 705

A warehouse migrates to a managed storage driver and observes volume attachment errors during rollout. Which combined solution and independent check are most directly justified?

  1. Cordon a worker to prevent new scheduling and drain safely under PodDisruptionBudgets and DaemonSet rules before maintenance. Acceptance evidence: Observe a controlled drain with replica owners and a PDB, then verify workloads move and uncordon restores eligibility.
  2. Select a StatefulSet with volumeClaimTemplates for a stateful clustered application requiring stable Pod names and individual durable volumes. Acceptance evidence: Scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod.
  3. Verify that the installed Container Storage Interface driver supports the requested persistent storage and inspect driver controller/node components when mounting fails. Acceptance evidence: Inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload.
  4. Check EndpointSlices and Pod readiness when a Service exists but connections reach no application backends. Acceptance evidence: Compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings.

Explanation

Correct Answer

C:

Verify that the installed Container Storage Interface driver supports the requested persistent storage and inspect driver controller/node components when mounting fails. Acceptance evidence: Inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload. This pairing is justified because CSI separates storage vendor implementation from Kubernetes core and manages provisioning, attachment and node mounting through driver-defined capabilities.

Incorrect Answers

A:

This action and check address the distinct objective “Use cordon and drain with disruption considerations for planned node maintenance” instead of the stated acceptance requirement. The matching action is to verify that the installed Container Storage Interface driver supports the requested persistent storage and inspect driver controller/node components when mounting fails. Its confirming test is to inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload.

B:

This action and check address the distinct objective “Use StatefulSet for stable ordinal identity and persistent per-replica claims” instead of the stated acceptance requirement. The matching action is to verify that the installed Container Storage Interface driver supports the requested persistent storage and inspect driver controller/node components when mounting fails. Its confirming test is to inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload.

D:

This action and check address the distinct objective “Use EndpointSlices to connect Service selectors with actual backend Pods” instead of the stated acceptance requirement. The matching action is to verify that the installed Container Storage Interface driver supports the requested persistent storage and inspect driver controller/node components when mounting fails. Its confirming test is to inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload.

Question 706

A school cluster has PVCs referencing a storage system whose CSI node plugin is not running. What technical action should the platform team take in this situation?

  1. Verify that the installed Container Storage Interface driver supports the requested persistent storage and inspect driver controller/node components when mounting fails.
  2. Review Sandbox, Incubating and Graduated CNCF stages as community maturity signals while independently assessing a project's fitness, lifecycle and security.
  3. Choose an available StorageClass with a compatible CSI provisioner and appropriate binding behavior when creating a PVC.
  4. Check that a supported CNI plugin assigns reachable Pod addresses across worker nodes before troubleshooting Service routing or DNS names.

Explanation

Correct Answer

A:

The situation is that a school cluster has PVCs referencing a storage system whose CSI node plugin is not running. Verify that the installed Container Storage Interface driver supports the requested persistent storage and inspect driver controller/node components when mounting fails. This resolves the issue because CSI separates storage vendor implementation from Kubernetes core and manages provisioning, attachment and node mounting through driver-defined capabilities. To verify, inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload.

Incorrect Answers

B:

This option addresses the distinct objective “Understand CNCF project maturity stages without equating them to security approval”, not the immediate requirement. CNCF maturity describes aspects of adoption and governance, not a blanket guarantee that every deployment or version is free of defects. For the stated case, CSI separates storage vendor implementation from Kubernetes core and manages provisioning, attachment and node mounting through driver-defined capabilities.

C:

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, CSI separates storage vendor implementation from Kubernetes core and manages provisioning, attachment and node mounting through driver-defined capabilities.

D:

This option addresses the distinct objective “Distinguish the CNI Pod network from Service discovery and routing”, not the immediate requirement. Kubernetes expects a Pod network providing Pod-to-Pod connectivity; the CNI implementation configures networking while Services provide stable virtual access to changing endpoints. For the stated case, CSI separates storage vendor implementation from Kubernetes core and manages provisioning, attachment and node mounting through driver-defined capabilities.

Question 707

A school cluster has PVCs referencing a storage system whose CSI node plugin is not running. What underlying Kubernetes behavior is most relevant to this technical decision?

  1. A StorageClass defines how storage is provisioned and may use WaitForFirstConsumer to delay provisioning until scheduling requirements are known.
  2. CSI separates storage vendor implementation from Kubernetes core and manages provisioning, attachment and node mounting through driver-defined capabilities.
  3. Open standards and vendor-neutral governance reduce lock-in and support collaboration, but products can still differ in versions, implementations and operational capabilities.
  4. Pod Security Standards establish common workload hardening profiles, and admission checks can enforce restricted capabilities and privilege use at API creation.

Explanation

Correct Answer

B:

The situation is that a school cluster has PVCs referencing a storage system whose CSI node plugin is not running. CSI separates storage vendor implementation from Kubernetes core and manages provisioning, attachment and node mounting through driver-defined capabilities. It supports this action: Verify that the installed Container Storage Interface driver supports the requested persistent storage and inspect driver controller/node components when mounting fails. To confirm, inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload.

Incorrect Answers

A:

That statement explains the distinct objective “Use StorageClass for dynamic volume provisioning rather than handcrafting every disk” rather than the cause in this case. The deciding mechanism here is that CSI separates storage vendor implementation from Kubernetes core and manages provisioning, attachment and node mounting through driver-defined capabilities.

C:

That statement explains the distinct objective “Understand open standards and vendor-neutral community collaboration” rather than the cause in this case. The deciding mechanism here is that CSI separates storage vendor implementation from Kubernetes core and manages provisioning, attachment and node mounting through driver-defined capabilities.

D:

That statement explains the distinct objective “Use Pod Security Standards to deny overly privileged Pod configurations” rather than the cause in this case. The deciding mechanism here is that CSI separates storage vendor implementation from Kubernetes core and manages provisioning, attachment and node mounting through driver-defined capabilities.

Question 708

A school cluster has PVCs referencing a storage system whose CSI node plugin is not running. What acceptance check most directly confirms this requirement is met?

  1. Scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod.
  2. Inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.
  3. Inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload.
  4. Create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence.

Explanation

Correct Answer

C:

The situation is that a school cluster has PVCs referencing a storage system whose CSI node plugin is not running. Inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload. This is the relevant test because CSI separates storage vendor implementation from Kubernetes core and manages provisioning, attachment and node mounting through driver-defined capabilities.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Use StatefulSet for stable ordinal identity and persistent per-replica claims”, but not the required result. For this case, inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload.

B:

This check would help evaluate the distinct objective “Distinguish ConfigMaps from Secrets and avoid storing credentials in public configuration”, but not the required result. For this case, inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload.

D:

This check would help evaluate the distinct objective “Understand PersistentVolumeClaim binding to persistent storage resources”, but not the required result. For this case, inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload.

Question 709

A school cluster has PVCs referencing a storage system whose CSI node plugin is not running. The team suggests: “Assume Kubernetes creates arbitrary cloud disks without a configured matching CSI provisioner or valid backend credentials.” Which failure should the reviewer anticipate?

  1. The claim remains Pending and dependent Pods cannot mount the missing volume.
  2. Clients may connect to an impersonated API endpoint and the token could grant excessive permissions.
  3. PersistentVolumeClaims remain Pending or Pods fail to mount because the required driver integration is missing.
  4. The replacement also fails while operators lack the information needed to identify the application error.

Explanation

Correct Answer

C:

The situation is that a school cluster has PVCs referencing a storage system whose CSI node plugin is not running. PersistentVolumeClaims remain Pending or Pods fail to mount because the required driver integration is missing. The shortcut creates this risk because CSI separates storage vendor implementation from Kubernetes core and manages provisioning, attachment and node mounting through driver-defined capabilities.

Incorrect Answers

A:

That outcome concerns the distinct objective “Use StorageClass for dynamic volume provisioning rather than handcrafting every disk”; it is not the most direct consequence of this shortcut. The relevant consequence is that persistentVolumeClaims remain Pending or Pods fail to mount because the required driver integration is missing.

B:

That outcome concerns the distinct objective “Protect API server access using authenticated TLS clients and audited authorization”; it is not the most direct consequence of this shortcut. The relevant consequence is that persistentVolumeClaims remain Pending or Pods fail to mount because the required driver integration is missing.

D:

That outcome concerns the distinct objective “Use kubectl logs and previous container logs to isolate application crashes”; it is not the most direct consequence of this shortcut. The relevant consequence is that persistentVolumeClaims remain Pending or Pods fail to mount because the required driver integration is missing.

Question 710

A school cluster has PVCs referencing a storage system whose CSI node plugin is not running. Which engineering change and test jointly addresses the scenario?

  1. Use an authorized kubectl debug ephemeral container when an application image lacks troubleshooting tools and policy permits ephemeral containers. Acceptance evidence: In a lab add a read-only debug container, inspect network conditions and verify audit logs record the ephemeral container action.
  2. Select a StatefulSet with volumeClaimTemplates for a stateful clustered application requiring stable Pod names and individual durable volumes. Acceptance evidence: Scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod.
  3. Check EndpointSlices and Pod readiness when a Service exists but connections reach no application backends. Acceptance evidence: Compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings.
  4. Verify that the installed Container Storage Interface driver supports the requested persistent storage and inspect driver controller/node components when mounting fails. Acceptance evidence: Inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload.

Explanation

Correct Answer

D:

The situation is that a school cluster has PVCs referencing a storage system whose CSI node plugin is not running. Verify that the installed Container Storage Interface driver supports the requested persistent storage and inspect driver controller/node components when mounting fails. Acceptance evidence: Inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload. This pairing is justified because CSI separates storage vendor implementation from Kubernetes core and manages provisioning, attachment and node mounting through driver-defined capabilities.

Incorrect Answers

A:

This action and check address the distinct objective “Use ephemeral debugging containers only with appropriate permission and safeguards” instead of the stated acceptance requirement. The matching action is to verify that the installed Container Storage Interface driver supports the requested persistent storage and inspect driver controller/node components when mounting fails. Its confirming test is to inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload.

B:

The situation is that a school cluster has PVCs referencing a storage system whose CSI node plugin is not running. This action and check address the distinct objective “Use StatefulSet for stable ordinal identity and persistent per-replica claims” instead of the stated acceptance requirement. The matching action is to verify that the installed Container Storage Interface driver supports the requested persistent storage and inspect driver controller/node components when mounting fails. Its confirming test is to inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload.

C:

The situation is that a school cluster has PVCs referencing a storage system whose CSI node plugin is not running. This action and check address the distinct objective “Use EndpointSlices to connect Service selectors with actual backend Pods” instead of the stated acceptance requirement. The matching action is to verify that the installed Container Storage Interface driver supports the requested persistent storage and inspect driver controller/node components when mounting fails. Its confirming test is to inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests