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 80

Question 790

A bank needs one application image reused across branches without exposing connection secrets in its Git repository. Which engineering change and test jointly addresses the scenario?

  1. Inspect the relevant object's conditions and timestamped Events to place the failure at API admission, scheduling, image pulling or runtime startup. Acceptance evidence: Create synthetic invalid quota, unschedulable node and missing-image cases and compare their event reasons and assigned node status.
  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. 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. 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.

Explanation

Correct Answer

C:

The situation is that a bank needs one application image reused across branches without exposing connection secrets in its Git repository. 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. This pairing is justified because image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout.

Incorrect Answers

A:

This action and check address the distinct objective “Use describe and Events to distinguish admission, scheduling and execution errors” instead of the stated acceptance requirement. The matching action is to inject environment-specific nonsecret values through ConfigMaps and secrets through guarded Secret references without rebuilding a different application image. Its confirming test is to promote the same image digest into two test namespaces with different safe endpoints, verifying Secret values are not in image layers.

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 inject environment-specific nonsecret values through ConfigMaps and secrets through guarded Secret references without rebuilding a different application image. Its confirming test is to promote the same image digest into two test namespaces with different safe endpoints, verifying Secret values are not in image layers.

D:

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 inject environment-specific nonsecret values through ConfigMaps and secrets through guarded Secret references without rebuilding a different application image. Its confirming test is to promote the same image digest into two test namespaces with different safe endpoints, verifying Secret values are not in image layers.

Question 791

A charity checkout service sees a spike in failed transactions after a new version becomes ready. Which engineering approach is the most appropriate for this cloud-native case?

  1. Define post-release checks for readiness, error rate and latency, and revert an unhealthy revision using an approved rollout mechanism.
  2. Run automated source tests, dependency checks and artifact signing during CI, then promote the vetted immutable artifact through a controlled delivery stage.
  3. Package reusable Kubernetes resource templates in a Helm chart and review rendered manifests and values before installation or upgrade.
  4. Package workloads in standard images and declarative manifests while documenting external dependencies and provider-specific integrations before claiming portability.

Explanation

Correct Answer

A:

Define post-release checks for readiness, error rate and latency, and revert an unhealthy revision using an approved rollout mechanism. This resolves the issue because a rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible. To verify, deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.

Incorrect Answers

B:

This option addresses the distinct objective “Separate CI build verification from CD environment promotion”, not the immediate requirement. Continuous integration validates and packages changes; continuous delivery or deployment governs how an already-built artifact reaches target environments. For the stated case, a rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.

C:

This option addresses the distinct objective “Use Helm charts for parameterized application packages without equating them to cluster controllers”, not the immediate requirement. Helm renders and manages chart releases but depends on Kubernetes controllers to maintain actual Pods and networking after the API objects exist. For the stated case, a rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.

D:

This option addresses the distinct objective “Apply cloud-native portability and immutable infrastructure principles pragmatically”, not the immediate requirement. Containers and Kubernetes APIs reduce some environment differences, but network load balancers, storage drivers and IAM integrations remain provider-specific. For the stated case, a rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.

Question 792

A charity checkout service sees a spike in failed transactions after a new version becomes ready. What infrastructure principle makes the correct treatment effective?

  1. Different Kubernetes components emit distinct Events; identifying the stage prevents changing unrelated network or application settings.
  2. Image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout.
  3. Declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.
  4. A rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.

Explanation

Correct Answer

D:

A rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible. It supports this action: Define post-release checks for readiness, error rate and latency, and revert an unhealthy revision using an approved rollout mechanism. To confirm, deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.

Incorrect Answers

A:

That statement explains the distinct objective “Use describe and Events to distinguish admission, scheduling and execution errors” rather than the cause in this case. The deciding mechanism here is that a rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.

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 a rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.

C:

That statement explains the distinct objective “Apply resource manifests declaratively instead of depending on imperative drift” rather than the cause in this case. The deciding mechanism here is that a rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.

Question 793

A charity checkout service sees a spike in failed transactions after a new version becomes ready. What verification result would most convincingly distinguish a working solution from a claim?

  1. Insert a deliberately unsigned test image into staging and confirm the release gate blocks production promotion while logging a reason.
  2. Generate controlled CPU load, verify HPA current/target metric reporting and observe replica changes within configured limits.
  3. Deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.
  4. Run a synthetic app that exits with a nonzero code, then confirm describe, previous logs and restart data reveal the failure path.

Explanation

Correct Answer

C:

Deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision. This is the relevant test because a rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.

Incorrect Answers

A:

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, deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.

B:

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, deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.

D:

This check would help evaluate the distinct objective “Diagnose CrashLoopBackOff from restart history and previous logs”, but not the required result. For this case, deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.

Question 794

A charity checkout service sees a spike in failed transactions after a new version becomes ready. The change review contains this proposal: “Assume kubectl apply returned success means the new release is automatically safe for users.” What risk matters most?

  1. The observed rollout may expose far more users than intended because percentage routing was never configured.
  2. The service can remain under capacity because a standalone Pod has no ReplicaSet controller to recreate it.
  3. Customer requests may fail for minutes while operational dashboards report only that the configuration was accepted.
  4. The application never becomes operational because packaging metadata is confused with cluster reconciliation.

Explanation

Correct Answer

C:

Customer requests may fail for minutes while operational dashboards report only that the configuration was accepted. The shortcut creates this risk because a rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.

Incorrect Answers

A:

That outcome concerns the distinct objective “Distinguish canary and blue-green delivery strategies from Kubernetes Deployment defaults”; it is not the most direct consequence of this shortcut. The relevant consequence is that customer requests may fail for minutes while operational dashboards report only that the configuration was accepted.

B:

That outcome concerns the distinct objective “Identify reconciliation work performed by kube-controller-manager”; it is not the most direct consequence of this shortcut. The relevant consequence is that customer requests may fail for minutes while operational dashboards report only that the configuration was accepted.

D:

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 customer requests may fail for minutes while operational dashboards report only that the configuration was accepted.

Question 795

A charity checkout service sees a spike in failed transactions after a new version becomes ready. Which implementation together with matching acceptance evidence best meets this case?

  1. 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.
  2. Define meaningful topology keys, matching label selectors and skew limits when balancing eligible replicas across nodes or zones. Acceptance evidence: Deploy a matching replica set across two labeled zones and inspect skew after adding a new Pod.
  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. 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.

Explanation

Correct Answer

A:

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. This pairing is justified because a rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.

Incorrect Answers

B:

This action and check address the distinct objective “Spread replicas across failure domains with topologySpreadConstraints” instead of the stated acceptance requirement. The matching action is to define post-release checks for readiness, error rate and latency, and revert an unhealthy revision using an approved rollout mechanism. Its confirming test is to deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.

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 define post-release checks for readiness, error rate and latency, and revert an unhealthy revision using an approved rollout mechanism. Its confirming test is to deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.

D:

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 define post-release checks for readiness, error rate and latency, and revert an unhealthy revision using an approved rollout mechanism. Its confirming test is to deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.

Question 796

A college course service needs automated release gates beyond successful container startup. 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. Grant operators only required API verbs and resources using RBAC, then test with kubectl auth can-i and separate synthetic identities.
  3. Configure an HPA for an eligible scalable controller using available resource or custom metrics and sensible minimum/maximum replicas.
  4. Package reusable Kubernetes resource templates in a Helm chart and review rendered manifests and values before installation or upgrade.

Explanation

Correct Answer

A:

The situation is that a college course service needs automated release gates beyond successful container startup. Define post-release checks for readiness, error rate and latency, and revert an unhealthy revision using an approved rollout mechanism. This resolves the issue because a rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible. To verify, deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.

Incorrect Answers

B:

This option addresses the distinct objective “Use least-privilege kubectl authentication and authorization during routine administration”, not the immediate requirement. Authentication establishes who calls the API; RBAC authorization checks requested verb, resource and namespace before the API permits it. For the stated case, a rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.

C:

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, a rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.

D:

The situation is that a college course service needs automated release gates beyond successful container startup. This option addresses the distinct objective “Use Helm charts for parameterized application packages without equating them to cluster controllers”, not the immediate requirement. Helm renders and manages chart releases but depends on Kubernetes controllers to maintain actual Pods and networking after the API objects exist. For the stated case, a rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.

Question 797

A college course service needs automated release gates beyond successful container startup. Which causal explanation supports the intended design choice?

  1. Cordon marks a node unschedulable for new ordinary Pods; drain evicts managed workloads when policies and availability permit.
  2. Image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout.
  3. Kubernetes object transitions and application telemetry must be correlated; a healthy rollout condition alone does not prove user-level functionality.
  4. A rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.

Explanation

Correct Answer

D:

The situation is that a college course service needs automated release gates beyond successful container startup. A rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible. It supports this action: Define post-release checks for readiness, error rate and latency, and revert an unhealthy revision using an approved rollout mechanism. To confirm, deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.

Incorrect Answers

A:

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 a rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.

B:

The situation is that a college course service needs automated release gates beyond successful container startup. 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 a rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.

C:

That statement explains the distinct objective “Correlate application rollout revisions with error spikes” rather than the cause in this case. The deciding mechanism here is that a rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.

Question 798

A college course service needs automated release gates beyond successful container startup. Which test provides the strongest evidence of a correct implementation?

  1. Calculate a synthetic seven-day success ratio from request metrics and compare it to the agreed target before a risky rollout.
  2. Deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.
  3. Generate controlled CPU load, verify HPA current/target metric reporting and observe replica changes within configured limits.
  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

B:

The situation is that a college course service needs automated release gates beyond successful container startup. Deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision. This is the relevant test because a rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Use SLI and SLO measures to focus reliability objectives”, but not the required result. For this case, deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.

C:

The situation is that a college course service needs automated release gates beyond successful container startup. 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, deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.

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, deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.

Question 799

A college course service needs automated release gates beyond successful container startup. A shortcut is proposed: “Assume kubectl apply returned success means the new release is automatically safe for users.” Which technical consequence follows most closely?

  1. Credentials can leak through registries and the binaries cannot be compared as the same tested artifact.
  2. External routing remains absent or policy is misunderstood, and internal identity controls may be incomplete.
  3. Customer requests may fail for minutes while operational dashboards report only that the configuration was accepted.
  4. All existing Pods could become unavailable before replacements pass readiness, breaking live requests.

Explanation

Correct Answer

C:

The situation is that a college course service needs automated release gates beyond successful container startup. Customer requests may fail for minutes while operational dashboards report only that the configuration was accepted. The shortcut creates this risk because a rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.

Incorrect Answers

A:

That outcome concerns the distinct objective “Externalize application configuration from an image while protecting secrets”; it is not the most direct consequence of this shortcut. The relevant consequence is that customer requests may fail for minutes while operational dashboards report only that the configuration was accepted.

B:

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 customer requests may fail for minutes while operational dashboards report only that the configuration was accepted.

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 customer requests may fail for minutes while operational dashboards report only that the configuration was accepted.

Question 800

A college course service needs automated release gates beyond successful container startup. Which combined solution and independent check are most directly justified?

  1. Use metrics for measurable trends, logs for event detail and distributed traces for individual transaction paths while sharing correlation identifiers. Acceptance evidence: Send a synthetic request with a correlation ID and confirm it appears in the trace and relevant logs while latency metrics change.
  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. 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.
  4. 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.

Explanation

Correct Answer

B:

The situation is that a college course service needs automated release gates beyond successful container startup. 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. This pairing is justified because a rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.

Incorrect Answers

A:

This action and check address the distinct objective “Explain metrics, logs and traces as complementary observability signals” instead of the stated acceptance requirement. The matching action is to define post-release checks for readiness, error rate and latency, and revert an unhealthy revision using an approved rollout mechanism. Its confirming test is to deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.

C:

The situation is that a college course service needs automated release gates beyond successful container startup. 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 define post-release checks for readiness, error rate and latency, and revert an unhealthy revision using an approved rollout mechanism. Its confirming test is to deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.

D:

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 define post-release checks for readiness, error rate and latency, and revert an unhealthy revision using an approved rollout mechanism. Its confirming test is to deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests