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 23

Question 220

A training team practices kubectl rollout status and rollout undo with a purposely broken test container. What pair of supported action and practical verification should be approved?

  1. Inspect the active kubeconfig context and namespace before applying manifests to staging or production. Acceptance evidence: Run kubectl config current-context and kubectl config view --minify, then perform a read-only lookup in the expected namespace.
  2. Run automated source tests, dependency checks and artifact signing during CI, then promote the vetted immutable artifact through a controlled delivery stage. Acceptance evidence: Trace a test commit through build-test-image-digest and compare that digest between staging and production promotion records.
  3. Observe rollout progression and use a reviewed rollback to a previous ReplicaSet revision when a new application build fails health checks. Acceptance evidence: Change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.
  4. Pin validated production images by registry digest and promote the same signed artifact across environments. Acceptance evidence: Resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.

Explanation

Correct Answer

C:

The situation is that a training team practices kubectl rollout status and rollout undo with a purposely broken test container. Observe rollout progression and use a reviewed rollback to a previous ReplicaSet revision when a new application build fails health checks. Acceptance evidence: Change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests. This pairing is justified because deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings.

Incorrect Answers

A:

This action and check address the distinct objective “Manage kubectl contexts to avoid changes in the wrong cluster” instead of the stated acceptance requirement. The matching action is to observe rollout progression and use a reviewed rollback to a previous ReplicaSet revision when a new application build fails health checks. Its confirming test is to change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.

B:

The situation is that a training team practices kubectl rollout status and rollout undo with a purposely broken test container. This action and check address the distinct objective “Separate CI build verification from CD environment promotion” instead of the stated acceptance requirement. The matching action is to observe rollout progression and use a reviewed rollback to a previous ReplicaSet revision when a new application build fails health checks. Its confirming test is to change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.

D:

This action and check address the distinct objective “Use an immutable image digest for exact deployment provenance” instead of the stated acceptance requirement. The matching action is to observe rollout progression and use a reviewed rollback to a previous ReplicaSet revision when a new application build fails health checks. Its confirming test is to change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.

Question 221

A university has services named reports in three different namespaces. Which supported Kubernetes practice directly addresses the stated requirement?

  1. Resolve an object's apiVersion, kind, metadata namespace and name before applying or deleting it.
  2. Run automated source tests, dependency checks and artifact signing during CI, then promote the vetted immutable artifact through a controlled delivery stage.
  3. Record non-identifying build or audit metadata as annotations and use labels for indexing, grouping and selector-based routing.
  4. Use emptyDir for temporary sharing between containers within a Pod, and PVC-backed storage when data must survive Pod replacement.

Explanation

Correct Answer

A:

Resolve an object's apiVersion, kind, metadata namespace and name before applying or deleting it. This resolves the issue because Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds. To verify, list Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.

Incorrect Answers

B:

This option addresses the distinct objective “Separate CI build verification from CD environment promotion”, not the immediate requirement. Continuous integration validates and packages changes; continuous delivery or deployment governs how an already-built artifact reaches target environments. For the stated case, Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds.

C:

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, Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds.

D:

This option addresses the distinct objective “Understand emptyDir as Pod-lifetime shared storage, not durable application persistence”, not the immediate requirement. EmptyDir is initialized for a Pod and its contents can be shared among containers but do not survive the Pod's removal. For the stated case, Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds.

Question 222

A university has services named reports in three different namespaces. Which causal explanation supports the intended design choice?

  1. GitOps connects a versioned desired-state source with automated drift detection and reconciliation; direct manual changes may be reverted by the controller.
  2. Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds.
  3. Get returns selected object information, while describe adds human-readable state and related Events helpful for initial diagnosis.
  4. kube-proxy can maintain node networking rules for Services, but supported network implementations may replace this function.

Explanation

Correct Answer

B:

Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds. It supports this action: Resolve an object's apiVersion, kind, metadata namespace and name before applying or deleting it. To confirm, list Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.

Incorrect Answers

A:

That statement explains the distinct objective “Apply GitOps reconciliation with a version-controlled desired state” rather than the cause in this case. The deciding mechanism here is that Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds.

C:

That statement explains the distinct objective “Use kubectl get and describe for distinct inspection needs” rather than the cause in this case. The deciding mechanism here is that Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds.

D:

That statement explains the distinct objective “Understand service proxy implementations without assuming kube-proxy is mandatory” rather than the cause in this case. The deciding mechanism here is that Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds.

Question 223

A university has services named reports in three different namespaces. Which test provides the strongest evidence of a correct implementation?

  1. List Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.
  2. Run a request across two synthetic services and verify traceparent propagation and two linked spans in the configured backend.
  3. With restricted identities, check get pods succeeds while delete secrets and create clusterroles are denied.
  4. Write a synthetic temporary file into emptyDir, restart a container and then recreate the Pod to compare lifetime semantics.

Explanation

Correct Answer

A:

List Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object. This is the relevant test because Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds.

Incorrect Answers

B:

This check would help evaluate the distinct objective “Instrument services with OpenTelemetry context propagation”, but not the required result. For this case, list Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.

C:

This check would help evaluate the distinct objective “Use least-privilege kubectl authentication and authorization during routine administration”, but not the required result. For this case, list Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.

D:

This check would help evaluate the distinct objective “Understand emptyDir as Pod-lifetime shared storage, not durable application persistence”, but not the required result. For this case, list Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.

Question 224

A university has services named reports in three different namespaces. A shortcut is proposed: “Issue a generic deletion by name without specifying resource kind or namespace on a shared cluster.” Which technical consequence follows most closely?

  1. The scheduler could place multiple replicas together, leaving a node without the intended local collector.
  2. Network calls and coordination complexity grow without a business reason, creating new failure modes.
  3. An unrelated object may be targeted or the intended workload may remain untouched and unavailable.
  4. The emergency fix disappears when the Pod is replaced and cannot be reproduced reliably.

Explanation

Correct Answer

C:

An unrelated object may be targeted or the intended workload may remain untouched and unavailable. The shortcut creates this risk because Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds.

Incorrect Answers

A:

That outcome concerns the distinct objective “Select DaemonSet for node-local agents rather than Deployment replica counts”; it is not the most direct consequence of this shortcut. The relevant consequence is that an unrelated object may be targeted or the intended workload may remain untouched and unavailable.

B:

That outcome concerns the distinct objective “Contrast cloud-native microservices with a monolith without treating either as inherently superior”; it is not the most direct consequence of this shortcut. The relevant consequence is that an unrelated object may be targeted or the intended workload may remain untouched and unavailable.

D:

That outcome concerns the distinct objective “Apply resource manifests declaratively instead of depending on imperative drift”; it is not the most direct consequence of this shortcut. The relevant consequence is that an unrelated object may be targeted or the intended workload may remain untouched and unavailable.

Question 225

A university has services named reports in three different namespaces. Which combined solution and independent check are most directly justified?

  1. Grant operators only required API verbs and resources using RBAC, then test with kubectl auth can-i and separate synthetic identities. Acceptance evidence: With restricted identities, check get pods succeeds while delete secrets and create clusterroles are denied.
  2. Resolve an object's apiVersion, kind, metadata namespace and name before applying or deleting it. Acceptance evidence: List Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.
  3. Use narrowly scoped imagePullSecrets or an approved node identity to authorize the runtime to pull a private image. Acceptance evidence: Deploy a synthetic private image using an approved Secret and confirm unauthorized namespaces cannot reuse a broad registry token.
  4. Apply ingress and egress NetworkPolicy to selected Pods and verify both permitted and denied synthetic flows under a network plugin that implements policy. Acceptance evidence: Check CNI capabilities, establish a default-deny test policy and verify one allowed and one denied connection.

Explanation

Correct Answer

B:

Resolve an object's apiVersion, kind, metadata namespace and name before applying or deleting it. Acceptance evidence: List Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object. This pairing is justified because Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds.

Incorrect Answers

A:

This action and check address the distinct objective “Use least-privilege kubectl authentication and authorization during routine administration” instead of the stated acceptance requirement. The matching action is to resolve an object's apiVersion, kind, metadata namespace and name before applying or deleting it. Its confirming test is to list Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.

C:

This action and check address the distinct objective “Handle private registry pulls with dedicated credentials instead of embedding secrets in images” instead of the stated acceptance requirement. The matching action is to resolve an object's apiVersion, kind, metadata namespace and name before applying or deleting it. Its confirming test is to list Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.

D:

This action and check address the distinct objective “Recognize NetworkPolicy isolation only when the CNI enforces it” instead of the stated acceptance requirement. The matching action is to resolve an object's apiVersion, kind, metadata namespace and name before applying or deleting it. Its confirming test is to list Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.

Question 226

A small manufacturer copies a manifest but confuses a ClusterRole with a namespaced Role of the same short name. What technical action should the platform team take in this situation?

  1. Resolve an object's apiVersion, kind, metadata namespace and name before applying or deleting it.
  2. Configure readiness to stop sending Service traffic to an unready Pod, liveness to restart an unhealthy container and startup to allow slow initialization.
  3. Observe rollout progression and use a reviewed rollback to a previous ReplicaSet revision when a new application build fails health checks.
  4. Combine RBAC, Pod security policies, NetworkPolicy and resource quotas for teams that share a Kubernetes control plane.

Explanation

Correct Answer

A:

The situation is that a small manufacturer copies a manifest but confuses a ClusterRole with a namespaced Role of the same short name. Resolve an object's apiVersion, kind, metadata namespace and name before applying or deleting it. This resolves the issue because Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds. To verify, list Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.

Incorrect Answers

B:

This option addresses the distinct objective “Understand readiness, liveness and startup probes as different signals”, not the immediate requirement. Readiness affects endpoint eligibility while liveness can cause restarts; a startup probe defers other probe checks until initialization succeeds. For the stated case, Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds.

C:

This option addresses the distinct objective “Use rollout status and undo to validate and recover a Deployment release”, not the immediate requirement. Deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings. For the stated case, Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds.

D:

This option addresses the distinct objective “Separate multi-tenant namespace governance from actual isolation guarantees”, not the immediate requirement. Namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads. For the stated case, Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds.

Question 227

A small manufacturer copies a manifest but confuses a ClusterRole with a namespaced Role of the same short name. What underlying Kubernetes behavior is most relevant to this technical decision?

  1. Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds.
  2. Get returns selected object information, while describe adds human-readable state and related Events helpful for initial diagnosis.
  3. An image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage.
  4. Containers and Kubernetes APIs reduce some environment differences, but network load balancers, storage drivers and IAM integrations remain provider-specific.

Explanation

Correct Answer

A:

The situation is that a small manufacturer copies a manifest but confuses a ClusterRole with a namespaced Role of the same short name. Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds. It supports this action: Resolve an object's apiVersion, kind, metadata namespace and name before applying or deleting it. To confirm, list Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.

Incorrect Answers

B:

The situation is that a small manufacturer copies a manifest but confuses a ClusterRole with a namespaced Role of the same short name. That statement explains the distinct objective “Use kubectl get and describe for distinct inspection needs” rather than the cause in this case. The deciding mechanism here is that Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds.

C:

That statement explains the distinct objective “Distinguish a container image from a running container and its writable layer” rather than the cause in this case. The deciding mechanism here is that Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds.

D:

That statement explains the distinct objective “Apply cloud-native portability and immutable infrastructure principles pragmatically” rather than the cause in this case. The deciding mechanism here is that Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds.

Question 228

A small manufacturer copies a manifest but confuses a ClusterRole with a namespaced Role of the same short name. What acceptance check most directly confirms this requirement is met?

  1. List Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.
  2. Delete and replace a Deployment Pod and verify a client continues to reach its Service DNS name despite changed backend Pod addresses.
  3. Simulate controlled resource pressure with two priorities and inspect Events for whether a high-priority test Pod can schedule.
  4. Edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.

Explanation

Correct Answer

A:

The situation is that a small manufacturer copies a manifest but confuses a ClusterRole with a namespaced Role of the same short name. List Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object. This is the relevant test because Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds.

Incorrect Answers

B:

This check would help evaluate the distinct objective “Distinguish Pod IPs from stable Services during rescheduling”, but not the required result. For this case, list Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.

C:

This check would help evaluate the distinct objective “Use PriorityClasses and understand preemption without assuming they guarantee availability”, but not the required result. For this case, list Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.

D:

This check would help evaluate the distinct objective “Apply resource manifests declaratively instead of depending on imperative drift”, but not the required result. For this case, list Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.

Question 229

A small manufacturer copies a manifest but confuses a ClusterRole with a namespaced Role of the same short name. The team suggests: “Issue a generic deletion by name without specifying resource kind or namespace on a shared cluster.” Which failure should the reviewer anticipate?

  1. Clients may connect to an impersonated API endpoint and the token could grant excessive permissions.
  2. An unrelated object may be targeted or the intended workload may remain untouched and unavailable.
  3. Compromised credentials can perform widespread cluster changes without attribution or least privilege.
  4. The Pod might schedule on any other feasible node because tolerance is not a selection constraint.

Explanation

Correct Answer

B:

The situation is that a small manufacturer copies a manifest but confuses a ClusterRole with a namespaced Role of the same short name. An unrelated object may be targeted or the intended workload may remain untouched and unavailable. The shortcut creates this risk because Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds.

Incorrect Answers

A:

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 an unrelated object may be targeted or the intended workload may remain untouched and unavailable.

C:

That outcome concerns the distinct objective “Use least-privilege kubectl authentication and authorization during routine administration”; it is not the most direct consequence of this shortcut. The relevant consequence is that an unrelated object may be targeted or the intended workload may remain untouched and unavailable.

D:

That outcome concerns the distinct objective “Understand taints and tolerations as repulsion controls”; it is not the most direct consequence of this shortcut. The relevant consequence is that an unrelated object may be targeted or the intended workload may remain untouched and unavailable.

Question 230

A small manufacturer copies a manifest but confuses a ClusterRole with a namespaced Role of the same short name. Which engineering change and test jointly addresses the scenario?

  1. Apply appropriate ResourceQuota and LimitRange policy to bound namespace consumption and guide default container resource requests or limits. Acceptance evidence: Create a controlled test namespace with a tiny quota and verify a request exceeding aggregate limits is rejected.
  2. Configure anti-affinity against other Pods with a specific label so replicas prefer or require separate failure domains as appropriate. Acceptance evidence: Deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.
  3. Use ClusterIP for internal backends and a properly controlled NodePort or supported LoadBalancer integration for justified external access. Acceptance evidence: Create a ClusterIP test Service and validate internal access, then compare the reachable endpoints under an authorized LoadBalancer configuration.
  4. Resolve an object's apiVersion, kind, metadata namespace and name before applying or deleting it. Acceptance evidence: List Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.

Explanation

Correct Answer

D:

The situation is that a small manufacturer copies a manifest but confuses a ClusterRole with a namespaced Role of the same short name. Resolve an object's apiVersion, kind, metadata namespace and name before applying or deleting it. Acceptance evidence: List Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object. This pairing is justified because Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds.

Incorrect Answers

A:

This action and check address the distinct objective “Understand resource quotas and LimitRanges for namespace capacity governance” instead of the stated acceptance requirement. The matching action is to resolve an object's apiVersion, kind, metadata namespace and name before applying or deleting it. Its confirming test is to list Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.

B:

This action and check address the distinct objective “Use Pod anti-affinity to reduce correlated replica failure” instead of the stated acceptance requirement. The matching action is to resolve an object's apiVersion, kind, metadata namespace and name before applying or deleting it. Its confirming test is to list Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.

C:

This action and check address the distinct objective “Choose ClusterIP, NodePort and LoadBalancer Service types for appropriate reachability” instead of the stated acceptance requirement. The matching action is to resolve an object's apiVersion, kind, metadata namespace and name before applying or deleting it. Its confirming test is to list Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests