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 46

Question 450

A Pod can resolve internal Services but outbound internet requests hang after a new default-deny egress policy. Following the proposed change—Inspect applicable NetworkPolicies and permit explicitly required external traffic and DNS—which observation best demonstrates that the particular fault is resolved?

  1. Approved west-to-east connections succeed while unauthorized namespaces remain blocked.
  2. Approved external probes succeed while prohibited destinations remain blocked.
  3. Fresh Pods on previously broken nodes resolve internal and external names through the configured listener.
  4. Probes reach the same healthy backend through each intended node and port.

Explanation

Correct Answer

B:

Approved external probes succeed while prohibited destinations remain blocked. This validates the stated intervention—inspect applicable NetworkPolicies and permit explicitly required external traffic and DNS.—rather than an unrelated cluster change. The relevant mechanism is: Egress isolation may deny flows independently of Service discovery and Pod health.

Incorrect Answers

A:

Both source egress and destination ingress policies can restrict a cross-namespace flow. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Approved external probes succeed while prohibited destinations remain blocked.

C:

Per-node DNS cache configuration can produce node-specific resolution failures. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Approved external probes succeed while prohibited destinations remain blocked.

D:

Service reachability depends on node packet-forwarding rules and network acceptance at entry nodes. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Approved external probes succeed while prohibited destinations remain blocked.

Question 451

A log-gathering command returns nothing because the responder queried an old namespace after a team migration. Following the proposed change—Resolve the actual namespace and label selector before requesting the current workload's logs—which observation best demonstrates that the particular fault is resolved?

  1. The captured output contains the incident window with reproducible source metadata.
  2. The exact Pending or waiting reason is found and the first successful start produces log output.
  3. kubectl logs --previous surfaces the original failure and event timestamps align.
  4. The queried Pods and log lines match the current deployment namespace and time window.

Explanation

Correct Answer

D:

The queried Pods and log lines match the current deployment namespace and time window. This validates the stated intervention—resolve the actual namespace and label selector before requesting the current workload's logs.—rather than an unrelated cluster change. The relevant mechanism is: kubectl resource lookups are namespace-scoped unless explicitly configured otherwise.

Incorrect Answers

A:

kubectl log filters help isolate relevant events and reduce diagnostic noise. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The queried Pods and log lines match the current deployment namespace and time window.

B:

Containers that never start may have no runtime logs; scheduling and image events carry the relevant diagnosis. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The queried Pods and log lines match the current deployment namespace and time window.

C:

Restarted containers can have a previous log stream that is distinct from the current one. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The queried Pods and log lines match the current deployment namespace and time window.

Question 452

A new cluster shows repeated leader-election failures between scheduler replicas because API access fluctuates. What is the most direct consequence if the underlying problem is left unresolved?

  1. Ready nodes may sit idle while unscheduled workloads accumulate.
  2. Unstable leadership can produce intermittent reconciliation delays.
  3. Read-only-looking API availability can conceal inability to persist state.
  4. Administrative automation can stop working after certificate rotation.

Explanation

Correct Answer

B:

Unstable leadership can produce intermittent reconciliation delays. This directly follows from the failed condition. The preventive correction is: Repair API endpoint reachability and lease storage health before forcing a leader. The governing Kubernetes behavior 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. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Unstable leadership can produce intermittent reconciliation delays.

C:

Etcd requires a majority of voters to commit changes; an API listener alone does not imply healthy storage. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Unstable leadership can produce intermittent reconciliation delays.

D:

Clients validate control-plane TLS certificate identity before trusting API responses. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Unstable leadership can produce intermittent reconciliation delays.

Question 453

An incident responder has permission to create Pods but not to attach interactively to running containers. Following the proposed change—Grant the narrowly required pods/attach or pods/exec subresource verbs according to the approved response workflow—which observation best demonstrates that the particular fault is resolved?

  1. Impersonated requests reach the approved subresource and reject unrelated secret reads.
  2. An impersonated service-account access test reads the permitted Secret and rejects unrelated Secrets.
  3. An impersonated authorization check denies deletion in another team's namespace but permits the required local update.
  4. kubectl auth can-i checks show read-only access on log inputs and denial of workload modification.

Explanation

Correct Answer

A:

Impersonated requests reach the approved subresource and reject unrelated secret reads. This validates the stated intervention—grant the narrowly required pods/attach or pods/exec subresource verbs according to the approved response workflow.—rather than an unrelated cluster change. The relevant mechanism is: RBAC treats interactive Pod subresources separately from operations on the parent Pod resource.

Incorrect Answers

B:

Kubernetes service accounts do not automatically inherit administrator permissions from the Pod owner. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Impersonated requests reach the approved subresource and reject unrelated secret reads.

C:

A RoleBinding restricts a Role or referenced ClusterRole to its own namespace; a ClusterRoleBinding grants across namespaces. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Impersonated requests reach the approved subresource and reject unrelated secret reads.

D:

Least-privilege RBAC narrows blast radius by limiting the allowed verbs, resources, and API groups. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Impersonated requests reach the approved subresource and reject unrelated secret reads.

Question 454

A container restarts after crashing and kubectl logs without flags shows only output from the new process. Following the proposed change—Retrieve the previous container instance logs and examine termination reason alongside current output—which observation best demonstrates that the particular fault is resolved?

  1. The exact Pending or waiting reason is found and the first successful start produces log output.
  2. kubectl logs --previous surfaces the original failure and event timestamps align.
  3. A controlled failure appears in retrieved logs with sufficient timestamps and context.
  4. Logs from the failing sidecar reveal the error while the app container's normal output is distinguished.

Explanation

Correct Answer

B:

kubectl logs --previous surfaces the original failure and event timestamps align. This validates the stated intervention—retrieve the previous container instance logs and examine termination reason alongside current output.—rather than an unrelated cluster change. The relevant mechanism is: Restarted containers can have a previous log stream that is distinct from the current one.

Incorrect Answers

A:

Containers that never start may have no runtime logs; scheduling and image events carry the relevant diagnosis. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: kubectl logs --previous surfaces the original failure and event timestamps align.

C:

kubectl logs primarily reads the container runtime's captured stdout and stderr streams. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: kubectl logs --previous surfaces the original failure and event timestamps align.

D:

Container logs belong to individual containers even within one Pod. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: kubectl logs --previous surfaces the original failure and event timestamps align.

Question 455

An on-premises cluster is planned with overlapping Pod and service address blocks in the organization's existing routed networks. Following the proposed change—Choose nonoverlapping Pod and Service CIDRs and validate them against physical and VPN routes before initialization—which observation best demonstrates that the particular fault is resolved?

  1. A route review and trial Pod-to-Service connection show unique destination networks.
  2. Targeted connectivity tests reach required listeners while unrelated ports remain closed.
  3. The endpoint resolves to an active listener and kubeadm discovery succeeds from a worker.
  4. crictl can query the runtime endpoint and a test Pod starts successfully.

Explanation

Correct Answer

A:

A route review and trial Pod-to-Service connection show unique destination networks. This validates the stated intervention—choose nonoverlapping Pod and Service CIDRs and validate them against physical and VPN routes before initialization.—rather than an unrelated cluster change. The relevant mechanism is: Conflicting cluster and external address spaces can misroute traffic even when the API server is healthy.

Incorrect Answers

B:

Bootstrap and reconciliation require distinct network flows among the API server, etcd, and nodes. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A route review and trial Pod-to-Service connection show unique destination networks.

C:

Clients and join operations need a durable API endpoint independent of one control-plane host. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A route review and trial Pod-to-Service connection show unique destination networks.

D:

The kubelet delegates container creation to a CRI-compatible runtime and requires compatible host settings. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A route review and trial Pod-to-Service connection show unique destination networks.

Question 456

A filesystem volume is mounted read-only by a Pod even though the application needs to write state. Following the proposed change—Correct the Pod volumeMount readOnly setting and validate the PV and backend's supported access—which observation best demonstrates that the particular fault is resolved?

  1. Pods on different workers simultaneously read and write a shared test file where supported.
  2. After PVC deletion, the retained PV and backend volume still exist for approved recovery.
  3. The approved Pod writes a test file and unauthorized consumers remain restricted.
  4. After a Pod reschedule, the workload reads the correct data from its supported backend.

Explanation

Correct Answer

C:

The approved Pod writes a test file and unauthorized consumers remain restricted. This validates the stated intervention—correct the Pod volumeMount readOnly setting and validate the PV and backend's supported access.—rather than an unrelated cluster change. The relevant mechanism is: Mount-level read-only settings can prohibit writes regardless of a backend's broader capabilities.

Incorrect Answers

A:

Kubernetes access modes express requested attachment semantics but cannot add capability to a backend. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The approved Pod writes a test file and unauthorized consumers remain restricted.

B:

Reclaim policy determines what happens to backend storage after a bound claim is released. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The approved Pod writes a test file and unauthorized consumers remain restricted.

D:

hostPath refers to a specific node filesystem and does not provide cluster-wide data mobility. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The approved Pod writes a test file and unauthorized consumers remain restricted.

Question 457

A legacy Pod tries to contact a service outside its namespace using only a short name and accidentally reaches a local Service. An engineer recommends: Use the fully qualified service name or an explicitly namespace-qualified DNS reference. Which Kubernetes behavior best explains why this correction fits?

  1. Unqualified DNS lookups are affected by search domains in the caller's namespace.
  2. Kubernetes Service DNS gives workloads a stable logical endpoint independent of Pod replacement.
  3. Pods are replaceable and their IP addresses can change even when the application identity remains.
  4. Dual-stack Services and Pods may expose more than one IP family depending on cluster configuration.

Explanation

Correct Answer

A:

Unqualified DNS lookups are affected by search domains in the caller's namespace. This explains why the proposed action—use the fully qualified service name or an explicitly namespace-qualified DNS reference.—is appropriate. Direct confirmation is: DNS resolution returns the intended namespace's Service IP and the target responds.

Incorrect Answers

B:

Kubernetes Service DNS gives workloads a stable logical endpoint independent of Pod replacement. This does not establish the proposed intervention. The governing principle here is: Unqualified DNS lookups are affected by search domains in the caller's namespace. Apply it by: Use the fully qualified service name or an explicitly namespace-qualified DNS reference.

C:

Pods are replaceable and their IP addresses can change even when the application identity remains. This does not establish the proposed intervention. The governing principle here is: Unqualified DNS lookups are affected by search domains in the caller's namespace. Apply it by: Use the fully qualified service name or an explicitly namespace-qualified DNS reference.

D:

Dual-stack Services and Pods may expose more than one IP family depending on cluster configuration. This does not establish the proposed intervention. The governing principle here is: Unqualified DNS lookups are affected by search domains in the caller's namespace. Apply it by: Use the fully qualified service name or an explicitly namespace-qualified DNS reference.

Question 458

A production cluster relies on one control-plane VM and its failure would remove API access. What is the most direct consequence if the underlying problem is left unresolved?

  1. An infrastructure failure can remove multiple quorum voters at once.
  2. Certificate name mismatch can block administrative and node API access.
  3. Nodes may fail to join or reconnect after a control-plane replacement.
  4. A single failed VM can halt changes and prevent the control plane from reconciling.

Explanation

Correct Answer

D:

A single failed VM can halt changes and prevent the control plane from reconciling. This directly follows from the failed condition. The preventive correction is: Design and test multiple control-plane nodes behind a durable API endpoint with compatible etcd quorum. The governing Kubernetes behavior is: Highly available control planes depend on load-balanced API access and durable quorum-backed state.

Incorrect Answers

A:

Quorum and replication do not protect against a common power or hypervisor failure domain. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A single failed VM can halt changes and prevent the control plane from reconciling.

B:

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: A single failed VM can halt changes and prevent the control plane from reconciling.

C:

Clients and join operations need a durable API endpoint independent of one control-plane host. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A single failed VM can halt changes and prevent the control plane from reconciling.

Question 459

Several application replicas restart during traffic peaks with OOMKilled status but their restart count is not monitored. An engineer recommends: Inspect last termination reasons and memory working-set trends, then right-size limits and alerting. Which Kubernetes behavior best explains why this correction fits?

  1. OOMKilled is evidence of memory-limit or node memory pressure, not an ordinary successful exit.
  2. Node memory usage includes multiple consumers and cannot be attributed to one Pod without evidence.
  3. Node-wide utilization can hide a throttled or memory-constrained application container.
  4. CPU limits may cause throttling independent of overall node idle time.

Explanation

Correct Answer

A:

OOMKilled is evidence of memory-limit or node memory pressure, not an ordinary successful exit. This explains why the proposed action—inspect last termination reasons and memory working-set trends, then right-size limits and alerting.—is appropriate. Direct confirmation is: Controlled peak tests show stable replicas without OOMKilled and dashboards show reduced restarts.

Incorrect Answers

B:

Node memory usage includes multiple consumers and cannot be attributed to one Pod without evidence. This does not establish the proposed intervention. The governing principle here is: OOMKilled is evidence of memory-limit or node memory pressure, not an ordinary successful exit. Apply it by: Inspect last termination reasons and memory working-set trends, then right-size limits and alerting.

C:

Node-wide utilization can hide a throttled or memory-constrained application container. This does not establish the proposed intervention. The governing principle here is: OOMKilled is evidence of memory-limit or node memory pressure, not an ordinary successful exit. Apply it by: Inspect last termination reasons and memory working-set trends, then right-size limits and alerting.

D:

CPU limits may cause throttling independent of overall node idle time. This does not establish the proposed intervention. The governing principle here is: OOMKilled is evidence of memory-limit or node memory pressure, not an ordinary successful exit. Apply it by: Inspect last termination reasons and memory working-set trends, then right-size limits and alerting.

Question 460

An application serves traffic before its cache has warmed and early requests fail during every restart. Following the proposed change—Add a readiness probe that becomes successful only when the application can serve requests—which observation best demonstrates that the particular fault is resolved?

  1. A controlled hung-process test triggers a restart and normal traffic returns after readiness.
  2. The new Pod is excluded from ready endpoints until its cache is usable.
  3. The application survives its expected initialization duration and later liveness recovery still works.
  4. New eligible nodes automatically receive collector Pods without manual replica adjustments.

Explanation

Correct Answer

B:

The new Pod is excluded from ready endpoints until its cache is usable. This validates the stated intervention—add a readiness probe that becomes successful only when the application can serve requests.—rather than an unrelated cluster change. The relevant mechanism is: A failed readiness probe removes Pod endpoints from Services without necessarily restarting the container.

Incorrect Answers

A:

Liveness failures restart a container; readiness failures alone only affect traffic eligibility. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The new Pod is excluded from ready endpoints until its cache is usable.

C:

Startup probes suppress other probe evaluation until the startup check succeeds. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The new Pod is excluded from ready endpoints until its cache is usable.

D:

DaemonSets ensure eligible nodes run a copy of the node-level workload. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The new Pod is excluded from ready endpoints until its cache is usable.