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 77

Question 760

An insurance developer believes passing unit tests automatically updates all live services without a delivery step. Which combined solution and independent check are most directly justified?

  1. 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.
  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. 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. Inject environment-specific nonsecret values through ConfigMaps and secrets through guarded Secret references without rebuilding a different application image. Acceptance evidence: Promote the same image digest into two test namespaces with different safe endpoints, verifying Secret values are not in image layers.

Explanation

Correct Answer

B:

The situation is that an insurance developer believes passing unit tests automatically updates all live services without a delivery step. 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. This pairing is justified because continuous integration validates and packages changes; continuous delivery or deployment governs how an already-built artifact reaches target environments.

Incorrect Answers

A:

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 run automated source tests, dependency checks and artifact signing during CI, then promote the vetted immutable artifact through a controlled delivery stage. Its confirming test is to trace a test commit through build-test-image-digest and compare that digest between staging and production promotion records.

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 run automated source tests, dependency checks and artifact signing during CI, then promote the vetted immutable artifact through a controlled delivery stage. Its confirming test is to trace a test commit through build-test-image-digest and compare that digest between staging and production promotion records.

D:

This action and check address the distinct objective “Externalize application configuration from an image while protecting secrets” instead of the stated acceptance requirement. The matching action is to run automated source tests, dependency checks and artifact signing during CI, then promote the vetted immutable artifact through a controlled delivery stage. Its confirming test is to trace a test commit through build-test-image-digest and compare that digest between staging and production promotion records.

Question 761

A software vendor distributes the same web application to multiple customers with environment-specific replica settings. Which Kubernetes or cloud-native implementation decision best solves the stated problem?

  1. Package reusable Kubernetes resource templates in a Helm chart and review rendered manifests and values before installation or upgrade.
  2. Keep a common base and targeted Kustomize overlays for namespace, image or replica differences across environments.
  3. Apply PriorityClasses sparingly for essential workloads and plan capacity so preemption does not unnecessarily evict useful lower-priority Pods.
  4. Require reviewed image provenance, admission policy checks and staged traffic validation before promoting a cloud-native application.

Explanation

Correct Answer

A:

Package reusable Kubernetes resource templates in a Helm chart and review rendered manifests and values before installation or upgrade. This resolves the issue because helm renders and manages chart releases but depends on Kubernetes controllers to maintain actual Pods and networking after the API objects exist. To verify, run helm template with staging values, inspect the generated Deployment and Service, and compare a revision's upgrade history.

Incorrect Answers

B:

This option addresses the distinct objective “Use Kustomize overlays to adapt manifests without copying whole deployments”, not the immediate requirement. Kustomize transforms declarative resource definitions, allowing reviewed variations while preserving a shared base instead of manually editing duplicate files. For the stated case, helm renders and manages chart releases but depends on Kubernetes controllers to maintain actual Pods and networking after the API objects exist.

C:

This option addresses the distinct objective “Use PriorityClasses and understand preemption without assuming they guarantee availability”, not the immediate requirement. Under pressure, a higher-priority pending Pod may preempt eligible lower-priority Pods, but constraints and eviction rules still apply. For the stated case, helm renders and manages chart releases but depends on Kubernetes controllers to maintain actual Pods and networking after the API objects exist.

D:

This option addresses the distinct objective “Define secure release governance with staged approvals and policy verification”, not the immediate requirement. A deployment pipeline is a trust boundary; signed artifacts and automated policy tests reduce the risk of unreviewed configurations reaching production. For the stated case, helm renders and manages chart releases but depends on Kubernetes controllers to maintain actual Pods and networking after the API objects exist.

Question 762

A software vendor distributes the same web application to multiple customers with environment-specific replica settings. Which platform mechanism explains why the suitable approach works?

  1. Helm renders and manages chart releases but depends on Kubernetes controllers to maintain actual Pods and networking after the API objects exist.
  2. SecurityContext configures process identity and privilege boundaries, and unnecessary root privileges increase impact if an application is compromised.
  3. A rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.
  4. A Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.

Explanation

Correct Answer

A:

Helm renders and manages chart releases but depends on Kubernetes controllers to maintain actual Pods and networking after the API objects exist. It supports this action: Package reusable Kubernetes resource templates in a Helm chart and review rendered manifests and values before installation or upgrade. To confirm, run helm template with staging values, inspect the generated Deployment and Service, and compare a revision's upgrade history.

Incorrect Answers

B:

That statement explains the distinct objective “Run images with least-privilege runtime security contexts” rather than the cause in this case. The deciding mechanism here is that helm renders and manages chart releases but depends on Kubernetes controllers to maintain actual Pods and networking after the API objects exist.

C:

That statement explains the distinct objective “Design a release rollback trigger from measurable service signals” rather than the cause in this case. The deciding mechanism here is that helm renders and manages chart releases but depends on Kubernetes controllers to maintain actual Pods and networking after the API objects exist.

D:

That statement explains the distinct objective “Distinguish a failed Service selector from broken DNS or a failing backend” rather than the cause in this case. The deciding mechanism here is that helm renders and manages chart releases but depends on Kubernetes controllers to maintain actual Pods and networking after the API objects exist.

Question 763

A software vendor distributes the same web application to multiple customers with environment-specific replica settings. Which controlled observation would best validate the intended improvement?

  1. Generate controlled CPU load, verify HPA current/target metric reporting and observe replica changes within configured limits.
  2. Run helm template with staging values, inspect the generated Deployment and Service, and compare a revision's upgrade history.
  3. Generate a synthetic slow downstream call and verify a trace links frontend and backend spans while metrics show the latency change.
  4. List Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.

Explanation

Correct Answer

B:

Run helm template with staging values, inspect the generated Deployment and Service, and compare a revision's upgrade history. This is the relevant test 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 check would help evaluate the distinct objective “Use HorizontalPodAutoscaler metrics rather than ad hoc instance scripts”, but not the required result. For this case, run helm template with staging values, inspect the generated Deployment and Service, and compare a revision's upgrade history.

C:

This check would help evaluate the distinct objective “Use metrics, logs and traces together when investigating cross-service latency”, but not the required result. For this case, run helm template with staging values, inspect the generated Deployment and Service, and compare a revision's upgrade history.

D:

This check would help evaluate the distinct objective “Read the API resource model using namespaces and names rather than guessing ownership”, but not the required result. For this case, run helm template with staging values, inspect the generated Deployment and Service, and compare a revision's upgrade history.

Question 764

A software vendor distributes the same web application to multiple customers with environment-specific replica settings. An engineer proposes: “Assume installing Helm itself schedules Pods, enforces RBAC and creates load balancers even when no Kubernetes objects are rendered.” What adverse outcome would be most direct?

  1. The application never becomes operational because packaging metadata is confused with cluster reconciliation.
  2. All existing Pods could become unavailable before replacements pass readiness, breaking live requests.
  3. The Pod continues restarting because Service DNS configuration is not the cause of the process exit.
  4. New Pods can remain Pending even when the controller increases desired replica count.

Explanation

Correct Answer

A:

The application never becomes operational because packaging metadata is confused with cluster reconciliation. The shortcut creates this risk 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

B:

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 the application never becomes operational because packaging metadata is confused with cluster reconciliation.

C:

That outcome concerns the distinct objective “Diagnose CrashLoopBackOff from restart history and previous logs”; it is not the most direct consequence of this shortcut. The relevant consequence is that the application never becomes operational because packaging metadata is confused with cluster reconciliation.

D:

That outcome concerns the distinct objective “Use HorizontalPodAutoscaler metrics rather than ad hoc instance scripts”; it is not the most direct consequence of this shortcut. The relevant consequence is that the application never becomes operational because packaging metadata is confused with cluster reconciliation.

Question 765

A software vendor distributes the same web application to multiple customers with environment-specific replica settings. What pair of supported action and practical verification should be approved?

  1. 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.
  2. Set runAsNonRoot, suitable user IDs and drop unneeded Linux capabilities rather than assuming every container requires root. Acceptance evidence: Deploy a test Pod with runAsNonRoot and verify its effective user and capability sets while confirming app file permissions work.
  3. Inject environment-specific nonsecret values through ConfigMaps and secrets through guarded Secret references without rebuilding a different application image. Acceptance evidence: Promote the same image digest into two test namespaces with different safe endpoints, verifying Secret values are not in image layers.
  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:

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 “Distinguish canary and blue-green delivery strategies from Kubernetes Deployment defaults” 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 “Run images with least-privilege runtime security contexts” 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 “Externalize application configuration from an image while protecting secrets” 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 766

A university downloads a Helm chart but needs to inspect exactly which resources and privileges it will create. Which Kubernetes or cloud-native implementation decision best solves the stated problem?

  1. Package reusable Kubernetes resource templates in a Helm chart and review rendered manifests and values before installation or upgrade.
  2. Configure an HPA for an eligible scalable controller using available resource or custom metrics and sensible minimum/maximum replicas.
  3. Use emptyDir for temporary sharing between containers within a Pod, and PVC-backed storage when data must survive Pod replacement.
  4. Run automated source tests, dependency checks and artifact signing during CI, then promote the vetted immutable artifact through a controlled delivery stage.

Explanation

Correct Answer

A:

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. This resolves the issue because helm renders and manages chart releases but depends on Kubernetes controllers to maintain actual Pods and networking after the API objects exist. To verify, run helm template with staging values, inspect the generated Deployment and Service, and compare a revision's upgrade history.

Incorrect Answers

B:

This option addresses the distinct objective “Use HorizontalPodAutoscaler metrics rather than ad hoc instance scripts”, not the immediate requirement. HPA adjusts desired replica count based on observed metric targets; it needs a functioning metrics source and cannot add missing node capacity itself. For the stated case, helm renders and manages chart releases but depends on Kubernetes controllers to maintain actual Pods and networking after the API objects exist.

C:

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, helm renders and manages chart releases but depends on Kubernetes controllers to maintain actual Pods and networking after the API objects exist.

D:

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, helm renders and manages chart releases but depends on Kubernetes controllers to maintain actual Pods and networking after the API objects exist.

Question 767

A university downloads a Helm chart but needs to inspect exactly which resources and privileges it will create. Which platform mechanism explains why the suitable approach works?

  1. Helm renders and manages chart releases but depends on Kubernetes controllers to maintain actual Pods and networking after the API objects exist.
  2. Namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.
  3. Kustomize transforms declarative resource definitions, allowing reviewed variations while preserving a shared base instead of manually editing duplicate files.
  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

A:

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

Incorrect Answers

B:

That statement explains the distinct objective “Separate multi-tenant namespace governance from actual isolation guarantees” rather than the cause in this case. The deciding mechanism here is that helm renders and manages chart releases but depends on Kubernetes controllers to maintain actual Pods and networking after the API objects exist.

C:

That statement explains the distinct objective “Use Kustomize overlays to adapt manifests without copying whole deployments” rather than the cause in this case. The deciding mechanism here is that helm renders and manages chart releases but depends on Kubernetes controllers to maintain actual Pods and networking after the API objects exist.

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 helm renders and manages chart releases but depends on Kubernetes controllers to maintain actual Pods and networking after the API objects exist.

Question 768

A university downloads a Helm chart but needs to inspect exactly which resources and privileges it will create. Which controlled observation would best validate the intended improvement?

  1. Deploy a matching replica set across two labeled zones and inspect skew after adding a new Pod.
  2. Generate controlled CPU load, verify HPA current/target metric reporting and observe replica changes within configured limits.
  3. Run helm template with staging values, inspect the generated Deployment and Service, and compare a revision's upgrade history.
  4. In a lab add a read-only debug container, inspect network conditions and verify audit logs record the ephemeral container action.

Explanation

Correct Answer

C:

The situation is that a university downloads a Helm chart but needs to inspect exactly which resources and privileges it will create. Run helm template with staging values, inspect the generated Deployment and Service, and compare a revision's upgrade history. This is the relevant test 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 check would help evaluate the distinct objective “Spread replicas across failure domains with topologySpreadConstraints”, but not the required result. For this case, run helm template with staging values, inspect the generated Deployment and Service, and compare a revision's upgrade history.

B:

The situation is that a university downloads a Helm chart but needs to inspect exactly which resources and privileges it will create. This check would help evaluate the distinct objective “Use HorizontalPodAutoscaler metrics rather than ad hoc instance scripts”, but not the required result. For this case, run helm template with staging values, inspect the generated Deployment and Service, and compare a revision's upgrade history.

D:

This check would help evaluate the distinct objective “Use ephemeral debugging containers only with appropriate permission and safeguards”, but not the required result. For this case, run helm template with staging values, inspect the generated Deployment and Service, and compare a revision's upgrade history.

Question 769

A university downloads a Helm chart but needs to inspect exactly which resources and privileges it will create. An engineer proposes: “Assume installing Helm itself schedules Pods, enforces RBAC and creates load balancers even when no Kubernetes objects are rendered.” What adverse outcome would be most direct?

  1. A resource can remain Pending indefinitely even while its desired configuration is stored correctly.
  2. Untrusted images or privileged settings can enter production without an auditable approval decision.
  3. An application regression can remain live even though container and readiness probes are healthy.
  4. The application never becomes operational because packaging metadata is confused with cluster reconciliation.

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. The application never becomes operational because packaging metadata is confused with cluster reconciliation. The shortcut creates this risk 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:

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 the application never becomes operational because packaging metadata is confused with cluster reconciliation.

B:

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 the application never becomes operational because packaging metadata is confused with cluster reconciliation.

C:

That outcome concerns the distinct objective “Correlate application rollout revisions with error spikes”; it is not the most direct consequence of this shortcut. The relevant consequence is that the application never becomes operational because packaging metadata is confused with cluster reconciliation.

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.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests