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 70

Question 690

A community library wants several read/write application replicas to share documents through supported network storage. What pair of supported action and practical verification should be approved?

  1. Select an access mode supported by the actual storage driver and workload placement requirements rather than assuming every volume supports concurrent writes from every node. Acceptance evidence: Use a synthetic two-node workload and compare expected attach behavior for an RWO volume with a documented RWX shared filesystem.
  2. 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.
  3. Treat etcd as Kubernetes control-plane state storage and protect its snapshots, keys, and access separately from an application's database or PVC. Acceptance evidence: Inspect the cluster backup policy for etcd snapshots and separately restore synthetic application data from its own backup.
  4. Define appropriate HTTP routing through an installed Ingress controller or Gateway API controller rather than expecting the API object alone to provision a proxy. Acceptance evidence: Deploy a test hostname route, verify a compatible controller exists and inspect the programmed listener and backend status.

Explanation

Correct Answer

A:

The situation is that a community library wants several read/write application replicas to share documents through supported network storage. Select an access mode supported by the actual storage driver and workload placement requirements rather than assuming every volume supports concurrent writes from every node. Acceptance evidence: Use a synthetic two-node workload and compare expected attach behavior for an RWO volume with a documented RWX shared filesystem. This pairing is justified because PV access modes express volume mount constraints and driver support; ReadWriteOnce normally restricts writable use to one node, while ReadWriteMany requires a capable backend.

Incorrect Answers

B:

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 select an access mode supported by the actual storage driver and workload placement requirements rather than assuming every volume supports concurrent writes from every node. Its confirming test is to use a synthetic two-node workload and compare expected attach behavior for an RWO volume with a documented RWX shared filesystem.

C:

This action and check address the distinct objective “Distinguish etcd persistence from running workload data” instead of the stated acceptance requirement. The matching action is to select an access mode supported by the actual storage driver and workload placement requirements rather than assuming every volume supports concurrent writes from every node. Its confirming test is to use a synthetic two-node workload and compare expected attach behavior for an RWO volume with a documented RWX shared filesystem.

D:

This action and check address the distinct objective “Choose Ingress or Gateway API with an implementing controller for HTTP exposure” instead of the stated acceptance requirement. The matching action is to select an access mode supported by the actual storage driver and workload placement requirements rather than assuming every volume supports concurrent writes from every node. Its confirming test is to use a synthetic two-node workload and compare expected attach behavior for an RWO volume with a documented RWX shared filesystem.

Question 691

A university runs a small stateful training database cluster whose members need persistent identities. Which Kubernetes or cloud-native implementation decision best solves the stated problem?

  1. Choose Pod affinity only when co-locating related workloads is beneficial and verify independent network policies still govern traffic.
  2. Inspect probe configuration, Pod Ready conditions and restart events to identify whether traffic eligibility or container execution is failing.
  3. Choose an available StorageClass with a compatible CSI provisioner and appropriate binding behavior when creating a PVC.
  4. Select a StatefulSet with volumeClaimTemplates for a stateful clustered application requiring stable Pod names and individual durable volumes.

Explanation

Correct Answer

D:

Select a StatefulSet with volumeClaimTemplates for a stateful clustered application requiring stable Pod names and individual durable volumes. This resolves the issue because statefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy. To verify, scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod.

Incorrect Answers

A:

This option addresses the distinct objective “Use Pod affinity for co-location without assuming it creates networking permissions”, not the immediate requirement. Pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules. For the stated case, statefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.

B:

This option addresses the distinct objective “Investigate readiness failures separately from liveness-related restarts”, not the immediate requirement. A failed readiness probe removes a Pod from ready Service endpoints, while failed liveness checks can restart a process; their operational consequences differ. For the stated case, statefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.

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, statefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.

Question 692

A university runs a small stateful training database cluster whose members need persistent identities. Which platform mechanism explains why the suitable approach works?

  1. A StorageClass defines how storage is provisioned and may use WaitForFirstConsumer to delay provisioning until scheduling requirements are known.
  2. A rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.
  3. CSI separates storage vendor implementation from Kubernetes core and manages provisioning, attachment and node mounting through driver-defined capabilities.
  4. StatefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.

Explanation

Correct Answer

D:

StatefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy. It supports this action: Select a StatefulSet with volumeClaimTemplates for a stateful clustered application requiring stable Pod names and individual durable volumes. To confirm, scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod.

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 statefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.

B:

That statement explains the distinct objective “Design a release rollback trigger from measurable service signals” rather than the cause in this case. The deciding mechanism here is that statefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.

C:

That statement explains the distinct objective “Understand CSI drivers and volume attachment responsibilities” rather than the cause in this case. The deciding mechanism here is that statefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.

Question 693

A university runs a small stateful training database cluster whose members need persistent identities. Which controlled observation would best validate the intended improvement?

  1. Scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod.
  2. Test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.
  3. Inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload.
  4. Annotate a Deployment with release notes and verify its Service still selects Pods using explicit app labels.

Explanation

Correct Answer

A:

Scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod. This is the relevant test because statefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.

Incorrect Answers

B:

This check would help evaluate the distinct objective “Separate multi-tenant namespace governance from actual isolation guarantees”, but not the required result. For this case, scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod.

C:

This check would help evaluate the distinct objective “Understand CSI drivers and volume attachment responsibilities”, but not the required result. For this case, scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod.

D:

This check would help evaluate the distinct objective “Use annotations for tool metadata rather than workload selection”, but not the required result. For this case, scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod.

Question 694

A university runs a small stateful training database cluster whose members need persistent identities. An engineer proposes: “Use a Deployment with one shared writable volume and assume every stateful replica receives its own independent identity and durable disk.” What adverse outcome would be most direct?

  1. Replicas can collide on storage ownership and application state ordering assumptions fail.
  2. PersistentVolumeClaims remain Pending or Pods fail to mount because the required driver integration is missing.
  3. The Service still has no ready endpoints and clients continue to encounter unavailable responses.
  4. The observed rollout may expose far more users than intended because percentage routing was never configured.

Explanation

Correct Answer

A:

Replicas can collide on storage ownership and application state ordering assumptions fail. The shortcut creates this risk because statefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.

Incorrect Answers

B:

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 replicas can collide on storage ownership and application state ordering assumptions fail.

C:

That outcome concerns the distinct objective “Investigate readiness failures separately from liveness-related restarts”; it is not the most direct consequence of this shortcut. The relevant consequence is that replicas can collide on storage ownership and application state ordering assumptions fail.

D:

That outcome concerns the distinct objective “Distinguish canary and blue-green delivery strategies from Kubernetes Deployment defaults”; it is not the most direct consequence of this shortcut. The relevant consequence is that replicas can collide on storage ownership and application state ordering assumptions fail.

Question 695

A university runs a small stateful training database cluster whose members need persistent identities. What pair of supported action and practical verification should be approved?

  1. 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.
  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. Use a ClusterRole for cluster-scoped resources or reusable rule definitions, recognizing that a RoleBinding to a ClusterRole grants those rules only in one namespace for namespaced resources. Acceptance evidence: Bind a synthetic ClusterRole through RoleBinding in namespace-a, then verify access fails in namespace-b.
  4. 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.

Explanation

Correct Answer

D:

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 “Compare PV reclaim policies and explain data retention on PVC deletion” 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.

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 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:

This action and check address the distinct objective “Distinguish ClusterRoles from Roles and binding scope” 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 696

A hospital analytics service has three durable replicas that should not overwrite a shared data directory. 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. Select a StatefulSet with volumeClaimTemplates for a stateful clustered application requiring stable Pod names and individual durable volumes.
  3. Pin validated production images by registry digest and promote the same signed artifact across environments.
  4. Read Pod Events and node assignment to distinguish a Pod that cannot be scheduled from a scheduled Pod whose image cannot be pulled.

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. This resolves the issue because statefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy. To verify, scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod.

Incorrect Answers

A:

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

C:

This option addresses the distinct objective “Use an immutable image digest for exact deployment provenance”, not the immediate requirement. Tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label. For the stated case, statefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.

D:

This option addresses the distinct objective “Separate Pending scheduling failures from ImagePullBackOff errors”, not the immediate requirement. FailedScheduling occurs before node binding; ImagePullBackOff occurs when a node's kubelet cannot obtain the container image. For the stated case, statefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.

Question 697

A hospital analytics service has three durable replicas that should not overwrite a shared data directory. What underlying Kubernetes behavior is most relevant to this technical decision?

  1. Readiness affects endpoint eligibility while liveness can cause restarts; a startup probe defers other probe checks until initialization succeeds.
  2. StatefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.
  3. FailedScheduling occurs before node binding; ImagePullBackOff occurs when a node's kubelet cannot obtain the container image.
  4. A StorageClass defines how storage is provisioned and may use WaitForFirstConsumer to delay provisioning until scheduling requirements are known.

Explanation

Correct Answer

B:

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

Incorrect Answers

A:

That statement explains the distinct objective “Understand readiness, liveness and startup probes as different signals” rather than the cause in this case. The deciding mechanism here is that statefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.

C:

That statement explains the distinct objective “Separate Pending scheduling failures from ImagePullBackOff errors” rather than the cause in this case. The deciding mechanism here is that statefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.

D:

The situation is that a hospital analytics service has three durable replicas that should not overwrite a shared data directory. 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 statefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.

Question 698

A hospital analytics service has three durable replicas that should not overwrite a shared data directory. What acceptance check most directly confirms this requirement is met?

  1. Create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.
  2. Test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.
  3. Change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.
  4. Scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod.

Explanation

Correct Answer

D:

The situation is that a hospital analytics service has three durable replicas that should not overwrite a shared data directory. Scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod. This is the relevant test 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 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, scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod.

B:

The situation is that a hospital analytics service has three durable replicas that should not overwrite a shared data directory. This check would help evaluate the distinct objective “Separate multi-tenant namespace governance from actual isolation guarantees”, but not the required result. For this case, scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod.

C:

This check would help evaluate the distinct objective “Use rollout status and undo to validate and recover a Deployment release”, but not the required result. For this case, scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod.

Question 699

A hospital analytics service has three durable replicas that should not overwrite a shared data directory. The team suggests: “Use a Deployment with one shared writable volume and assume every stateful replica receives its own independent identity and durable disk.” Which failure should the reviewer anticipate?

  1. Replicas can collide on storage ownership and application state ordering assumptions fail.
  2. Credentials can leak through registries and the binaries cannot be compared as the same tested artifact.
  3. The claim remains Pending and dependent Pods cannot mount the missing volume.
  4. The subject receives unnecessary authority to alter privileged resources or unrelated namespaces.

Explanation

Correct Answer

A:

The situation is that a hospital analytics service has three durable replicas that should not overwrite a shared data directory. Replicas can collide on storage ownership and application state ordering assumptions fail. The shortcut creates this risk because statefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.

Incorrect Answers

B:

That outcome concerns the distinct objective “Externalize application configuration from an image while protecting secrets”; it is not the most direct consequence of this shortcut. The relevant consequence is that replicas can collide on storage ownership and application state ordering assumptions fail.

C:

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 replicas can collide on storage ownership and application state ordering assumptions fail.

D:

That outcome concerns the distinct objective “Implement namespaced RBAC Roles for least-privilege resource permissions”; it is not the most direct consequence of this shortcut. The relevant consequence is that replicas can collide on storage ownership and application state ordering assumptions fail.

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.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests