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 24

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.

Question 231

A local council gives interns read access to staging Pods but no ability to change production roles. Which supported Kubernetes practice directly addresses the stated requirement?

  1. Grant operators only required API verbs and resources using RBAC, then test with kubectl auth can-i and separate synthetic identities.
  2. Require approved image registries, signature or digest verification and patch ownership when admitting production container images.
  3. Observe rollout progression and use a reviewed rollback to a previous ReplicaSet revision when a new application build fails health checks.
  4. Resolve an object's apiVersion, kind, metadata namespace and name before applying or deleting it.

Explanation

Correct Answer

A:

Grant operators only required API verbs and resources using RBAC, then test with kubectl auth can-i and separate synthetic identities. This resolves the issue because authentication establishes who calls the API; RBAC authorization checks requested verb, resource and namespace before the API permits it. To verify, with restricted identities, check get pods succeeds while delete secrets and create clusterroles are denied.

Incorrect Answers

B:

This option addresses the distinct objective “Use image provenance and policy controls without trusting mutable tags”, not the immediate requirement. Image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity. For the stated case, authentication establishes who calls the API; RBAC authorization checks requested verb, resource and namespace before the API permits it.

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, authentication establishes who calls the API; RBAC authorization checks requested verb, resource and namespace before the API permits it.

D:

This option addresses the distinct objective “Read the API resource model using namespaces and names rather than guessing ownership”, not the immediate requirement. Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds. For the stated case, authentication establishes who calls the API; RBAC authorization checks requested verb, resource and namespace before the API permits it.

Question 232

A local council gives interns read access to staging Pods but no ability to change production roles. Which causal explanation supports the intended design choice?

  1. Pod Security Standards establish common workload hardening profiles, and admission checks can enforce restricted capabilities and privilege use at API creation.
  2. A quota constrains aggregate namespace resource usage, while a LimitRange validates or defaults eligible individual resource settings.
  3. Authentication establishes who calls the API; RBAC authorization checks requested verb, resource and namespace before the API permits it.
  4. The API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.

Explanation

Correct Answer

C:

Authentication establishes who calls the API; RBAC authorization checks requested verb, resource and namespace before the API permits it. It supports this action: Grant operators only required API verbs and resources using RBAC, then test with kubectl auth can-i and separate synthetic identities. To confirm, with restricted identities, check get pods succeeds while delete secrets and create clusterroles are denied.

Incorrect Answers

A:

That statement explains the distinct objective “Use Pod Security Standards to deny overly privileged Pod configurations” rather than the cause in this case. The deciding mechanism here is that authentication establishes who calls the API; RBAC authorization checks requested verb, resource and namespace before the API permits it.

B:

That statement explains the distinct objective “Understand resource quotas and LimitRanges for namespace capacity governance” rather than the cause in this case. The deciding mechanism here is that authentication establishes who calls the API; RBAC authorization checks requested verb, resource and namespace before the API permits it.

D:

That statement explains the distinct objective “Explain desired state versus observed status in Kubernetes objects” rather than the cause in this case. The deciding mechanism here is that authentication establishes who calls the API; RBAC authorization checks requested verb, resource and namespace before the API permits it.

Question 233

A local council gives interns read access to staging Pods but no ability to change production roles. Which test provides the strongest evidence of a correct implementation?

  1. With restricted identities, check get pods succeeds while delete secrets and create clusterroles are denied.
  2. Run kubectl kustomize for development and production overlays and compare the resulting YAML objects before application.
  3. Inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.
  4. 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

A:

With restricted identities, check get pods succeeds while delete secrets and create clusterroles are denied. This is the relevant test because authentication establishes who calls the API; RBAC authorization checks requested verb, resource and namespace before the API permits it.

Incorrect Answers

B:

This check would help evaluate the distinct objective “Use Kustomize overlays to adapt manifests without copying whole deployments”, but not the required result. For this case, with restricted identities, check get pods succeeds while delete secrets and create clusterroles are denied.

C:

This check would help evaluate the distinct objective “Distinguish ConfigMaps from Secrets and avoid storing credentials in public configuration”, but not the required result. For this case, with restricted identities, check get pods succeeds while delete secrets and create clusterroles are denied.

D:

This check would help evaluate the distinct objective “Use kubectl get and describe for distinct inspection needs”, but not the required result. For this case, with restricted identities, check get pods succeeds while delete secrets and create clusterroles are denied.

Question 234

A local council gives interns read access to staging Pods but no ability to change production roles. A shortcut is proposed: “Share one permanent cluster-admin user token with every technician and rely on good intentions as the access boundary.” Which technical consequence follows most closely?

  1. External routing remains absent or policy is misunderstood, and internal identity controls may be incomplete.
  2. Compromised credentials can perform widespread cluster changes without attribution or least privilege.
  3. Credential reuse could expose all namespaces and persist after the original developer loses access.
  4. The command can mutate production objects although the operator intended a disposable laboratory cluster.

Explanation

Correct Answer

B:

Compromised credentials can perform widespread cluster changes without attribution or least privilege. The shortcut creates this risk because authentication establishes who calls the API; RBAC authorization checks requested verb, resource and namespace before the API permits it.

Incorrect Answers

A:

That outcome concerns the distinct objective “Distinguish service mesh traffic management from external ingress routing”; it is not the most direct consequence of this shortcut. The relevant consequence is that compromised credentials can perform widespread cluster changes without attribution or least privilege.

C:

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 compromised credentials can perform widespread cluster changes without attribution or least privilege.

D:

That outcome concerns the distinct objective “Manage kubectl contexts to avoid changes in the wrong cluster”; it is not the most direct consequence of this shortcut. The relevant consequence is that compromised credentials can perform widespread cluster changes without attribution or least privilege.

Question 235

A local council gives interns read access to staging Pods but no ability to change production roles. 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. 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.
  3. Change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation. Acceptance evidence: Set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.
  4. Create a Role with only required verbs and resource types, and bind it to the intended subject within the target namespace. Acceptance evidence: Use kubectl auth can-i --as a synthetic student to verify pod get allowed and secret delete denied in the specified namespace.

Explanation

Correct Answer

A:

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. This pairing is justified because authentication establishes who calls the API; RBAC authorization checks requested verb, resource and namespace before the API permits it.

Incorrect Answers

B:

This action and check address the distinct objective “Use rollout status and undo to validate and recover a Deployment release” instead of the stated acceptance requirement. The matching action is to grant operators only required API verbs and resources using RBAC, then test with kubectl auth can-i and separate synthetic identities. Its confirming test is to with restricted identities, check get pods succeeds while delete secrets and create clusterroles are denied.

C:

This action and check address the distinct objective “Explain desired state versus observed status in Kubernetes objects” instead of the stated acceptance requirement. The matching action is to grant operators only required API verbs and resources using RBAC, then test with kubectl auth can-i and separate synthetic identities. Its confirming test is to with restricted identities, check get pods succeeds while delete secrets and create clusterroles are denied.

D:

This action and check address the distinct objective “Implement namespaced RBAC Roles for least-privilege resource permissions” instead of the stated acceptance requirement. The matching action is to grant operators only required API verbs and resources using RBAC, then test with kubectl auth can-i and separate synthetic identities. Its confirming test is to with restricted identities, check get pods succeeds while delete secrets and create clusterroles are denied.

Question 236

A financial cooperative's on-call staff must inspect Events without modifying cluster-wide security settings. Which Kubernetes or cloud-native implementation decision best solves the stated problem?

  1. Put non-sensitive application settings in ConfigMaps and put credentials in Secret objects with RBAC, encryption and external secret-management safeguards where appropriate.
  2. Use a supported service mesh when fine-grained internal service-to-service security and telemetry are needed, while separately configuring north-south ingress or gateway exposure.
  3. Grant operators only required API verbs and resources using RBAC, then test with kubectl auth can-i and separate synthetic identities.
  4. Group tightly coupled containers that require the same Pod networking identity and optionally shared volumes into one Pod while keeping independently scalable services separate.

Explanation

Correct Answer

C:

The situation is that a financial cooperative's on-call staff must inspect Events without modifying cluster-wide security settings. Grant operators only required API verbs and resources using RBAC, then test with kubectl auth can-i and separate synthetic identities. This resolves the issue because authentication establishes who calls the API; RBAC authorization checks requested verb, resource and namespace before the API permits it. To verify, with restricted identities, check get pods succeeds while delete secrets and create clusterroles are denied.

Incorrect Answers

A:

This option addresses the distinct objective “Distinguish ConfigMaps from Secrets and avoid storing credentials in public configuration”, not the immediate requirement. ConfigMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy. For the stated case, authentication establishes who calls the API; RBAC authorization checks requested verb, resource and namespace before the API permits it.

B:

This option addresses the distinct objective “Distinguish service mesh traffic management from external ingress routing”, not the immediate requirement. Service meshes commonly use proxies or ambient dataplanes to control east-west traffic; ingress/gateway handling addresses entry routes and can integrate with the mesh. For the stated case, authentication establishes who calls the API; RBAC authorization checks requested verb, resource and namespace before the API permits it.

D:

This option addresses the distinct objective “Use Pods as the shared network and storage execution unit”, not the immediate requirement. Containers in a Pod share a network namespace and IP address and can coordinate on localhost, while the Pod is scheduled as one unit. For the stated case, authentication establishes who calls the API; RBAC authorization checks requested verb, resource and namespace before the API permits it.

Question 237

A financial cooperative's on-call staff must inspect Events without modifying cluster-wide security settings. Which platform mechanism explains why the suitable approach works?

  1. FailedScheduling occurs before node binding; ImagePullBackOff occurs when a node's kubelet cannot obtain the container image.
  2. The spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.
  3. Cordon marks a node unschedulable for new ordinary Pods; drain evicts managed workloads when policies and availability permit.
  4. Authentication establishes who calls the API; RBAC authorization checks requested verb, resource and namespace before the API permits it.

Explanation

Correct Answer

D:

The situation is that a financial cooperative's on-call staff must inspect Events without modifying cluster-wide security settings. Authentication establishes who calls the API; RBAC authorization checks requested verb, resource and namespace before the API permits it. It supports this action: Grant operators only required API verbs and resources using RBAC, then test with kubectl auth can-i and separate synthetic identities. To confirm, with restricted identities, check get pods succeeds while delete secrets and create clusterroles are denied.

Incorrect Answers

A:

That statement explains the distinct objective “Separate Pending scheduling failures from ImagePullBackOff errors” rather than the cause in this case. The deciding mechanism here is that authentication establishes who calls the API; RBAC authorization checks requested verb, resource and namespace before the API permits it.

B:

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 authentication establishes who calls the API; RBAC authorization checks requested verb, resource and namespace before the API permits it.

C:

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 authentication establishes who calls the API; RBAC authorization checks requested verb, resource and namespace before the API permits it.

Question 238

A financial cooperative's on-call staff must inspect Events without modifying cluster-wide security settings. Which controlled observation would best validate the intended improvement?

  1. Add a test worker node and inspect the corresponding DaemonSet agent Pod without scaling a Deployment.
  2. With restricted identities, check get pods succeeds while delete secrets and create clusterroles are denied.
  3. Create synthetic invalid quota, unschedulable node and missing-image cases and compare their event reasons and assigned node status.
  4. 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

B:

The situation is that a financial cooperative's on-call staff must inspect Events without modifying cluster-wide security settings. With restricted identities, check get pods succeeds while delete secrets and create clusterroles are denied. This is the relevant test because authentication establishes who calls the API; RBAC authorization checks requested verb, resource and namespace before the API permits it.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Select DaemonSet for node-local agents rather than Deployment replica counts”, but not the required result. For this case, with restricted identities, check get pods succeeds while delete secrets and create clusterroles are denied.

C:

This check would help evaluate the distinct objective “Use describe and Events to distinguish admission, scheduling and execution errors”, but not the required result. For this case, with restricted identities, check get pods succeeds while delete secrets and create clusterroles are denied.

D:

The situation is that a financial cooperative's on-call staff must inspect Events without modifying cluster-wide security settings. This check would help evaluate the distinct objective “Use kubectl get and describe for distinct inspection needs”, but not the required result. For this case, with restricted identities, check get pods succeeds while delete secrets and create clusterroles are denied.

Question 239

A financial cooperative's on-call staff must inspect Events without modifying cluster-wide security settings. An engineer proposes: “Share one permanent cluster-admin user token with every technician and rely on good intentions as the access boundary.” What adverse outcome would be most direct?

  1. PersistentVolumeClaims remain Pending or Pods fail to mount because the required driver integration is missing.
  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. Secrets can be exposed to broadly authorized readers and source-control users despite apparently valid deployments.

Explanation

Correct Answer

C:

The situation is that a financial cooperative's on-call staff must inspect Events without modifying cluster-wide security settings. Compromised credentials can perform widespread cluster changes without attribution or least privilege. The shortcut creates this risk because authentication establishes who calls the API; RBAC authorization checks requested verb, resource and namespace before the API permits it.

Incorrect Answers

A:

That outcome concerns the distinct objective “Understand CSI drivers and volume attachment responsibilities”; it is not the most direct consequence of this shortcut. The relevant consequence is that compromised credentials can perform widespread cluster changes without attribution or least privilege.

B:

That outcome concerns the distinct objective “Read the API resource model using namespaces and names rather than guessing ownership”; it is not the most direct consequence of this shortcut. The relevant consequence is that compromised credentials can perform widespread cluster changes without attribution or least privilege.

D:

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 compromised credentials can perform widespread cluster changes without attribution or least privilege.

Question 240

A financial cooperative's on-call staff must inspect Events without modifying cluster-wide security settings. What pair of supported action and practical verification should be approved?

  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. 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.
  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. 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.

Explanation

Correct Answer

A:

The situation is that a financial cooperative's on-call staff must inspect Events without modifying cluster-wide security settings. 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. This pairing is justified because authentication establishes who calls the API; RBAC authorization checks requested verb, resource and namespace before the API permits it.

Incorrect Answers

B:

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 grant operators only required API verbs and resources using RBAC, then test with kubectl auth can-i and separate synthetic identities. Its confirming test is to with restricted identities, check get pods succeeds while delete secrets and create clusterroles are denied.

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 grant operators only required API verbs and resources using RBAC, then test with kubectl auth can-i and separate synthetic identities. Its confirming test is to with restricted identities, check get pods succeeds while delete secrets and create clusterroles are denied.

D:

The situation is that a financial cooperative's on-call staff must inspect Events without modifying cluster-wide security settings. This action and check address the distinct objective “Use rollout status and undo to validate and recover a Deployment release” instead of the stated acceptance requirement. The matching action is to grant operators only required API verbs and resources using RBAC, then test with kubectl auth can-i and separate synthetic identities. Its confirming test is to with restricted identities, check get pods succeeds while delete secrets and create clusterroles are denied.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests