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 78

Question 770

A university downloads a Helm chart but needs to inspect exactly which resources and privileges it will create. What pair of supported action and practical verification should be approved?

  1. 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.
  2. Select an access mode supported by the actual storage driver and workload placement requirements rather than assuming every volume supports concurrent writes from every node. Acceptance evidence: Use a synthetic two-node workload and compare expected attach behavior for an RWO volume with a documented RWX shared filesystem.
  3. Require reviewed image provenance, admission policy checks and staged traffic validation before promoting a cloud-native application. Acceptance evidence: Insert a deliberately unsigned test image into staging and confirm the release gate blocks production promotion while logging a reason.
  4. Package reusable Kubernetes resource templates in a Helm chart and review rendered manifests and values before installation or upgrade. Acceptance evidence: Run helm template with staging values, inspect the generated Deployment and Service, and compare a revision's upgrade history.

Explanation

Correct Answer

D:

The situation is that a university downloads a Helm chart but needs to inspect exactly which resources and privileges it will create. Package reusable Kubernetes resource templates in a Helm chart and review rendered manifests and values before installation or upgrade. Acceptance evidence: Run helm template with staging values, inspect the generated Deployment and Service, and compare a revision's upgrade history. This pairing is justified because helm renders and manages chart releases but depends on Kubernetes controllers to maintain actual Pods and networking after the API objects exist.

Incorrect Answers

A:

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 package reusable Kubernetes resource templates in a Helm chart and review rendered manifests and values before installation or upgrade. Its confirming test is to run helm template with staging values, inspect the generated Deployment and Service, and compare a revision's upgrade history.

B:

This action and check address the distinct objective “Choose ReadWriteOnce and ReadWriteMany access modes by backend capability” instead of the stated acceptance requirement. The matching action is to package reusable Kubernetes resource templates in a Helm chart and review rendered manifests and values before installation or upgrade. Its confirming test is to run helm template with staging values, inspect the generated Deployment and Service, and compare a revision's upgrade history.

C:

This action and check address the distinct objective “Define secure release governance with staged approvals and policy verification” instead of the stated acceptance requirement. The matching action is to package reusable Kubernetes resource templates in a Helm chart and review rendered manifests and values before installation or upgrade. Its confirming test is to run helm template with staging values, inspect the generated Deployment and Service, and compare a revision's upgrade history.

Question 771

A city web service needs two replicas in staging and six in production using a common deployment definition. Which supported Kubernetes practice directly addresses the stated requirement?

  1. Define post-release checks for readiness, error rate and latency, and revert an unhealthy revision using an approved rollout mechanism.
  2. Store approved declarative cluster manifests in Git and let a GitOps controller reconcile differences while keeping sensitive access appropriately scoped.
  3. Keep a common base and targeted Kustomize overlays for namespace, image or replica differences across environments.
  4. Match a Service's exposed port and targetPort to the actual listening application container, checking protocol and named ports when used.

Explanation

Correct Answer

C:

Keep a common base and targeted Kustomize overlays for namespace, image or replica differences across environments. This resolves the issue because kustomize transforms declarative resource definitions, allowing reviewed variations while preserving a shared base instead of manually editing duplicate files. To verify, run kubectl kustomize for development and production overlays and compare the resulting YAML objects before application.

Incorrect Answers

A:

This option addresses the distinct objective “Design a release rollback trigger from measurable service signals”, not the immediate requirement. A rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible. For the stated case, kustomize transforms declarative resource definitions, allowing reviewed variations while preserving a shared base instead of manually editing duplicate files.

B:

This option addresses the distinct objective “Apply GitOps reconciliation with a version-controlled desired state”, not the immediate requirement. GitOps connects a versioned desired-state source with automated drift detection and reconciliation; direct manual changes may be reverted by the controller. For the stated case, kustomize transforms declarative resource definitions, allowing reviewed variations while preserving a shared base instead of manually editing duplicate files.

D:

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, kustomize transforms declarative resource definitions, allowing reviewed variations while preserving a shared base instead of manually editing duplicate files.

Question 772

A city web service needs two replicas in staging and six in production using a common deployment definition. Which causal explanation supports the intended design choice?

  1. Metrics reveal aggregate trends, logs record events and traces connect operations across services, so each signal answers a different debugging question.
  2. Image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout.
  3. ConfigMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.
  4. Kustomize transforms declarative resource definitions, allowing reviewed variations while preserving a shared base instead of manually editing duplicate files.

Explanation

Correct Answer

D:

Kustomize transforms declarative resource definitions, allowing reviewed variations while preserving a shared base instead of manually editing duplicate files. It supports this action: Keep a common base and targeted Kustomize overlays for namespace, image or replica differences across environments. To confirm, run kubectl kustomize for development and production overlays and compare the resulting YAML objects before application.

Incorrect Answers

A:

That statement explains the distinct objective “Use metrics, logs and traces together when investigating cross-service latency” rather than the cause in this case. The deciding mechanism here is that kustomize transforms declarative resource definitions, allowing reviewed variations while preserving a shared base instead of manually editing duplicate files.

B:

That statement explains the distinct objective “Externalize application configuration from an image while protecting secrets” rather than the cause in this case. The deciding mechanism here is that kustomize transforms declarative resource definitions, allowing reviewed variations while preserving a shared base instead of manually editing duplicate files.

C:

That statement explains the distinct objective “Distinguish ConfigMaps from Secrets and avoid storing credentials in public configuration” rather than the cause in this case. The deciding mechanism here is that kustomize transforms declarative resource definitions, allowing reviewed variations while preserving a shared base instead of manually editing duplicate files.

Question 773

A city web service needs two replicas in staging and six in production using a common deployment definition. Which test provides the strongest evidence of a correct implementation?

  1. Run kubectl kustomize for development and production overlays and compare the resulting YAML objects before application.
  2. Create synthetic invalid quota, unschedulable node and missing-image cases and compare their event reasons and assigned node status.
  3. Simulate an unavailable lab worker, inspect Ready condition and Pod Events, then confirm managed workloads are rescheduled where feasible.
  4. Insert a deliberately unsigned test image into staging and confirm the release gate blocks production promotion while logging a reason.

Explanation

Correct Answer

A:

Run kubectl kustomize for development and production overlays and compare the resulting YAML objects before application. This is the relevant test because kustomize transforms declarative resource definitions, allowing reviewed variations while preserving a shared base instead of manually editing duplicate files.

Incorrect Answers

B:

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, run kubectl kustomize for development and production overlays and compare the resulting YAML objects before application.

C:

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, run kubectl kustomize for development and production overlays and compare the resulting YAML objects before application.

D:

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, run kubectl kustomize for development and production overlays and compare the resulting YAML objects before application.

Question 774

A city web service needs two replicas in staging and six in production using a common deployment definition. A shortcut is proposed: “Maintain unrelated copies of one Deployment YAML for every environment and edit production fields without tracking divergence.” Which technical consequence follows most closely?

  1. The application never becomes operational because packaging metadata is confused with cluster reconciliation.
  2. An urgent fix is applied to only one environment and configuration drift grows difficult to audit.
  3. The emergency fix disappears when the Pod is replaced and cannot be reproduced reliably.
  4. All existing Pods could become unavailable before replacements pass readiness, breaking live requests.

Explanation

Correct Answer

B:

An urgent fix is applied to only one environment and configuration drift grows difficult to audit. The shortcut creates this risk because kustomize transforms declarative resource definitions, allowing reviewed variations while preserving a shared base instead of manually editing duplicate files.

Incorrect Answers

A:

That outcome concerns the distinct objective “Use Helm charts for parameterized application packages without equating them to cluster controllers”; it is not the most direct consequence of this shortcut. The relevant consequence is that an urgent fix is applied to only one environment and configuration drift grows difficult to audit.

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 an urgent fix is applied to only one environment and configuration drift grows difficult to audit.

D:

That outcome concerns the distinct objective “Configure Deployment rolling updates with availability safeguards”; it is not the most direct consequence of this shortcut. The relevant consequence is that an urgent fix is applied to only one environment and configuration drift grows difficult to audit.

Question 775

A city web service needs two replicas in staging and six in production using a common deployment definition. Which combined solution and independent check are most directly justified?

  1. 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.
  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. Use an authorized kubectl debug ephemeral container when an application image lacks troubleshooting tools and policy permits ephemeral containers. Acceptance evidence: In a lab add a read-only debug container, inspect network conditions and verify audit logs record the ephemeral container action.
  4. 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.

Explanation

Correct Answer

A:

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. This pairing is justified because kustomize transforms declarative resource definitions, allowing reviewed variations while preserving a shared base instead of manually editing duplicate files.

Incorrect Answers

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 keep a common base and targeted Kustomize overlays for namespace, image or replica differences across environments. Its confirming test is to run kubectl kustomize for development and production overlays and compare the resulting YAML objects before application.

C:

This action and check address the distinct objective “Use ephemeral debugging containers only with appropriate permission and safeguards” instead of the stated acceptance requirement. The matching action is to keep a common base and targeted Kustomize overlays for namespace, image or replica differences across environments. Its confirming test is to run kubectl kustomize for development and production overlays and compare the resulting YAML objects before application.

D:

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 a common base and targeted Kustomize overlays for namespace, image or replica differences across environments. Its confirming test is to run kubectl kustomize for development and production overlays and compare the resulting YAML objects before application.

Question 776

A college teaching team keeps copying Kubernetes manifests and forgetting to update labels in one environment. What technical action should the platform team take in this situation?

  1. Keep a common base and targeted Kustomize overlays for namespace, image or replica differences across environments.
  2. Check that a supported CNI plugin assigns reachable Pod addresses across worker nodes before troubleshooting Service routing or DNS names.
  3. Route a measured fraction of traffic to a canary or switch between separately verified blue and green environments using an appropriate routing controller.
  4. Inject environment-specific nonsecret values through ConfigMaps and secrets through guarded Secret references without rebuilding a different application image.

Explanation

Correct Answer

A:

The situation is that a college teaching team keeps copying Kubernetes manifests and forgetting to update labels in one environment. Keep a common base and targeted Kustomize overlays for namespace, image or replica differences across environments. This resolves the issue because kustomize transforms declarative resource definitions, allowing reviewed variations while preserving a shared base instead of manually editing duplicate files. To verify, run kubectl kustomize for development and production overlays and compare the resulting YAML objects before application.

Incorrect Answers

B:

This option addresses the distinct objective “Distinguish the CNI Pod network from Service discovery and routing”, not the immediate requirement. Kubernetes expects a Pod network providing Pod-to-Pod connectivity; the CNI implementation configures networking while Services provide stable virtual access to changing endpoints. For the stated case, kustomize transforms declarative resource definitions, allowing reviewed variations while preserving a shared base instead of manually editing duplicate files.

C:

This option addresses the distinct objective “Distinguish canary and blue-green delivery strategies from Kubernetes Deployment defaults”, not the immediate requirement. Canary release needs traffic steering and metrics for a subset; blue-green shifts a complete traffic target after validation, and neither is automatically provided by a plain Deployment update. For the stated case, kustomize transforms declarative resource definitions, allowing reviewed variations while preserving a shared base instead of manually editing duplicate files.

D:

This option addresses the distinct objective “Externalize application configuration from an image while protecting secrets”, not the immediate requirement. Image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout. For the stated case, kustomize transforms declarative resource definitions, allowing reviewed variations while preserving a shared base instead of manually editing duplicate files.

Question 777

A college teaching team keeps copying Kubernetes manifests and forgetting to update labels in one environment. What underlying Kubernetes behavior is most relevant to this technical decision?

  1. Pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes.
  2. Kustomize transforms declarative resource definitions, allowing reviewed variations while preserving a shared base instead of manually editing duplicate files.
  3. Metrics reveal aggregate trends, logs record events and traces connect operations across services, so each signal answers a different debugging question.
  4. A deployment pipeline is a trust boundary; signed artifacts and automated policy tests reduce the risk of unreviewed configurations reaching production.

Explanation

Correct Answer

B:

The situation is that a college teaching team keeps copying Kubernetes manifests and forgetting to update labels in one environment. Kustomize transforms declarative resource definitions, allowing reviewed variations while preserving a shared base instead of manually editing duplicate files. It supports this action: Keep a common base and targeted Kustomize overlays for namespace, image or replica differences across environments. To confirm, run kubectl kustomize for development and production overlays and compare the resulting YAML objects before application.

Incorrect Answers

A:

That statement explains the distinct objective “Use Pod anti-affinity to reduce correlated replica failure” rather than the cause in this case. The deciding mechanism here is that kustomize transforms declarative resource definitions, allowing reviewed variations while preserving a shared base instead of manually editing duplicate files.

C:

The situation is that a college teaching team keeps copying Kubernetes manifests and forgetting to update labels in one environment. That statement explains the distinct objective “Use metrics, logs and traces together when investigating cross-service latency” rather than the cause in this case. The deciding mechanism here is that kustomize transforms declarative resource definitions, allowing reviewed variations while preserving a shared base instead of manually editing duplicate files.

D:

That statement explains the distinct objective “Define secure release governance with staged approvals and policy verification” rather than the cause in this case. The deciding mechanism here is that kustomize transforms declarative resource definitions, allowing reviewed variations while preserving a shared base instead of manually editing duplicate files.

Question 778

A college teaching team keeps copying Kubernetes manifests and forgetting to update labels in one environment. What acceptance check most directly confirms this requirement is met?

  1. Run kubectl kustomize for development and production overlays and compare the resulting YAML objects before application.
  2. Deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.
  3. Run helm template with staging values, inspect the generated Deployment and Service, and compare a revision's upgrade history.
  4. Deploy two synthetic Pods on different nodes and test direct Pod IP connectivity before testing the Service virtual IP.

Explanation

Correct Answer

A:

The situation is that a college teaching team keeps copying Kubernetes manifests and forgetting to update labels in one environment. Run kubectl kustomize for development and production overlays and compare the resulting YAML objects before application. This is the relevant test because kustomize transforms declarative resource definitions, allowing reviewed variations while preserving a shared base instead of manually editing duplicate files.

Incorrect Answers

B:

This check would help evaluate the distinct objective “Design a release rollback trigger from measurable service signals”, but not the required result. For this case, run kubectl kustomize for development and production overlays and compare the resulting YAML objects before application.

C:

This check would help evaluate the distinct objective “Use Helm charts for parameterized application packages without equating them to cluster controllers”, but not the required result. For this case, run kubectl kustomize for development and production overlays and compare the resulting YAML objects before application.

D:

This check would help evaluate the distinct objective “Distinguish the CNI Pod network from Service discovery and routing”, but not the required result. For this case, run kubectl kustomize for development and production overlays and compare the resulting YAML objects before application.

Question 779

A college teaching team keeps copying Kubernetes manifests and forgetting to update labels in one environment. The team suggests: “Maintain unrelated copies of one Deployment YAML for every environment and edit production fields without tracking divergence.” Which failure should the reviewer anticipate?

  1. Untrusted images or privileged settings can enter production without an auditable approval decision.
  2. PersistentVolumeClaims remain Pending or Pods fail to mount because the required driver integration is missing.
  3. An urgent fix is applied to only one environment and configuration drift grows difficult to audit.
  4. The change is repeatedly reverted, making incident response and audit history inconsistent.

Explanation

Correct Answer

C:

The situation is that a college teaching team keeps copying Kubernetes manifests and forgetting to update labels in one environment. An urgent fix is applied to only one environment and configuration drift grows difficult to audit. The shortcut creates this risk because kustomize transforms declarative resource definitions, allowing reviewed variations while preserving a shared base instead of manually editing duplicate files.

Incorrect Answers

A:

That outcome concerns the distinct objective “Define secure release governance with staged approvals and policy verification”; it is not the most direct consequence of this shortcut. The relevant consequence is that an urgent fix is applied to only one environment and configuration drift grows difficult to audit.

B:

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 an urgent fix is applied to only one environment and configuration drift grows difficult to audit.

D:

That outcome concerns the distinct objective “Apply GitOps reconciliation with a version-controlled desired state”; it is not the most direct consequence of this shortcut. The relevant consequence is that an urgent fix is applied to only one environment and configuration drift grows difficult to audit.

Question 780

A college teaching team keeps copying Kubernetes manifests and forgetting to update labels in one environment. Which engineering change and test jointly addresses the scenario?

  1. Compare Deployment rollout history, changed image digests, readiness events and application error times to identify an introduced regression. Acceptance evidence: Deploy a controlled defective revision, record error rate before and after rollout and verify rollback restores the prior behavior.
  2. Route a measured fraction of traffic to a canary or switch between separately verified blue and green environments using an appropriate routing controller. Acceptance evidence: In a staging gateway route 5 percent to a canary, inspect version-specific success rates and verify a rollback rule.
  3. 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.
  4. Package workloads in standard images and declarative manifests while documenting external dependencies and provider-specific integrations before claiming portability. Acceptance evidence: Deploy a synthetic stateless workload to two conformant clusters and record which storage, ingress and identity settings require changes.

Explanation

Correct Answer

C:

The situation is that a college teaching team keeps copying Kubernetes manifests and forgetting to update labels in one environment. 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. This pairing is justified because kustomize transforms declarative resource definitions, allowing reviewed variations while preserving a shared base instead of manually editing duplicate files.

Incorrect Answers

A:

This action and check address the distinct objective “Correlate application rollout revisions with error spikes” instead of the stated acceptance requirement. The matching action is to keep a common base and targeted Kustomize overlays for namespace, image or replica differences across environments. Its confirming test is to run kubectl kustomize for development and production overlays and compare the resulting YAML objects before application.

B:

This action and check address the distinct objective “Distinguish canary and blue-green delivery strategies from Kubernetes Deployment defaults” instead of the stated acceptance requirement. The matching action is to keep a common base and targeted Kustomize overlays for namespace, image or replica differences across environments. Its confirming test is to run kubectl kustomize for development and production overlays and compare the resulting YAML objects before application.

D:

This action and check address the distinct objective “Apply cloud-native portability and immutable infrastructure principles pragmatically” instead of the stated acceptance requirement. The matching action is to keep a common base and targeted Kustomize overlays for namespace, image or replica differences across environments. Its confirming test is to run kubectl kustomize for development and production overlays and compare the resulting YAML objects before application.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests