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 20

Question 190

A university dashboard wants to find all application Pods by team while retaining long-form audit notes. Which engineering change and test jointly addresses the scenario?

  1. 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.
  2. Define post-release checks for readiness, error rate and latency, and revert an unhealthy revision using an approved rollout mechanism. Acceptance evidence: Deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.
  3. Record non-identifying build or audit metadata as annotations and use labels for indexing, grouping and selector-based routing. Acceptance evidence: Annotate a Deployment with release notes and verify its Service still selects Pods using explicit app labels.
  4. 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.

Explanation

Correct Answer

C:

The situation is that a university dashboard wants to find all application Pods by team while retaining long-form audit notes. Record non-identifying build or audit metadata as annotations and use labels for indexing, grouping and selector-based routing. Acceptance evidence: Annotate a Deployment with release notes and verify its Service still selects Pods using explicit app labels. This pairing is justified because labels are designed for selectors and filtering, whereas annotations hold descriptive metadata not intended as a resource-matching control.

Incorrect Answers

A:

This action and check address the distinct objective “Use kubectl get and describe for distinct inspection needs” instead of the stated acceptance requirement. The matching action is to record non-identifying build or audit metadata as annotations and use labels for indexing, grouping and selector-based routing. Its confirming test is to annotate a Deployment with release notes and verify its Service still selects Pods using explicit app labels.

B:

This action and check address the distinct objective “Design a release rollback trigger from measurable service signals” instead of the stated acceptance requirement. The matching action is to record non-identifying build or audit metadata as annotations and use labels for indexing, grouping and selector-based routing. Its confirming test is to annotate a Deployment with release notes and verify its Service still selects Pods using explicit app labels.

D:

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 record non-identifying build or audit metadata as annotations and use labels for indexing, grouping and selector-based routing. Its confirming test is to annotate a Deployment with release notes and verify its Service still selects Pods using explicit app labels.

Question 191

A school analytics app needs a harmless report interval and a private database credential. Which Kubernetes or cloud-native implementation decision best solves the stated problem?

  1. Build an OCI-compatible image with immutable packaged artifacts and treat running container writable state as ephemeral.
  2. Observe rollout progression and use a reviewed rollback to a previous ReplicaSet revision when a new application build fails health checks.
  3. Put non-sensitive application settings in ConfigMaps and put credentials in Secret objects with RBAC, encryption and external secret-management safeguards where appropriate.
  4. Apply suitable Pod Security Admission labels such as baseline or restricted and test whether noncompliant synthetic Pod specs are rejected.

Explanation

Correct Answer

C:

Put non-sensitive application settings in ConfigMaps and put credentials in Secret objects with RBAC, encryption and external secret-management safeguards where appropriate. This resolves the issue because configMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy. To verify, inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.

Incorrect Answers

A:

This option addresses the distinct objective “Distinguish a container image from a running container and its writable layer”, not the immediate requirement. An image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage. For the stated case, configMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.

B:

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, configMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.

D:

This option addresses the distinct objective “Use Pod Security Standards to deny overly privileged Pod configurations”, not the immediate requirement. Pod Security Standards establish common workload hardening profiles, and admission checks can enforce restricted capabilities and privilege use at API creation. For the stated case, configMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.

Question 192

A school analytics app needs a harmless report interval and a private database credential. Which platform mechanism explains why the suitable approach works?

  1. ConfigMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.
  2. kube-proxy can maintain node networking rules for Services, but supported network implementations may replace this function.
  3. The spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.
  4. FailedScheduling occurs before node binding; ImagePullBackOff occurs when a node's kubelet cannot obtain the container image.

Explanation

Correct Answer

A:

ConfigMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy. It supports this action: Put non-sensitive application settings in ConfigMaps and put credentials in Secret objects with RBAC, encryption and external secret-management safeguards where appropriate. To confirm, inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.

Incorrect Answers

B:

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 configMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.

C:

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 configMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.

D:

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 configMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.

Question 193

A school analytics app needs a harmless report interval and a private database credential. Which controlled observation would best validate the intended improvement?

  1. Apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.
  2. Insert a deliberately unsigned test image into staging and confirm the release gate blocks production promotion while logging a reason.
  3. Inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.
  4. Run kubectl config current-context and kubectl config view --minify, then perform a read-only lookup in the expected namespace.

Explanation

Correct Answer

C:

Inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret. This is the relevant test because configMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.

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, inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.

B:

This check would help evaluate the distinct objective “Define secure release governance with staged approvals and policy verification”, but not the required result. For this case, inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.

D:

This check would help evaluate the distinct objective “Manage kubectl contexts to avoid changes in the wrong cluster”, but not the required result. For this case, inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.

Question 194

A school analytics app needs a harmless report interval and a private database credential. An engineer proposes: “Embed production passwords in a ConfigMap because its YAML is easier to inspect and store in a public repository.” What adverse outcome would be most direct?

  1. Unexpected data loss or orphaned sensitive volumes can result from misunderstanding reclaim and retention policies.
  2. More replicas fail the same way because the process configuration, not desired replica count, caused the exit.
  3. The emergency fix disappears when the Pod is replaced and cannot be reproduced reliably.
  4. Secrets can be exposed to broadly authorized readers and source-control users despite apparently valid deployments.

Explanation

Correct Answer

D:

Secrets can be exposed to broadly authorized readers and source-control users despite apparently valid deployments. The shortcut creates this risk because configMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.

Incorrect Answers

A:

That outcome concerns the distinct objective “Compare PV reclaim policies and explain data retention on PVC deletion”; it is not the most direct consequence of this shortcut. The relevant consequence is that secrets can be exposed to broadly authorized readers and source-control users despite apparently valid deployments.

B:

That outcome concerns the distinct objective “Understand ENTRYPOINT and command overrides when a container exits immediately”; it is not the most direct consequence of this shortcut. The relevant consequence is that secrets can be exposed to broadly authorized readers and source-control users despite apparently valid deployments.

C:

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 secrets can be exposed to broadly authorized readers and source-control users despite apparently valid deployments.

Question 195

A school analytics app needs a harmless report interval and a private database credential. What pair of supported action and practical verification should be approved?

  1. Build an OCI-compatible image with immutable packaged artifacts and treat running container writable state as ephemeral. Acceptance evidence: Build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.
  2. 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.
  3. Record non-identifying build or audit metadata as annotations and use labels for indexing, grouping and selector-based routing. Acceptance evidence: Annotate a Deployment with release notes and verify its Service still selects Pods using explicit app labels.
  4. Keep a common base and targeted Kustomize overlays for namespace, image or replica differences across environments. Acceptance evidence: Run kubectl kustomize for development and production overlays and compare the resulting YAML objects before application.

Explanation

Correct Answer

B:

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. This pairing is justified because configMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.

Incorrect Answers

A:

This action and check address the distinct objective “Distinguish a container image from a running container and its writable layer” instead of the stated acceptance requirement. The matching action is to put non-sensitive application settings in ConfigMaps and put credentials in Secret objects with RBAC, encryption and external secret-management safeguards where appropriate. Its confirming test is to inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.

C:

This action and check address the distinct objective “Use annotations for tool metadata rather than workload selection” instead of the stated acceptance requirement. The matching action is to put non-sensitive application settings in ConfigMaps and put credentials in Secret objects with RBAC, encryption and external secret-management safeguards where appropriate. Its confirming test is to inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.

D:

This action and check address the distinct objective “Use Kustomize overlays to adapt manifests without copying whole deployments” instead of the stated acceptance requirement. The matching action is to put non-sensitive application settings in ConfigMaps and put credentials in Secret objects with RBAC, encryption and external secret-management safeguards where appropriate. Its confirming test is to inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.

Question 196

A cooperative's workload uses API tokens and administrators propose putting them into a shared configuration map. Which Kubernetes or cloud-native implementation decision best solves the stated problem?

  1. Define appropriate HTTP routing through an installed Ingress controller or Gateway API controller rather than expecting the API object alone to provision a proxy.
  2. Inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count.
  3. Resolve an object's apiVersion, kind, metadata namespace and name before applying or deleting it.
  4. Put non-sensitive application settings in ConfigMaps and put credentials in Secret objects with RBAC, encryption and external secret-management safeguards where appropriate.

Explanation

Correct Answer

D:

The situation is that a cooperative's workload uses API tokens and administrators propose putting them into a shared configuration map. Put non-sensitive application settings in ConfigMaps and put credentials in Secret objects with RBAC, encryption and external secret-management safeguards where appropriate. This resolves the issue because configMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy. To verify, inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.

Incorrect Answers

A:

This option addresses the distinct objective “Choose Ingress or Gateway API with an implementing controller for HTTP exposure”, not the immediate requirement. Ingress and Gateway API express routing intent, while an actual controller/dataplane implements TLS termination, listeners and backend forwarding. For the stated case, configMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.

B:

This option addresses the distinct objective “Interpret ReplicaSet ownership and selectors in a Deployment”, not the immediate requirement. A Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts. For the stated case, configMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.

C:

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, configMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.

Question 197

A cooperative's workload uses API tokens and administrators propose putting them into a shared configuration map. Which platform mechanism explains why the suitable approach works?

  1. The spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.
  2. Ingress and Gateway API express routing intent, while an actual controller/dataplane implements TLS termination, listeners and backend forwarding.
  3. Get returns selected object information, while describe adds human-readable state and related Events helpful for initial diagnosis.
  4. ConfigMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.

Explanation

Correct Answer

D:

The situation is that a cooperative's workload uses API tokens and administrators propose putting them into a shared configuration map. ConfigMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy. It supports this action: Put non-sensitive application settings in ConfigMaps and put credentials in Secret objects with RBAC, encryption and external secret-management safeguards where appropriate. To confirm, inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.

Incorrect Answers

A:

The situation is that a cooperative's workload uses API tokens and administrators propose putting them into a shared configuration map. 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 configMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.

B:

That statement explains the distinct objective “Choose Ingress or Gateway API with an implementing controller for HTTP exposure” rather than the cause in this case. The deciding mechanism here is that configMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.

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 configMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.

Question 198

A cooperative's workload uses API tokens and administrators propose putting them into a shared configuration map. Which controlled observation would best validate the intended improvement?

  1. Inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.
  2. Deploy a controlled defective revision, record error rate before and after rollout and verify rollback restores the prior behavior.
  3. Apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.
  4. Create matching Service names in two namespaces and test separately configured RBAC and NetworkPolicy access boundaries.

Explanation

Correct Answer

A:

The situation is that a cooperative's workload uses API tokens and administrators propose putting them into a shared configuration map. Inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret. This is the relevant test because configMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.

Incorrect Answers

B:

This check would help evaluate the distinct objective “Correlate application rollout revisions with error spikes”, but not the required result. For this case, inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.

C:

The situation is that a cooperative's workload uses API tokens and administrators propose putting them into a shared configuration map. 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, inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.

D:

This check would help evaluate the distinct objective “Use namespaces as organizational scopes without treating them as firewalls”, but not the required result. For this case, inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.

Question 199

A cooperative's workload uses API tokens and administrators propose putting them into a shared configuration map. An engineer proposes: “Embed production passwords in a ConfigMap because its YAML is easier to inspect and store in a public repository.” What adverse outcome would be most direct?

  1. A resource can remain Pending indefinitely even while its desired configuration is stored correctly.
  2. Secrets can be exposed to broadly authorized readers and source-control users despite apparently valid deployments.
  3. The image-pull issue stays unresolved because etcd is not the node component managing container starts.
  4. PersistentVolumeClaims remain Pending or Pods fail to mount because the required driver integration is missing.

Explanation

Correct Answer

B:

The situation is that a cooperative's workload uses API tokens and administrators propose putting them into a shared configuration map. Secrets can be exposed to broadly authorized readers and source-control users despite apparently valid deployments. The shortcut creates this risk because configMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.

Incorrect Answers

A:

That outcome concerns the distinct objective “Interpret Kubernetes spec and status fields without confusing intent with condition”; it is not the most direct consequence of this shortcut. The relevant consequence is that secrets can be exposed to broadly authorized readers and source-control users despite apparently valid deployments.

C:

That outcome concerns the distinct objective “Recognize the kubelet role in local Pod lifecycle management”; it is not the most direct consequence of this shortcut. The relevant consequence is that secrets can be exposed to broadly authorized readers and source-control users despite apparently valid deployments.

D:

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 secrets can be exposed to broadly authorized readers and source-control users despite apparently valid deployments.

Question 200

A cooperative's workload uses API tokens and administrators propose putting them into a shared configuration map. What pair of supported action and practical verification should be approved?

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

C:

The situation is that a cooperative's workload uses API tokens and administrators propose putting them into a shared configuration map. 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. This pairing is justified because configMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.

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 put non-sensitive application settings in ConfigMaps and put credentials in Secret objects with RBAC, encryption and external secret-management safeguards where appropriate. Its confirming test is to inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.

B:

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 put non-sensitive application settings in ConfigMaps and put credentials in Secret objects with RBAC, encryption and external secret-management safeguards where appropriate. Its confirming test is to inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.

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 put non-sensitive application settings in ConfigMaps and put credentials in Secret objects with RBAC, encryption and external secret-management safeguards where appropriate. Its confirming test is to inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests