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 79

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.

Question 781

A university portal uses distinct nonsecret service URLs and credentials in staging and production. Which engineering approach is the most appropriate for this cloud-native case?

  1. Inject environment-specific nonsecret values through ConfigMaps and secrets through guarded Secret references without rebuilding a different application image.
  2. Use a Deployment for a replicated stateless application requiring rolling updates and replacement of failed Pods.
  3. Configure an HPA for an eligible scalable controller using available resource or custom metrics and sensible minimum/maximum replicas.
  4. Read current logs and --previous logs for the failing container and correlate timestamps with Pod restart counts before altering workloads.

Explanation

Correct Answer

A:

Inject environment-specific nonsecret values through ConfigMaps and secrets through guarded Secret references without rebuilding a different application image. This resolves the issue because image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout. To verify, promote the same image digest into two test namespaces with different safe endpoints, verifying Secret values are not in image layers.

Incorrect Answers

B:

This option addresses the distinct objective “Distinguish Deployment desired state from a manually created Pod”, not the immediate requirement. A Deployment owns ReplicaSets that manage matching Pods and supports declarative rollout history, unlike an independent Pod object. For the stated case, image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout.

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, image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout.

D:

This option addresses the distinct objective “Use kubectl logs and previous container logs to isolate application crashes”, not the immediate requirement. Kubectl logs retrieves container output and --previous can expose the prior terminated instance, but application output is not a substitute for cluster Events. For the stated case, image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout.

Question 782

A university portal uses distinct nonsecret service URLs and credentials in staging and production. What infrastructure principle makes the correct treatment effective?

  1. Image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout.
  2. HPA adjusts desired replica count based on observed metric targets; it needs a functioning metrics source and cannot add missing node capacity itself.
  3. Readiness affects endpoint eligibility while liveness can cause restarts; a startup probe defers other probe checks until initialization succeeds.
  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

A:

Image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout. It supports this action: Inject environment-specific nonsecret values through ConfigMaps and secrets through guarded Secret references without rebuilding a different application image. To confirm, promote the same image digest into two test namespaces with different safe endpoints, verifying Secret values are not in image layers.

Incorrect Answers

B:

That statement explains the distinct objective “Use HorizontalPodAutoscaler metrics rather than ad hoc instance scripts” rather than the cause in this case. The deciding mechanism here is that image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout.

C:

That statement explains the distinct objective “Understand readiness, liveness and startup probes as different signals” rather than the cause in this case. The deciding mechanism here is that image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout.

D:

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 image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout.

Question 783

A university portal uses distinct nonsecret service URLs and credentials in staging and production. What verification result would most convincingly distinguish a working solution from a claim?

  1. Promote the same image digest into two test namespaces with different safe endpoints, verifying Secret values are not in image layers.
  2. Run helm template with staging values, inspect the generated Deployment and Service, and compare a revision's upgrade history.
  3. Apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.
  4. Trace a test commit through build-test-image-digest and compare that digest between staging and production promotion records.

Explanation

Correct Answer

A:

Promote the same image digest into two test namespaces with different safe endpoints, verifying Secret values are not in image layers. This is the relevant test because image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout.

Incorrect Answers

B:

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, promote the same image digest into two test namespaces with different safe endpoints, verifying Secret values are not in image layers.

C:

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, promote the same image digest into two test namespaces with different safe endpoints, verifying Secret values are not in image layers.

D:

This check would help evaluate the distinct objective “Separate CI build verification from CD environment promotion”, but not the required result. For this case, promote the same image digest into two test namespaces with different safe endpoints, verifying Secret values are not in image layers.

Question 784

A university portal uses distinct nonsecret service URLs and credentials in staging and production. The change review contains this proposal: “Compile the database password directly into an application image for each environment and call those artifacts identical releases.” What risk matters most?

  1. New Pods can remain Pending even when the controller increases desired replica count.
  2. The change is repeatedly reverted, making incident response and audit history inconsistent.
  3. Independent rollout, scaling and failure isolation become difficult because the services are coupled to one scheduling unit.
  4. Credentials can leak through registries and the binaries cannot be compared as the same tested artifact.

Explanation

Correct Answer

D:

Credentials can leak through registries and the binaries cannot be compared as the same tested artifact. The shortcut creates this risk 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:

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 credentials can leak through registries and the binaries cannot be compared as the same tested artifact.

B:

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 credentials can leak through registries and the binaries cannot be compared as the same tested artifact.

C:

That outcome concerns the distinct objective “Use Pods as the shared network and storage execution unit”; it is not the most direct consequence of this shortcut. The relevant consequence is that credentials can leak through registries and the binaries cannot be compared as the same tested artifact.

Question 785

A university portal uses distinct nonsecret service URLs and credentials in staging and production. Which implementation together with matching acceptance evidence best meets this case?

  1. Store approved declarative cluster manifests in Git and let a GitOps controller reconcile differences while keeping sensitive access appropriately scoped. Acceptance evidence: Change a test Deployment field outside Git, observe drift and confirm reconciliation restores the reviewed Git value.
  2. 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.
  3. 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.
  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

B:

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 “Apply GitOps reconciliation with a version-controlled desired state” 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.

C:

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 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 “Use Helm charts for parameterized application packages without equating them to cluster controllers” 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 786

A bank needs one application image reused across branches without exposing connection secrets in its Git repository. What technical action should the platform team take in this situation?

  1. Store approved declarative cluster manifests in Git and let a GitOps controller reconcile differences while keeping sensitive access appropriately scoped.
  2. Build an OCI-compatible image with immutable packaged artifacts and treat running container writable state as ephemeral.
  3. Inject environment-specific nonsecret values through ConfigMaps and secrets through guarded Secret references without rebuilding a different application image.
  4. Keep a common base and targeted Kustomize overlays for namespace, image or replica differences across environments.

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. This resolves the issue because image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout. To verify, promote the same image digest into two test namespaces with different safe endpoints, verifying Secret values are not in image layers.

Incorrect Answers

A:

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, image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout.

B:

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, image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout.

D:

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, image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout.

Question 787

A bank needs one application image reused across branches without exposing connection secrets in its Git repository. What underlying Kubernetes behavior is most relevant to this technical decision?

  1. Kubernetes object transitions and application telemetry must be correlated; a healthy rollout condition alone does not prove user-level functionality.
  2. A PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory.
  3. GitOps connects a versioned desired-state source with automated drift detection and reconciliation; direct manual changes may be reverted by the controller.
  4. Image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout.

Explanation

Correct Answer

D:

The situation is that a bank needs one application image reused across branches without exposing connection secrets in its Git repository. Image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout. It supports this action: Inject environment-specific nonsecret values through ConfigMaps and secrets through guarded Secret references without rebuilding a different application image. To confirm, promote the same image digest into two test namespaces with different safe endpoints, verifying Secret values are not in image layers.

Incorrect Answers

A:

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 image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout.

B:

That statement explains the distinct objective “Understand PersistentVolumeClaim binding to persistent storage resources” rather than the cause in this case. The deciding mechanism here is that image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout.

C:

That statement explains the distinct objective “Apply GitOps reconciliation with a version-controlled desired state” rather than the cause in this case. The deciding mechanism here is that image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout.

Question 788

A bank needs one application image reused across branches without exposing connection secrets in its Git repository. What acceptance check most directly confirms this requirement is met?

  1. Promote the same image digest into two test namespaces with different safe endpoints, verifying Secret values are not in image layers.
  2. Upgrade a synthetic four-replica app, monitor old/new ReplicaSets and ready endpoints, then compare observed minimum availability.
  3. Apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.
  4. Generate controlled CPU load, verify HPA current/target metric reporting and observe replica changes within configured limits.

Explanation

Correct Answer

A:

The situation is that a bank needs one application image reused across branches without exposing connection secrets in its Git repository. Promote the same image digest into two test namespaces with different safe endpoints, verifying Secret values are not in image layers. This is the relevant test because image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout.

Incorrect Answers

B:

This check would help evaluate the distinct objective “Configure Deployment rolling updates with availability safeguards”, but not the required result. For this case, promote the same image digest into two test namespaces with different safe endpoints, verifying Secret values are not in image layers.

C:

The situation is that a bank needs one application image reused across branches without exposing connection secrets in its Git repository. 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, promote the same image digest into two test namespaces with different safe endpoints, verifying Secret values are not in image layers.

D:

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, promote the same image digest into two test namespaces with different safe endpoints, verifying Secret values are not in image layers.

Question 789

A bank needs one application image reused across branches without exposing connection secrets in its Git repository. The team suggests: “Compile the database password directly into an application image for each environment and call those artifacts identical releases.” Which failure should the reviewer anticipate?

  1. The change is repeatedly reverted, making incident response and audit history inconsistent.
  2. The true database bottleneck remains and resource adjustments can increase cost without fixing service behavior.
  3. Credentials can leak through registries and the binaries cannot be compared as the same tested artifact.
  4. Operators can see the metadata but the Service cannot select the desired Pods using that annotation.

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. Credentials can leak through registries and the binaries cannot be compared as the same tested artifact. The shortcut creates this risk 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:

The situation is that a bank needs one application image reused across branches without exposing connection secrets in its Git repository. 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 credentials can leak through registries and the binaries cannot be compared as the same tested artifact.

B:

That outcome concerns the distinct objective “Use metrics, logs and traces together when investigating cross-service latency”; it is not the most direct consequence of this shortcut. The relevant consequence is that credentials can leak through registries and the binaries cannot be compared as the same tested artifact.

D:

That outcome concerns the distinct objective “Use annotations for tool metadata rather than workload selection”; it is not the most direct consequence of this shortcut. The relevant consequence is that credentials can leak through registries and the binaries cannot be compared as the same tested artifact.

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.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests