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 17

Question 160

A shipping developer reads Ready 0/1 from kubectl get and wants conditions and Events before changing the image. Which implementation together with matching acceptance evidence best meets this case?

  1. Expose appropriately labeled /metrics endpoints or exporters and configure Prometheus scrape targets to collect time-series measurements. Acceptance evidence: Verify a synthetic exporter is listed UP in Prometheus target status and query its request counter after generating traffic.
  2. Apply PriorityClasses sparingly for essential workloads and plan capacity so preemption does not unnecessarily evict useful lower-priority Pods. Acceptance evidence: Simulate controlled resource pressure with two priorities and inspect Events for whether a high-priority test Pod can schedule.
  3. Keep desired workload YAML in version control and use kubectl apply to reconcile supported object fields through the API. Acceptance evidence: Edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.
  4. Use kubectl get for concise resource lists and kubectl describe for detailed status, conditions and Events when triaging a workload. Acceptance evidence: Compare kubectl get pods -o wide with kubectl describe pod for a test image-pull failure and note which output shows recent Events.

Explanation

Correct Answer

D:

The situation is that a shipping developer reads Ready 0/1 from kubectl get and wants conditions and Events before changing the image. Use kubectl get for concise resource lists and kubectl describe for detailed status, conditions and Events when triaging a workload. Acceptance evidence: Compare kubectl get pods -o wide with kubectl describe pod for a test image-pull failure and note which output shows recent Events. This pairing is justified because get returns selected object information, while describe adds human-readable state and related Events helpful for initial diagnosis.

Incorrect Answers

A:

This action and check address the distinct objective “Understand Prometheus pull-based metrics collection and exporters” instead of the stated acceptance requirement. The matching action is to use kubectl get for concise resource lists and kubectl describe for detailed status, conditions and Events when triaging a workload. Its confirming test is to compare kubectl get pods -o wide with kubectl describe pod for a test image-pull failure and note which output shows recent Events.

B:

This action and check address the distinct objective “Use PriorityClasses and understand preemption without assuming they guarantee availability” instead of the stated acceptance requirement. The matching action is to use kubectl get for concise resource lists and kubectl describe for detailed status, conditions and Events when triaging a workload. Its confirming test is to compare kubectl get pods -o wide with kubectl describe pod for a test image-pull failure and note which output shows recent Events.

C:

This action and check address the distinct objective “Apply resource manifests declaratively instead of depending on imperative drift” instead of the stated acceptance requirement. The matching action is to use kubectl get for concise resource lists and kubectl describe for detailed status, conditions and Events when triaging a workload. Its confirming test is to compare kubectl get pods -o wide with kubectl describe pod for a test image-pull failure and note which output shows recent Events.

Question 161

A research portal updates a container image across two campus clusters with the same manifest. Which supported Kubernetes practice directly addresses the stated requirement?

  1. Record non-identifying build or audit metadata as annotations and use labels for indexing, grouping and selector-based routing.
  2. Set runAsNonRoot, suitable user IDs and drop unneeded Linux capabilities rather than assuming every container requires root.
  3. Keep desired workload YAML in version control and use kubectl apply to reconcile supported object fields through the API.
  4. Review Sandbox, Incubating and Graduated CNCF stages as community maturity signals while independently assessing a project's fitness, lifecycle and security.

Explanation

Correct Answer

C:

Keep desired workload YAML in version control and use kubectl apply to reconcile supported object fields through the API. This resolves the issue because declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management. To verify, edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.

Incorrect Answers

A:

This option addresses the distinct objective “Use annotations for tool metadata rather than workload selection”, not the immediate requirement. Labels are designed for selectors and filtering, whereas annotations hold descriptive metadata not intended as a resource-matching control. For the stated case, declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.

B:

This option addresses the distinct objective “Run images with least-privilege runtime security contexts”, not the immediate requirement. SecurityContext configures process identity and privilege boundaries, and unnecessary root privileges increase impact if an application is compromised. For the stated case, declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.

D:

This option addresses the distinct objective “Understand CNCF project maturity stages without equating them to security approval”, not the immediate requirement. CNCF maturity describes aspects of adoption and governance, not a blanket guarantee that every deployment or version is free of defects. For the stated case, declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.

Question 162

A research portal updates a container image across two campus clusters with the same manifest. Which causal explanation supports the intended design choice?

  1. A Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.
  2. Declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.
  3. A supported runtime such as containerd executes container operations requested through kubelet using the Container Runtime Interface.
  4. The spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.

Explanation

Correct Answer

B:

Declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management. It supports this action: Keep desired workload YAML in version control and use kubectl apply to reconcile supported object fields through the API. To confirm, edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.

Incorrect Answers

A:

That statement explains the distinct objective “Distinguish a failed Service selector from broken DNS or a failing backend” rather than the cause in this case. The deciding mechanism here is that declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.

C:

That statement explains the distinct objective “Explain the container runtime interface without conflating it with the control plane” rather than the cause in this case. The deciding mechanism here is that declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.

D:

That statement explains the distinct objective “Interpret Kubernetes spec and status fields without confusing intent with condition” rather than the cause in this case. The deciding mechanism here is that declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.

Question 163

A research portal updates a container image across two campus clusters with the same manifest. Which test provides the strongest evidence of a correct implementation?

  1. Change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.
  2. Edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.
  3. Test the same Service from a diagnostic Pod by fully qualified DNS name and known ClusterIP, then inspect CoreDNS logs if only resolution fails.
  4. Delay a synthetic app response and compare EndpointSlice readiness with restart counts under controlled probe settings.

Explanation

Correct Answer

B:

Edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change. This is the relevant test because declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.

Incorrect Answers

A:

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, edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.

C:

This check would help evaluate the distinct objective “Diagnose cluster DNS separately from Pod network reachability”, but not the required result. For this case, edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.

D:

This check would help evaluate the distinct objective “Understand readiness, liveness and startup probes as different signals”, but not the required result. For this case, edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.

Question 164

A research portal updates a container image across two campus clusters with the same manifest. A shortcut is proposed: “Install a package manually inside a running Pod and treat that mutable container filesystem as the durable release artifact.” Which technical consequence follows most closely?

  1. A control-plane restore might recover resource metadata while losing application records that were never backed up.
  2. The emergency fix disappears when the Pod is replaced and cannot be reproduced reliably.
  3. Clients may connect to an impersonated API endpoint and the token could grant excessive permissions.
  4. Users may encounter failed requests because readiness and application-level health remain unverified.

Explanation

Correct Answer

B:

The emergency fix disappears when the Pod is replaced and cannot be reproduced reliably. The shortcut creates this risk because declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.

Incorrect Answers

A:

That outcome concerns the distinct objective “Distinguish etcd persistence from running workload data”; it is not the most direct consequence of this shortcut. The relevant consequence is that the emergency fix disappears when the Pod is replaced and cannot be reproduced reliably.

C:

That outcome concerns the distinct objective “Protect API server access using authenticated TLS clients and audited authorization”; it is not the most direct consequence of this shortcut. The relevant consequence is that the emergency fix disappears when the Pod is replaced and cannot be reproduced reliably.

D:

That outcome concerns the distinct objective “Use kubectl get and describe for distinct inspection needs”; it is not the most direct consequence of this shortcut. The relevant consequence is that the emergency fix disappears when the Pod is replaced and cannot be reproduced reliably.

Question 165

A research portal updates a container image across two campus clusters with the same manifest. Which combined solution and independent check are most directly justified?

  1. Use metrics for measurable trends, logs for event detail and distributed traces for individual transaction paths while sharing correlation identifiers. Acceptance evidence: Send a synthetic request with a correlation ID and confirm it appears in the trace and relevant logs while latency metrics change.
  2. Keep desired workload YAML in version control and use kubectl apply to reconcile supported object fields through the API. Acceptance evidence: Edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.
  3. Read a workload's spec and status separately and inspect conditions when determining whether an API change became healthy. Acceptance evidence: Apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.
  4. Inspect kubelet-reported Pod and container conditions when a scheduled workload fails to start, while keeping cluster resources managed through the API. Acceptance evidence: Describe a scheduled Pod with ImagePullBackOff and compare its assigned node against kubelet-related Events.

Explanation

Correct Answer

B:

Keep desired workload YAML in version control and use kubectl apply to reconcile supported object fields through the API. Acceptance evidence: Edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change. This pairing is justified because declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.

Incorrect Answers

A:

This action and check address the distinct objective “Explain metrics, logs and traces as complementary observability signals” instead of the stated acceptance requirement. The matching action is to keep desired workload YAML in version control and use kubectl apply to reconcile supported object fields through the API. Its confirming test is to edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.

C:

This action and check address the distinct objective “Interpret Kubernetes spec and status fields without confusing intent with condition” instead of the stated acceptance requirement. The matching action is to keep desired workload YAML in version control and use kubectl apply to reconcile supported object fields through the API. Its confirming test is to edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.

D:

This action and check address the distinct objective “Recognize the kubelet role in local Pod lifecycle management” instead of the stated acceptance requirement. The matching action is to keep desired workload YAML in version control and use kubectl apply to reconcile supported object fields through the API. Its confirming test is to edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.

Question 166

A hotel service team keeps modifying a live Pod shell instead of changing its Deployment definition. What technical action should the platform team take in this situation?

  1. Record non-identifying build or audit metadata as annotations and use labels for indexing, grouping and selector-based routing.
  2. Use kubectl get for concise resource lists and kubectl describe for detailed status, conditions and Events when triaging a workload.
  3. Match a Service's exposed port and targetPort to the actual listening application container, checking protocol and named ports when used.
  4. Keep desired workload YAML in version control and use kubectl apply to reconcile supported object fields through the API.

Explanation

Correct Answer

D:

The situation is that a hotel service team keeps modifying a live Pod shell instead of changing its Deployment definition. Keep desired workload YAML in version control and use kubectl apply to reconcile supported object fields through the API. This resolves the issue because declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management. To verify, edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.

Incorrect Answers

A:

The situation is that a hotel service team keeps modifying a live Pod shell instead of changing its Deployment definition. This option addresses the distinct objective “Use annotations for tool metadata rather than workload selection”, not the immediate requirement. Labels are designed for selectors and filtering, whereas annotations hold descriptive metadata not intended as a resource-matching control. For the stated case, declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.

B:

This option addresses the distinct objective “Use kubectl get and describe for distinct inspection needs”, not the immediate requirement. Get returns selected object information, while describe adds human-readable state and related Events helpful for initial diagnosis. For the stated case, declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.

C:

This option addresses the distinct objective “Understand ports, targetPort and protocol mapping in a Service”, not the immediate requirement. A Service exposes port to clients and forwards to targetPort on selected endpoints; a mismatched targetPort can break delivery even with valid DNS and selectors. For the stated case, declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.

Question 167

A hotel service team keeps modifying a live Pod shell instead of changing its Deployment definition. What underlying Kubernetes behavior is most relevant to this technical decision?

  1. Authentication establishes who calls the API; RBAC authorization checks requested verb, resource and namespace before the API permits it.
  2. Cordon marks a node unschedulable for new ordinary Pods; drain evicts managed workloads when policies and availability permit.
  3. Declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.
  4. CSI separates storage vendor implementation from Kubernetes core and manages provisioning, attachment and node mounting through driver-defined capabilities.

Explanation

Correct Answer

C:

The situation is that a hotel service team keeps modifying a live Pod shell instead of changing its Deployment definition. Declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management. It supports this action: Keep desired workload YAML in version control and use kubectl apply to reconcile supported object fields through the API. To confirm, edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.

Incorrect Answers

A:

That statement explains the distinct objective “Use least-privilege kubectl authentication and authorization during routine administration” rather than the cause in this case. The deciding mechanism here is that declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.

B:

That statement explains the distinct objective “Use cordon and drain with disruption considerations for planned node maintenance” rather than the cause in this case. The deciding mechanism here is that declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.

D:

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 declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.

Question 168

A hotel service team keeps modifying a live Pod shell instead of changing its Deployment definition. What acceptance check most directly confirms this requirement is met?

  1. Apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.
  2. Simulate an unavailable lab worker, inspect Ready condition and Pod Events, then confirm managed workloads are rescheduled where feasible.
  3. Edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.
  4. Deploy a test sidecar and main container, verify localhost communication and compare their shared Pod IP with a separate Pod.

Explanation

Correct Answer

C:

The situation is that a hotel service team keeps modifying a live Pod shell instead of changing its Deployment definition. Edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change. This is the relevant test because declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Interpret Kubernetes spec and status fields without confusing intent with condition”, but not the required result. For this case, edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.

B:

This check would help evaluate the distinct objective “Use node conditions and allocatable capacity to diagnose NotReady workloads”, but not the required result. For this case, edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.

D:

This check would help evaluate the distinct objective “Use Pods as the shared network and storage execution unit”, but not the required result. For this case, edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.

Question 169

A hotel service team keeps modifying a live Pod shell instead of changing its Deployment definition. The team suggests: “Install a package manually inside a running Pod and treat that mutable container filesystem as the durable release artifact.” Which failure should the reviewer anticipate?

  1. An application regression can remain live even though container and readiness probes are healthy.
  2. Secrets can be exposed to broadly authorized readers and source-control users despite apparently valid deployments.
  3. The emergency fix disappears when the Pod is replaced and cannot be reproduced reliably.
  4. Credential reuse could expose all namespaces and persist after the original developer loses access.

Explanation

Correct Answer

C:

The situation is that a hotel service team keeps modifying a live Pod shell instead of changing its Deployment definition. The emergency fix disappears when the Pod is replaced and cannot be reproduced reliably. The shortcut creates this risk because declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.

Incorrect Answers

A:

That outcome concerns the distinct objective “Correlate application rollout revisions with error spikes”; it is not the most direct consequence of this shortcut. The relevant consequence is that the emergency fix disappears when the Pod is replaced and cannot be reproduced reliably.

B:

That outcome concerns the distinct objective “Distinguish ConfigMaps from Secrets and avoid storing credentials in public configuration”; it is not the most direct consequence of this shortcut. The relevant consequence is that the emergency fix disappears when the Pod is replaced and cannot be reproduced reliably.

D:

That outcome concerns the distinct objective “Differentiate ServiceAccounts from human kubeconfig identities”; it is not the most direct consequence of this shortcut. The relevant consequence is that the emergency fix disappears when the Pod is replaced and cannot be reproduced reliably.

Question 170

A hotel service team keeps modifying a live Pod shell instead of changing its Deployment definition. Which engineering change and test jointly addresses the scenario?

  1. Store approved declarative cluster manifests in Git and let a GitOps controller reconcile differences while keeping sensitive access appropriately scoped. Acceptance evidence: Change a test Deployment field outside Git, observe drift and confirm reconciliation restores the reviewed Git value.
  2. Label eligible nodes for a test hardware property and use nodeSelector when a Pod must run only on matching nodes. Acceptance evidence: Label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.
  3. Keep desired workload YAML in version control and use kubectl apply to reconcile supported object fields through the API. Acceptance evidence: Edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.
  4. Put non-sensitive application settings in ConfigMaps and put credentials in Secret objects with RBAC, encryption and external secret-management safeguards where appropriate. Acceptance evidence: Inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.

Explanation

Correct Answer

C:

The situation is that a hotel service team keeps modifying a live Pod shell instead of changing its Deployment definition. Keep desired workload YAML in version control and use kubectl apply to reconcile supported object fields through the API. Acceptance evidence: Edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change. This pairing is justified because declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.

Incorrect Answers

A:

This action and check address the distinct objective “Apply GitOps reconciliation with a version-controlled desired state” instead of the stated acceptance requirement. The matching action is to keep desired workload YAML in version control and use kubectl apply to reconcile supported object fields through the API. Its confirming test is to edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.

B:

This action and check address the distinct objective “Use nodeSelector to place a workload on nodes with required labels” instead of the stated acceptance requirement. The matching action is to keep desired workload YAML in version control and use kubectl apply to reconcile supported object fields through the API. Its confirming test is to edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.

D:

This action and check address the distinct objective “Distinguish ConfigMaps from Secrets and avoid storing credentials in public configuration” instead of the stated acceptance requirement. The matching action is to keep desired workload YAML in version control and use kubectl apply to reconcile supported object fields through the API. Its confirming test is to edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests