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 36

Question 350

A tenant can edit operator configuration custom resources outside its namespace due to a broad custom API RoleBinding. Which Kubernetes administration action most directly addresses the observed failure?

  1. Install the CRD and wait for its Established condition before applying dependent custom resources.
  2. Restore the controller/operator and check reconciliation logs and permissions before changing the custom object.
  3. Restrict custom resource group, kind and namespace verbs using scoped RBAC policies.
  4. Grant the controller the minimum required update or patch permission for the status subresource.

Explanation

Correct Answer

C:

Restrict custom resource group, kind and namespace verbs using scoped RBAC policies. This corrects the specific failure because new custom resource types participate in authorization using their API group and scope. Verify it by checking: Impersonated edits fail outside the permitted namespace while intended local access remains.

Incorrect Answers

A:

The API server must register an extension type before it can accept objects of that kind. That is relevant to a different intervention. For the stated situation, the required action is: Restrict custom resource group, kind and namespace verbs using scoped RBAC policies. The governing reason is: New custom resource types participate in authorization using their API group and scope.

B:

A CRD defines the API schema while a running controller implements the desired behavior. That is relevant to a different intervention. For the stated situation, the required action is: Restrict custom resource group, kind and namespace verbs using scoped RBAC policies. The governing reason is: New custom resource types participate in authorization using their API group and scope.

D:

Custom resource status updates are separately authorized from spec updates when status is enabled. That is relevant to a different intervention. For the stated situation, the required action is: Restrict custom resource group, kind and namespace verbs using scoped RBAC policies. The governing reason is: New custom resource types participate in authorization using their API group and scope.

Question 351

A database Pod keeps landing on the same node as another replica despite the service's resilience goal. Following the proposed change—Use appropriate podAntiAffinity or topology spread constraints for the intended failure domains—which observation best demonstrates that the particular fault is resolved?

  1. The replicas appear across the required topology domains after a controlled reschedule.
  2. A matching eligible Pod exists in the specified topology and the new Pod schedules.
  3. Scheduling tests reject nodes that lack the required sovereignty label.
  4. The Pod schedules onto a matching GPU node and a nonmatching node is excluded.

Explanation

Correct Answer

A:

The replicas appear across the required topology domains after a controlled reschedule. This validates the stated intervention—use appropriate podAntiAffinity or topology spread constraints for the intended failure domains.—rather than an unrelated cluster change. The relevant mechanism is: Affinity and spread rules influence placement of replicas across nodes or zones.

Incorrect Answers

B:

Required pod affinity is a hard predicate and cannot match nonexistent target Pods. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The replicas appear across the required topology domains after a controlled reschedule.

C:

Preferred affinity influences scoring but is not a hard scheduling constraint. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The replicas appear across the required topology domains after a controlled reschedule.

D:

The scheduler matches Pod node constraints to node labels and available resources. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The replicas appear across the required topology domains after a controlled reschedule.

Question 352

A control-plane host lacks swap configuration compatible with the kubelet and new Pods remain unscheduled after provisioning. Which Kubernetes administration action most directly addresses the observed failure?

  1. Configure a compatible CRI runtime and its cgroup driver consistently with the kubelet.
  2. Validate the stable controlPlaneEndpoint name and its reachable load balancer before kubeadm initialization.
  3. Open only documented kubeadm control-plane, etcd, and kubelet communication paths for the intended topology.
  4. Align swap settings and kubelet configuration with supported Kubernetes host prerequisites before join.

Explanation

Correct Answer

D:

Align swap settings and kubelet configuration with supported Kubernetes host prerequisites before join. This corrects the specific failure because node prerequisites must be consistent with kubelet behavior and runtime support. Verify it by checking: The kubelet starts without swap-related errors and the node becomes Ready.

Incorrect Answers

A:

The kubelet delegates container creation to a CRI-compatible runtime and requires compatible host settings. That is relevant to a different intervention. For the stated situation, the required action is: Align swap settings and kubelet configuration with supported Kubernetes host prerequisites before join. The governing reason is: Node prerequisites must be consistent with kubelet behavior and runtime support.

B:

Clients and join operations need a durable API endpoint independent of one control-plane host. That is relevant to a different intervention. For the stated situation, the required action is: Align swap settings and kubelet configuration with supported Kubernetes host prerequisites before join. The governing reason is: Node prerequisites must be consistent with kubelet behavior and runtime support.

C:

Bootstrap and reconciliation require distinct network flows among the API server, etcd, and nodes. That is relevant to a different intervention. For the stated situation, the required action is: Align swap settings and kubelet configuration with supported Kubernetes host prerequisites before join. The governing reason is: Node prerequisites must be consistent with kubelet behavior and runtime support.

Question 353

A Secret update is expected to replace a running process's environment value immediately without restarting the container. Which Kubernetes administration action most directly addresses the observed failure?

  1. Roll out the workload or make the application reread supported projected files as required.
  2. Align the Secret key name and the Pod's secretKeyRef with the application contract.
  3. Externalize the host into a ConfigMap and consume it through environment variables or a mounted configuration volume.
  4. Configure rolling-update maxUnavailable and maxSurge according to available capacity and readiness requirements.

Explanation

Correct Answer

A:

Roll out the workload or make the application reread supported projected files as required. This corrects the specific failure because environment variables sourced from Secrets are fixed for the lifetime of a container process. Verify it by checking: New Pods use the updated Secret value and old processes terminate in a controlled rollout.

Incorrect Answers

B:

Secret key references are exact and missing mandatory keys prevent valid container configuration. That is relevant to a different intervention. For the stated situation, the required action is: Roll out the workload or make the application reread supported projected files as required. The governing reason is: Environment variables sourced from Secrets are fixed for the lifetime of a container process.

C:

ConfigMaps separate nonsecret configuration from the application container image. That is relevant to a different intervention. For the stated situation, the required action is: Roll out the workload or make the application reread supported projected files as required. The governing reason is: Environment variables sourced from Secrets are fixed for the lifetime of a container process.

D:

The Deployment rollout strategy controls the allowed temporary excess and unavailable replicas. That is relevant to a different intervention. For the stated situation, the required action is: Roll out the workload or make the application reread supported projected files as required. The governing reason is: Environment variables sourced from Secrets are fixed for the lifetime of a container process.

Question 354

A team uses kubectl logs against a Pending Pod and assumes no log output proves the image is healthy. Which Kubernetes administration action most directly addresses the observed failure?

  1. Retrieve the previous container instance logs and examine termination reason alongside current output.
  2. Inspect Pod events and waiting reasons before expecting a container log stream.
  3. Configure the app or log collector to expose relevant output streams and preserve needed files.
  4. Specify the container name when retrieving Pod logs and compare related containers' output.

Explanation

Correct Answer

B:

Inspect Pod events and waiting reasons before expecting a container log stream. This corrects the specific failure because containers that never start may have no runtime logs; scheduling and image events carry the relevant diagnosis. Verify it by checking: The exact Pending or waiting reason is found and the first successful start produces log output.

Incorrect Answers

A:

Restarted containers can have a previous log stream that is distinct from the current one. That is relevant to a different intervention. For the stated situation, the required action is: Inspect Pod events and waiting reasons before expecting a container log stream. The governing reason is: Containers that never start may have no runtime logs; scheduling and image events carry the relevant diagnosis.

C:

kubectl logs primarily reads the container runtime's captured stdout and stderr streams. That is relevant to a different intervention. For the stated situation, the required action is: Inspect Pod events and waiting reasons before expecting a container log stream. The governing reason is: Containers that never start may have no runtime logs; scheduling and image events carry the relevant diagnosis.

D:

Container logs belong to individual containers even within one Pod. That is relevant to a different intervention. For the stated situation, the required action is: Inspect Pod events and waiting reasons before expecting a container log stream. The governing reason is: Containers that never start may have no runtime logs; scheduling and image events carry the relevant diagnosis.

Question 355

An HPA oscillates between minimum and maximum replicas, and the team only watches its current desired count. Which Kubernetes administration action most directly addresses the observed failure?

  1. Inspect last termination reasons and memory working-set trends, then right-size limits and alerting.
  2. Inspect image filesystem consumption and kubelet garbage collection thresholds before changing policies.
  3. Compare kubectl describe Pod scheduling events with node allocatable and total requested resources.
  4. Inspect HPA events, metric availability and scaling behavior over time before tuning thresholds.

Explanation

Correct Answer

D:

Inspect HPA events, metric availability and scaling behavior over time before tuning thresholds. This corrects the specific failure because autoscaling dynamics depend on metric sampling, requests and stabilization parameters. Verify it by checking: A controlled load pattern produces bounded replica changes without repeated rapid oscillation.

Incorrect Answers

A:

OOMKilled is evidence of memory-limit or node memory pressure, not an ordinary successful exit. That is relevant to a different intervention. For the stated situation, the required action is: Inspect HPA events, metric availability and scaling behavior over time before tuning thresholds. The governing reason is: Autoscaling dynamics depend on metric sampling, requests and stabilization parameters.

B:

Image storage pressure and image garbage collection are distinct from application CPU demand. That is relevant to a different intervention. For the stated situation, the required action is: Inspect HPA events, metric availability and scaling behavior over time before tuning thresholds. The governing reason is: Autoscaling dynamics depend on metric sampling, requests and stabilization parameters.

C:

Scheduling uses resource requests and constraints, not recent utilization percentages alone. That is relevant to a different intervention. For the stated situation, the required action is: Inspect HPA events, metric availability and scaling behavior over time before tuning thresholds. The governing reason is: Autoscaling dynamics depend on metric sampling, requests and stabilization parameters.

Question 356

A node reports DiskPressure and new Pods cannot be admitted although CPU and memory are available. An engineer recommends: Identify and clean safe image or container filesystem usage and expand capacity if needed. Which Kubernetes behavior best explains why this correction fits?

  1. Node PIDPressure reflects process-ID exhaustion rather than CPU, memory or disk usage.
  2. The kernel and kubelet can terminate memory-hungry containers independently of scheduler requests.
  3. Kubelet disk-pressure signals can cause eviction and scheduling taints independent of CPU utilization.
  4. Node readiness can depend on successful Pod network initialization.

Explanation

Correct Answer

C:

Kubelet disk-pressure signals can cause eviction and scheduling taints independent of CPU utilization. This explains why the proposed action—identify and clean safe image or container filesystem usage and expand capacity if needed.—is appropriate. Direct confirmation is: Node DiskPressure clears and new Pods are admitted without deleting active volume data.

Incorrect Answers

A:

Node PIDPressure reflects process-ID exhaustion rather than CPU, memory or disk usage. This does not establish the proposed intervention. The governing principle here is: Kubelet disk-pressure signals can cause eviction and scheduling taints independent of CPU utilization. Apply it by: Identify and clean safe image or container filesystem usage and expand capacity if needed.

B:

The kernel and kubelet can terminate memory-hungry containers independently of scheduler requests. This does not establish the proposed intervention. The governing principle here is: Kubelet disk-pressure signals can cause eviction and scheduling taints independent of CPU utilization. Apply it by: Identify and clean safe image or container filesystem usage and expand capacity if needed.

D:

Node readiness can depend on successful Pod network initialization. This does not establish the proposed intervention. The governing principle here is: Kubelet disk-pressure signals can cause eviction and scheduling taints independent of CPU utilization. Apply it by: Identify and clean safe image or container filesystem usage and expand capacity if needed.

Question 357

A new cluster shows repeated leader-election failures between scheduler replicas because API access fluctuates. Following the proposed change—Repair API endpoint reachability and lease storage health before forcing a leader—which observation best demonstrates that the particular fault is resolved?

  1. The scheduler becomes healthy and newly created Pods receive node assignments.
  2. etcd endpoint health and a safe API create or update operation both succeed.
  3. One scheduler leader holds the lease and normal scheduling resumes under stable API access.
  4. kubectl establishes a verified TLS session to the intended endpoint without insecure skipping.

Explanation

Correct Answer

C:

One scheduler leader holds the lease and normal scheduling resumes under stable API access. This validates the stated intervention—repair API endpoint reachability and lease storage health before forcing a leader.—rather than an unrelated cluster change. The relevant mechanism is: Leader election requires reliable access to coordination Lease objects in the cluster API.

Incorrect Answers

A:

The scheduler assigns unscheduled Pods to eligible nodes; other control-plane components cannot replace it. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: One scheduler leader holds the lease and normal scheduling resumes under stable API access.

B:

Etcd requires a majority of voters to commit changes; an API listener alone does not imply healthy storage. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: One scheduler leader holds the lease and normal scheduling resumes under stable API access.

D:

Clients validate control-plane TLS certificate identity before trusting API responses. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: One scheduler leader holds the lease and normal scheduling resumes under stable API access.

Question 358

A load balancer health check probes only TCP 6443 and continues routing clients to an API server that is not ready. What is the most direct consequence if the underlying problem is left unresolved?

  1. Clients may receive repeated failed API requests despite healthy peer servers.
  2. A single failed VM can halt changes and prevent the control plane from reconciling.
  3. Certificate name mismatch can block administrative and node API access.
  4. Unsafe voter changes can make the cluster state store unavailable.

Explanation

Correct Answer

A:

Clients may receive repeated failed API requests despite healthy peer servers. This directly follows from the failed condition. The preventive correction is: Configure a readiness-aware control-plane health check compatible with the API service. The governing Kubernetes behavior is: A successful TCP handshake does not prove a particular API server is ready to serve requests.

Incorrect Answers

B:

Highly available control planes depend on load-balanced API access and durable quorum-backed state. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Clients may receive repeated failed API requests despite healthy peer servers.

C:

TLS clients verify the endpoint hostname against the presented certificate SANs. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Clients may receive repeated failed API requests despite healthy peer servers.

D:

Etcd commits require a majority of voting members; removal and replacement must preserve quorum. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Clients may receive repeated failed API requests despite healthy peer servers.

Question 359

A Gateway route splits traffic between two backend Services but weight settings send most requests to an untested canary. An engineer recommends: Adjust backendRefs weights and validate rollout percentages before production promotion. Which Kubernetes behavior best explains why this correction fits?

  1. Gateway API HTTPRoutes must attach to compatible allowed listeners through parent references.
  2. Gateway API constrains route attachment and cross-namespace references through explicit policies.
  3. Exact and prefix path matches are different routing rules in Gateway API.
  4. Gateway API backend weights influence proportional HTTPRoute forwarding among valid backends.

Explanation

Correct Answer

D:

Gateway API backend weights influence proportional HTTPRoute forwarding among valid backends. This explains why the proposed action—adjust backendRefs weights and validate rollout percentages before production promotion.—is appropriate. Direct confirmation is: Observed test traffic approximates approved weights and both backends report ready.

Incorrect Answers

A:

Gateway API HTTPRoutes must attach to compatible allowed listeners through parent references. This does not establish the proposed intervention. The governing principle here is: Gateway API backend weights influence proportional HTTPRoute forwarding among valid backends. Apply it by: Adjust backendRefs weights and validate rollout percentages before production promotion.

B:

Gateway API constrains route attachment and cross-namespace references through explicit policies. This does not establish the proposed intervention. The governing principle here is: Gateway API backend weights influence proportional HTTPRoute forwarding among valid backends. Apply it by: Adjust backendRefs weights and validate rollout percentages before production promotion.

C:

Exact and prefix path matches are different routing rules in Gateway API. This does not establish the proposed intervention. The governing principle here is: Gateway API backend weights influence proportional HTTPRoute forwarding among valid backends. Apply it by: Adjust backendRefs weights and validate rollout percentages before production promotion.

Question 360

A new cluster shows repeated leader-election failures between scheduler replicas because API access fluctuates. Which Kubernetes administration action most directly addresses the observed failure?

  1. Repair the scheduler manifest or configuration after inspecting static Pod logs.
  2. Repair API endpoint reachability and lease storage health before forcing a leader.
  3. Inspect etcd membership and quorum health, then restore sufficient approved voting members.
  4. Regenerate the affected serving certificate with the actual API endpoint names and rotate it safely.

Explanation

Correct Answer

B:

Repair API endpoint reachability and lease storage health before forcing a leader. This corrects the specific failure because leader election requires reliable access to coordination Lease objects in the cluster API. Verify it by checking: One scheduler leader holds the lease and normal scheduling resumes under stable API access.

Incorrect Answers

A:

The scheduler assigns unscheduled Pods to eligible nodes; other control-plane components cannot replace it. That is relevant to a different intervention. For the stated situation, the required action is: Repair API endpoint reachability and lease storage health before forcing a leader. The governing reason is: Leader election requires reliable access to coordination Lease objects in the cluster API.

C:

Etcd requires a majority of voters to commit changes; an API listener alone does not imply healthy storage. That is relevant to a different intervention. For the stated situation, the required action is: Repair API endpoint reachability and lease storage health before forcing a leader. The governing reason is: Leader election requires reliable access to coordination Lease objects in the cluster API.

D:

Clients validate control-plane TLS certificate identity before trusting API responses. That is relevant to a different intervention. For the stated situation, the required action is: Repair API endpoint reachability and lease storage health before forcing a leader. The governing reason is: Leader election requires reliable access to coordination Lease objects in the cluster API.