McAfee Secured

CNCF CKA Bundle

Exam Code: CKA

Exam Name Certified Kubernetes Administrator

Certification Provider: CNCF

Corresponding Certification: CKA

CNCF CKA Bundle $44.99

Pass CNCF CKA with Real Questions From Testking

Download Web's Best CKA Exam Preparation Materials Today

  • Questions & Answers

    CKA Questions & Answers

    58 Questions & Answers

    Questions & Answers Testing Engine software allows you to practice questions and answers in real CKA exam environment.

  • CKA Video Course

    CKA Video Course

    138 Video Lectures

    CKA Video Course is developed by CNCF Professionals to help you pass CKA exam.

    Description

    This course will improve your knowledge and skills required to pass Certified Kubernetes Administrator exam.
  • Study Guide

    CKA Study Guide

    268 PDF Pages

    Study Guide will give you a practical experience regarding the subject and provide an academic background. CKA Study Guide is available in PDF format.

Certified Kubernetes Administrator (CKA) Practice Tests

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Total Cost: $194.97
Bundle Price: $149.98

Purchase Individually

  • Questions & Answers

    Questions & Answers

    58 Questions

    $124.99
  • CKA Video Course

    Video Course

    138 Video Lectures

    $39.99
  • Study Guide

    Study Guide

    268 PDF Pages

    $29.99

CNCF CKA Practice Test 29

Question 280

A tenant can edit operator configuration custom resources outside its namespace due to a broad custom API RoleBinding. Following the proposed change—Restrict custom resource group, kind and namespace verbs using scoped RBAC policies—which observation best demonstrates that the particular fault is resolved?

  1. kubectl api-resources lists the new kind and an instance is accepted under the correct group/version.
  2. The operator returns healthy and the managed Deployment appears with the expected owner references.
  3. Controller events show successful status reconciliation without allowing unwanted spec modification.
  4. Impersonated edits fail outside the permitted namespace while intended local access remains.

Explanation

Correct Answer

D:

Impersonated edits fail outside the permitted namespace while intended local access remains. This validates the stated intervention—restrict custom resource group, kind and namespace verbs using scoped RBAC policies.—rather than an unrelated cluster change. The relevant mechanism is: New custom resource types participate in authorization using their API group and scope.

Incorrect Answers

A:

The API server must register an extension type before it can accept objects of that kind. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Impersonated edits fail outside the permitted namespace while intended local access remains.

B:

A CRD defines the API schema while a running controller implements the desired behavior. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Impersonated edits fail outside the permitted namespace while intended local access remains.

C:

Custom resource status updates are separately authorized from spec updates when status is enabled. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Impersonated edits fail outside the permitted namespace while intended local access remains.

Question 281

A cluster uses an internal Service named frontend but an Ingress backend references old-service after a rename. Following the proposed change—Update the Ingress backend service.name and the correct service port reference—which observation best demonstrates that the particular fault is resolved?

  1. The HTTPS listener presents the intended certificate for the host and forwards to the backend.
  2. Controller events clear missing-Service errors and the hostname reaches the new backend.
  3. The controller reconciles the Ingress and an external host/path probe reaches the Service.
  4. The intended controller accepts the Ingress and the undesired controller ignores it.

Explanation

Correct Answer

B:

Controller events clear missing-Service errors and the hostname reaches the new backend. This validates the stated intervention—update the Ingress backend service.name and the correct service port reference.—rather than an unrelated cluster change. The relevant mechanism is: Ingress rules point to Services by name and port within their namespace.

Incorrect Answers

A:

Ingress TLS termination depends on a usable referenced Secret and an active controller. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Controller events clear missing-Service errors and the hostname reaches the new backend.

C:

Ingress API objects do not themselves implement HTTP routing; a controller supplies the dataplane. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Controller events clear missing-Service errors and the hostname reaches the new backend.

D:

Ingress controllers commonly filter resources by configured IngressClass. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Controller events clear missing-Service errors and the hostname reaches the new backend.

Question 282

A database Pod uses a PVC name that exists in a different namespace and receives a not found error. Which Kubernetes administration action most directly addresses the observed failure?

  1. Create or reference the PVC in the Pod's own namespace with the approved storage configuration.
  2. Match the claim's accessModes, storage class and capacity to the intended static PV.
  3. Use supported same-namespace clone capabilities or a separate approved snapshot/restore transfer workflow.
  4. Perform the approved reclaim and rebind procedure, including handling stale claimRef where safe.

Explanation

Correct Answer

A:

Create or reference the PVC in the Pod's own namespace with the approved storage configuration. This corrects the specific failure because pVCs are namespace-scoped and Pods cannot mount another namespace's claim by name. Verify it by checking: The Pod's namespace contains the referenced claim and volume mounts successfully.

Incorrect Answers

B:

A PVC must satisfy PV binding predicates, not merely request a compatible size. That is relevant to a different intervention. For the stated situation, the required action is: Create or reference the PVC in the Pod's own namespace with the approved storage configuration. The governing reason is: PVCs are namespace-scoped and Pods cannot mount another namespace's claim by name.

C:

PVC cloning and dataSource references have scope and driver capability constraints. That is relevant to a different intervention. For the stated situation, the required action is: Create or reference the PVC in the Pod's own namespace with the approved storage configuration. The governing reason is: PVCs are namespace-scoped and Pods cannot mount another namespace's claim by name.

D:

A Released PV may preserve its previous claim reference until an administrator makes it available. That is relevant to a different intervention. For the stated situation, the required action is: Create or reference the PVC in the Pod's own namespace with the approved storage configuration. The governing reason is: PVCs are namespace-scoped and Pods cannot mount another namespace's claim by name.

Question 283

A worker shows MemoryPressure while one batch Pod repeatedly exceeds its memory limit. Which Kubernetes administration action most directly addresses the observed failure?

  1. Inspect process counts and runaway process creation, then cap or repair the offending workload.
  2. Inspect memory metrics and OOMKilled events, then right-size the Pod and add safe limits or capacity.
  3. Identify and clean safe image or container filesystem usage and expand capacity if needed.
  4. Renew or rotate kubelet client credentials using the supported cluster certificate process.

Explanation

Correct Answer

B:

Inspect memory metrics and OOMKilled events, then right-size the Pod and add safe limits or capacity. This corrects the specific failure because the kernel and kubelet can terminate memory-hungry containers independently of scheduler requests. Verify it by checking: The workload completes under tested memory bounds and node pressure clears.

Incorrect Answers

A:

Node PIDPressure reflects process-ID exhaustion rather than CPU, memory or disk usage. That is relevant to a different intervention. For the stated situation, the required action is: Inspect memory metrics and OOMKilled events, then right-size the Pod and add safe limits or capacity. The governing reason is: The kernel and kubelet can terminate memory-hungry containers independently of scheduler requests.

C:

Kubelet disk-pressure signals can cause eviction and scheduling taints independent of CPU utilization. That is relevant to a different intervention. For the stated situation, the required action is: Inspect memory metrics and OOMKilled events, then right-size the Pod and add safe limits or capacity. The governing reason is: The kernel and kubelet can terminate memory-hungry containers independently of scheduler requests.

D:

Node status updates require authenticated kubelet API requests using valid credentials. That is relevant to a different intervention. For the stated situation, the required action is: Inspect memory metrics and OOMKilled events, then right-size the Pod and add safe limits or capacity. The governing reason is: The kernel and kubelet can terminate memory-hungry containers independently of scheduler requests.

Question 284

A bare-metal worker can contact the API but cannot pull images because the container runtime is not configured correctly. An engineer recommends: Configure a compatible CRI runtime and its cgroup driver consistently with the kubelet. Which Kubernetes behavior best explains why this correction fits?

  1. Node prerequisites must be consistent with kubelet behavior and runtime support.
  2. Clients and join operations need a durable API endpoint independent of one control-plane host.
  3. Conflicting cluster and external address spaces can misroute traffic even when the API server is healthy.
  4. The kubelet delegates container creation to a CRI-compatible runtime and requires compatible host settings.

Explanation

Correct Answer

D:

The kubelet delegates container creation to a CRI-compatible runtime and requires compatible host settings. This explains why the proposed action—configure a compatible CRI runtime and its cgroup driver consistently with the kubelet.—is appropriate. Direct confirmation is: crictl can query the runtime endpoint and a test Pod starts successfully.

Incorrect Answers

A:

Node prerequisites must be consistent with kubelet behavior and runtime support. This does not establish the proposed intervention. The governing principle here is: The kubelet delegates container creation to a CRI-compatible runtime and requires compatible host settings. Apply it by: Configure a compatible CRI runtime and its cgroup driver consistently with the kubelet.

B:

Clients and join operations need a durable API endpoint independent of one control-plane host. This does not establish the proposed intervention. The governing principle here is: The kubelet delegates container creation to a CRI-compatible runtime and requires compatible host settings. Apply it by: Configure a compatible CRI runtime and its cgroup driver consistently with the kubelet.

C:

Conflicting cluster and external address spaces can misroute traffic even when the API server is healthy. This does not establish the proposed intervention. The governing principle here is: The kubelet delegates container creation to a CRI-compatible runtime and requires compatible host settings. Apply it by: Configure a compatible CRI runtime and its cgroup driver consistently with the kubelet.

Question 285

A Pod stays Pending because required pod affinity points to a label that no existing Pod has. An engineer recommends: Correct the label selector or intentionally seed the matching workload after validating the placement requirement. Which Kubernetes behavior best explains why this correction fits?

  1. Preferred affinity influences scoring but is not a hard scheduling constraint.
  2. Required pod affinity is a hard predicate and cannot match nonexistent target Pods.
  3. The scheduler matches Pod node constraints to node labels and available resources.
  4. Affinity and spread rules influence placement of replicas across nodes or zones.

Explanation

Correct Answer

B:

Required pod affinity is a hard predicate and cannot match nonexistent target Pods. This explains why the proposed action—correct the label selector or intentionally seed the matching workload after validating the placement requirement.—is appropriate. Direct confirmation is: A matching eligible Pod exists in the specified topology and the new Pod schedules.

Incorrect Answers

A:

Preferred affinity influences scoring but is not a hard scheduling constraint. This does not establish the proposed intervention. The governing principle here is: Required pod affinity is a hard predicate and cannot match nonexistent target Pods. Apply it by: Correct the label selector or intentionally seed the matching workload after validating the placement requirement.

C:

The scheduler matches Pod node constraints to node labels and available resources. This does not establish the proposed intervention. The governing principle here is: Required pod affinity is a hard predicate and cannot match nonexistent target Pods. Apply it by: Correct the label selector or intentionally seed the matching workload after validating the placement requirement.

D:

Affinity and spread rules influence placement of replicas across nodes or zones. This does not establish the proposed intervention. The governing principle here is: Required pod affinity is a hard predicate and cannot match nonexistent target Pods. Apply it by: Correct the label selector or intentionally seed the matching workload after validating the placement requirement.

Question 286

A stateful cache requires a stable identity for each Pod but is currently managed as interchangeable Deployment replicas. Following the proposed change—Use a StatefulSet with the required stable identity and appropriately provisioned storage—which observation best demonstrates that the particular fault is resolved?

  1. During a controlled rollout, the configured availability floor is maintained while new Pods become Ready.
  2. Pods retain stable ordinal network identities and corresponding storage across replacement.
  3. kubectl rollout status shows the prior revision fully available and application probes succeed.
  4. The desired replica count is ready under the new image and old ReplicaSet replicas are reduced.

Explanation

Correct Answer

B:

Pods retain stable ordinal network identities and corresponding storage across replacement. This validates the stated intervention—use a StatefulSet with the required stable identity and appropriately provisioned storage.—rather than an unrelated cluster change. The relevant mechanism is: StatefulSets provide ordered identities and stable per-Pod names where identity matters.

Incorrect Answers

A:

The Deployment rollout strategy controls the allowed temporary excess and unavailable replicas. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Pods retain stable ordinal network identities and corresponding storage across replacement.

C:

Deployment revisions track supported rollout history and a rollback restores a previous Pod template. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Pods retain stable ordinal network identities and corresponding storage across replacement.

D:

Desired-state changes are asynchronous and a successful API update is not proof of healthy Pods. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Pods retain stable ordinal network identities and corresponding storage across replacement.

Question 287

A Gateway is deployed but the namespace's HTTPRoute has no permission to attach across namespace boundaries. Which Kubernetes administration action most directly addresses the observed failure?

  1. Change parentRefs sectionName or create the intended listener and confirm route attachment status.
  2. Inspect the GatewayClass controller and Gateway listener conditions before debugging application Pods.
  3. Use a namespaceSelector matching an explicitly approved label and combine with podSelector when appropriate.
  4. Configure the listener allowedRoutes namespaces policy or appropriate cross-namespace reference permissions.

Explanation

Correct Answer

D:

Configure the listener allowedRoutes namespaces policy or appropriate cross-namespace reference permissions. This corrects the specific failure because gateway API constrains route attachment and cross-namespace references through explicit policies. Verify it by checking: The intended route becomes Accepted only from an approved namespace.

Incorrect Answers

A:

Gateway API HTTPRoutes must attach to compatible allowed listeners through parent references. That is relevant to a different intervention. For the stated situation, the required action is: Configure the listener allowedRoutes namespaces policy or appropriate cross-namespace reference permissions. The governing reason is: Gateway API constrains route attachment and cross-namespace references through explicit policies.

B:

Gateway API resources require an implementing controller to provision and program data-plane listeners. That is relevant to a different intervention. For the stated situation, the required action is: Configure the listener allowedRoutes namespaces policy or appropriate cross-namespace reference permissions. The governing reason is: Gateway API constrains route attachment and cross-namespace references through explicit policies.

C:

An empty namespaceSelector matches all namespaces; namespace and Pod peers must be scoped deliberately. That is relevant to a different intervention. For the stated situation, the required action is: Configure the listener allowedRoutes namespaces policy or appropriate cross-namespace reference permissions. The governing reason is: Gateway API constrains route attachment and cross-namespace references through explicit policies.

Question 288

A stateful Pod requests a PVC from a StorageClass using a CSI driver that is healthy on control-plane nodes but not on workers. Following the proposed change—Install and verify the CSI node plugin on every eligible attachment node—which observation best demonstrates that the particular fault is resolved?

  1. A test PVC becomes Bound and the expected CSI volume is created.
  2. A test PV is created with the required encryption setting reported by the storage provider.
  3. The PVC is Bound and a consumer on each eligible worker mounts and reads the volume.
  4. The storage driver reports successful attachment to the replacement node and the Pod mounts correctly.

Explanation

Correct Answer

C:

The PVC is Bound and a consumer on each eligible worker mounts and reads the volume. This validates the stated intervention—install and verify the CSI node plugin on every eligible attachment node.—rather than an unrelated cluster change. The relevant mechanism is: A controller may provision a volume while the node-side CSI plugin is still required to mount it.

Incorrect Answers

A:

Dynamic provisioning depends on a controller that recognizes the StorageClass provisioner identifier. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The PVC is Bound and a consumer on each eligible worker mounts and reads the volume.

B:

StorageClass parameters are driver-specific and determine backend provisioning behavior. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The PVC is Bound and a consumer on each eligible worker mounts and reads the volume.

D:

A Bound PVC proves allocation but not that attach, stage and publish operations have succeeded. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The PVC is Bound and a consumer on each eligible worker mounts and reads the volume.

Question 289

A filesystem volume is mounted read-only by a Pod even though the application needs to write state. An engineer recommends: Correct the Pod volumeMount readOnly setting and validate the PV and backend's supported access. Which Kubernetes behavior best explains why this correction fits?

  1. Mount-level read-only settings can prohibit writes regardless of a backend's broader capabilities.
  2. Kubernetes access modes express requested attachment semantics but cannot add capability to a backend.
  3. Reclaim policy determines what happens to backend storage after a bound claim is released.
  4. hostPath refers to a specific node filesystem and does not provide cluster-wide data mobility.

Explanation

Correct Answer

A:

Mount-level read-only settings can prohibit writes regardless of a backend's broader capabilities. This explains why the proposed action—correct the Pod volumeMount readOnly setting and validate the PV and backend's supported access.—is appropriate. Direct confirmation is: The approved Pod writes a test file and unauthorized consumers remain restricted.

Incorrect Answers

B:

Kubernetes access modes express requested attachment semantics but cannot add capability to a backend. This does not establish the proposed intervention. The governing principle here is: Mount-level read-only settings can prohibit writes regardless of a backend's broader capabilities. Apply it by: Correct the Pod volumeMount readOnly setting and validate the PV and backend's supported access.

C:

Reclaim policy determines what happens to backend storage after a bound claim is released. This does not establish the proposed intervention. The governing principle here is: Mount-level read-only settings can prohibit writes regardless of a backend's broader capabilities. Apply it by: Correct the Pod volumeMount readOnly setting and validate the PV and backend's supported access.

D:

hostPath refers to a specific node filesystem and does not provide cluster-wide data mobility. This does not establish the proposed intervention. The governing principle here is: Mount-level read-only settings can prohibit writes regardless of a backend's broader capabilities. Apply it by: Correct the Pod volumeMount readOnly setting and validate the PV and backend's supported access.

Question 290

An etcd member is removed after a disk failure, but nobody checks whether the remaining members have quorum. An engineer recommends: Inspect etcd endpoint status and membership before modifying the cluster's voter set. Which Kubernetes behavior best explains why this correction fits?

  1. Quorum and replication do not protect against a common power or hypervisor failure domain.
  2. Highly available control planes depend on load-balanced API access and durable quorum-backed state.
  3. Etcd commits require a majority of voting members; removal and replacement must preserve quorum.
  4. A successful TCP handshake does not prove a particular API server is ready to serve requests.

Explanation

Correct Answer

C:

Etcd commits require a majority of voting members; removal and replacement must preserve quorum. This explains why the proposed action—inspect etcd endpoint status and membership before modifying the cluster's voter set.—is appropriate. Direct confirmation is: The member list and endpoint health show an operational majority before and after the change.

Incorrect Answers

A:

Quorum and replication do not protect against a common power or hypervisor failure domain. This does not establish the proposed intervention. The governing principle here is: Etcd commits require a majority of voting members; removal and replacement must preserve quorum. Apply it by: Inspect etcd endpoint status and membership before modifying the cluster's voter set.

B:

Highly available control planes depend on load-balanced API access and durable quorum-backed state. This does not establish the proposed intervention. The governing principle here is: Etcd commits require a majority of voting members; removal and replacement must preserve quorum. Apply it by: Inspect etcd endpoint status and membership before modifying the cluster's voter set.

D:

A successful TCP handshake does not prove a particular API server is ready to serve requests. This does not establish the proposed intervention. The governing principle here is: Etcd commits require a majority of voting members; removal and replacement must preserve quorum. Apply it by: Inspect etcd endpoint status and membership before modifying the cluster's voter set.