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 82

Question 810

A retailer expects an autoscaler to solve high latency caused by an overloaded fixed-size storage backend. Which implementation together with matching acceptance evidence best meets this case?

  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. 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.
  3. 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.
  4. Configure an HPA for an eligible scalable controller using available resource or custom metrics and sensible minimum/maximum replicas. Acceptance evidence: Generate controlled CPU load, verify HPA current/target metric reporting and observe replica changes within configured limits.

Explanation

Correct Answer

D:

The situation is that a retailer expects an autoscaler to solve high latency caused by an overloaded fixed-size storage backend. Configure an HPA for an eligible scalable controller using available resource or custom metrics and sensible minimum/maximum replicas. Acceptance evidence: Generate controlled CPU load, verify HPA current/target metric reporting and observe replica changes within configured limits. This pairing is justified because HPA adjusts desired replica count based on observed metric targets; it needs a functioning metrics source and cannot add missing node capacity itself.

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 configure an HPA for an eligible scalable controller using available resource or custom metrics and sensible minimum/maximum replicas. Its confirming test is to generate controlled CPU load, verify HPA current/target metric reporting and observe replica changes within configured limits.

B:

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 configure an HPA for an eligible scalable controller using available resource or custom metrics and sensible minimum/maximum replicas. Its confirming test is to generate controlled CPU load, verify HPA current/target metric reporting and observe replica changes within configured limits.

C:

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 configure an HPA for an eligible scalable controller using available resource or custom metrics and sensible minimum/maximum replicas. Its confirming test is to generate controlled CPU load, verify HPA current/target metric reporting and observe replica changes within configured limits.

Question 811

A medical technology company must validate third-party sidecar images before deployment. Which supported Kubernetes practice directly addresses the stated requirement?

  1. Match a Service's exposed port and targetPort to the actual listening application container, checking protocol and named ports when used.
  2. Define post-release checks for readiness, error rate and latency, and revert an unhealthy revision using an approved rollout mechanism.
  3. Package reusable Kubernetes resource templates in a Helm chart and review rendered manifests and values before installation or upgrade.
  4. Require reviewed image provenance, admission policy checks and staged traffic validation before promoting a cloud-native application.

Explanation

Correct Answer

D:

Require reviewed image provenance, admission policy checks and staged traffic validation before promoting a cloud-native application. This resolves the issue because a deployment pipeline is a trust boundary; signed artifacts and automated policy tests reduce the risk of unreviewed configurations reaching production. To verify, insert a deliberately unsigned test image into staging and confirm the release gate blocks production promotion while logging a reason.

Incorrect Answers

A:

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, a deployment pipeline is a trust boundary; signed artifacts and automated policy tests reduce the risk of unreviewed configurations reaching production.

B:

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, a deployment pipeline is a trust boundary; signed artifacts and automated policy tests reduce the risk of unreviewed configurations reaching production.

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 deployment pipeline is a trust boundary; signed artifacts and automated policy tests reduce the risk of unreviewed configurations reaching production.

Question 812

A medical technology company must validate third-party sidecar images before deployment. Which causal explanation supports the intended design choice?

  1. GitOps connects a versioned desired-state source with automated drift detection and reconciliation; direct manual changes may be reverted by the controller.
  2. CoreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains.
  3. Helm renders and manages chart releases but depends on Kubernetes controllers to maintain actual Pods and networking after the API objects exist.
  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

D:

A deployment pipeline is a trust boundary; signed artifacts and automated policy tests reduce the risk of unreviewed configurations reaching production. It supports this action: Require reviewed image provenance, admission policy checks and staged traffic validation before promoting a cloud-native application. To confirm, insert a deliberately unsigned test image into staging and confirm the release gate blocks production promotion while logging a reason.

Incorrect Answers

A:

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 a deployment pipeline is a trust boundary; signed artifacts and automated policy tests reduce the risk of unreviewed configurations reaching production.

B:

That statement explains the distinct objective “Verify CoreDNS resolution and namespace-qualified Service names” rather than the cause in this case. The deciding mechanism here is that a deployment pipeline is a trust boundary; signed artifacts and automated policy tests reduce the risk of unreviewed configurations reaching production.

C:

That statement explains the distinct objective “Use Helm charts for parameterized application packages without equating them to cluster controllers” rather than the cause in this case. The deciding mechanism here is that a deployment pipeline is a trust boundary; signed artifacts and automated policy tests reduce the risk of unreviewed configurations reaching production.

Question 813

A medical technology company must validate third-party sidecar images before deployment. Which test provides the strongest evidence of a correct implementation?

  1. Delete one test Deployment-owned Pod and observe a replacement appear without a new Deployment definition.
  2. Insert a deliberately unsigned test image into staging and confirm the release gate blocks production promotion while logging a reason.
  3. Run helm template with staging values, inspect the generated Deployment and Service, and compare a revision's upgrade history.
  4. 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:

Insert a deliberately unsigned test image into staging and confirm the release gate blocks production promotion while logging a reason. This is the relevant test because a deployment pipeline is a trust boundary; signed artifacts and automated policy tests reduce the risk of unreviewed configurations reaching production.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Identify reconciliation work performed by kube-controller-manager”, but not the required result. For this case, insert a deliberately unsigned test image into staging and confirm the release gate blocks production promotion while logging a reason.

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, insert a deliberately unsigned test image into staging and confirm the release gate blocks production promotion while logging a reason.

D:

This check would help evaluate the distinct objective “Externalize application configuration from an image while protecting secrets”, but not the required result. For this case, insert a deliberately unsigned test image into staging and confirm the release gate blocks production promotion while logging a reason.

Question 814

A medical technology company must validate third-party sidecar images before deployment. A shortcut is proposed: “Disable the container registry and admission checks for all namespaces to accelerate one urgent developer demonstration.” Which technical consequence follows most closely?

  1. Untrusted images or privileged settings can enter production without an auditable approval decision.
  2. The production binary can differ from the validated image even though the release version label matches.
  3. The application never becomes operational because packaging metadata is confused with cluster reconciliation.
  4. A working dataplane may be needlessly modified, disrupting traffic that was already being forwarded correctly.

Explanation

Correct Answer

A:

Untrusted images or privileged settings can enter production without an auditable approval decision. The shortcut creates this risk because a deployment pipeline is a trust boundary; signed artifacts and automated policy tests reduce the risk of unreviewed configurations reaching production.

Incorrect Answers

B:

That outcome concerns the distinct objective “Separate CI build verification from CD environment promotion”; it is not the most direct consequence of this shortcut. The relevant consequence is that untrusted images or privileged settings can enter production without an auditable approval decision.

C:

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 untrusted images or privileged settings can enter production without an auditable approval decision.

D:

That outcome concerns the distinct objective “Understand service proxy implementations without assuming kube-proxy is mandatory”; it is not the most direct consequence of this shortcut. The relevant consequence is that untrusted images or privileged settings can enter production without an auditable approval decision.

Question 815

A medical technology company must validate third-party sidecar images before deployment. Which combined solution and independent check are most directly justified?

  1. Read a workload's spec and status separately and inspect conditions when determining whether an API change became healthy. Acceptance evidence: Apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.
  2. Choose an appropriate RollingUpdate strategy with maxSurge and maxUnavailable, and verify readiness and service traffic during replacement. Acceptance evidence: Upgrade a synthetic four-replica app, monitor old/new ReplicaSets and ready endpoints, then compare observed minimum availability.
  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. 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.

Explanation

Correct Answer

C:

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. This pairing is justified because a deployment pipeline is a trust boundary; signed artifacts and automated policy tests reduce the risk of unreviewed configurations reaching production.

Incorrect Answers

A:

This action and check address the distinct objective “Interpret Kubernetes spec and status fields without confusing intent with condition” instead of the stated acceptance requirement. The matching action is to require reviewed image provenance, admission policy checks and staged traffic validation before promoting a cloud-native application. Its confirming test is to insert a deliberately unsigned test image into staging and confirm the release gate blocks production promotion while logging a reason.

B:

This action and check address the distinct objective “Configure Deployment rolling updates with availability safeguards” instead of the stated acceptance requirement. The matching action is to require reviewed image provenance, admission policy checks and staged traffic validation before promoting a cloud-native application. Its confirming test is to insert a deliberately unsigned test image into staging and confirm the release gate blocks production promotion while logging a reason.

D:

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 require reviewed image provenance, admission policy checks and staged traffic validation before promoting a cloud-native application. Its confirming test is to insert a deliberately unsigned test image into staging and confirm the release gate blocks production promotion while logging a reason.

Question 816

A college shares a Kubernetes production cluster and wants an auditable promotion gate for student applications. Which engineering approach is the most appropriate for this cloud-native case?

  1. Change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation.
  2. Require reviewed image provenance, admission policy checks and staged traffic validation before promoting a cloud-native application.
  3. Keep a common base and targeted Kustomize overlays for namespace, image or replica differences across environments.
  4. Choose an appropriate RollingUpdate strategy with maxSurge and maxUnavailable, and verify readiness and service traffic during replacement.

Explanation

Correct Answer

B:

The situation is that a college shares a Kubernetes production cluster and wants an auditable promotion gate for student applications. Require reviewed image provenance, admission policy checks and staged traffic validation before promoting a cloud-native application. This resolves the issue because a deployment pipeline is a trust boundary; signed artifacts and automated policy tests reduce the risk of unreviewed configurations reaching production. To verify, insert a deliberately unsigned test image into staging and confirm the release gate blocks production promotion while logging a reason.

Incorrect Answers

A:

This option addresses the distinct objective “Explain desired state versus observed status in Kubernetes objects”, not the immediate requirement. The API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence. For the stated case, a deployment pipeline is a trust boundary; signed artifacts and automated policy tests reduce the risk of unreviewed configurations reaching production.

C:

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, a deployment pipeline is a trust boundary; signed artifacts and automated policy tests reduce the risk of unreviewed configurations reaching production.

D:

This option addresses the distinct objective “Configure Deployment rolling updates with availability safeguards”, not the immediate requirement. A rolling Deployment temporarily creates and removes Pods within its surge and unavailable budgets, but readiness is required for new replicas to count as available. For the stated case, a deployment pipeline is a trust boundary; signed artifacts and automated policy tests reduce the risk of unreviewed configurations reaching production.

Question 817

A college shares a Kubernetes production cluster and wants an auditable promotion gate for student applications. What infrastructure principle makes the correct treatment effective?

  1. GitOps connects a versioned desired-state source with automated drift detection and reconciliation; direct manual changes may be reverted by the controller.
  2. A deployment pipeline is a trust boundary; signed artifacts and automated policy tests reduce the risk of unreviewed configurations reaching production.
  3. emptyDir is initialized for a Pod and its contents can be shared among containers but do not survive the Pod's removal.
  4. Different Kubernetes components emit distinct Events; identifying the stage prevents changing unrelated network or application settings.

Explanation

Correct Answer

B:

The situation is that a college shares a Kubernetes production cluster and wants an auditable promotion gate for student applications. A deployment pipeline is a trust boundary; signed artifacts and automated policy tests reduce the risk of unreviewed configurations reaching production. It supports this action: Require reviewed image provenance, admission policy checks and staged traffic validation before promoting a cloud-native application. To confirm, insert a deliberately unsigned test image into staging and confirm the release gate blocks production promotion while logging a reason.

Incorrect Answers

A:

The situation is that a college shares a Kubernetes production cluster and wants an auditable promotion gate for student applications. 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 a deployment pipeline is a trust boundary; signed artifacts and automated policy tests reduce the risk of unreviewed configurations reaching production.

C:

That statement explains the distinct objective “Understand emptyDir as Pod-lifetime shared storage, not durable application persistence” rather than the cause in this case. The deciding mechanism here is that a deployment pipeline is a trust boundary; signed artifacts and automated policy tests reduce the risk of unreviewed configurations reaching production.

D:

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 deployment pipeline is a trust boundary; signed artifacts and automated policy tests reduce the risk of unreviewed configurations reaching production.

Question 818

A college shares a Kubernetes production cluster and wants an auditable promotion gate for student applications. What verification result would most convincingly distinguish a working solution from a claim?

  1. Change a test Deployment field outside Git, observe drift and confirm reconciliation restores the reviewed Git value.
  2. Insert a deliberately unsigned test image into staging and confirm the release gate blocks production promotion while logging a reason.
  3. Bind a synthetic ClusterRole through RoleBinding in namespace-a, then verify access fails in namespace-b.
  4. Upgrade a synthetic four-replica app, monitor old/new ReplicaSets and ready endpoints, then compare observed minimum availability.

Explanation

Correct Answer

B:

The situation is that a college shares a Kubernetes production cluster and wants an auditable promotion gate for student applications. Insert a deliberately unsigned test image into staging and confirm the release gate blocks production promotion while logging a reason. This is the relevant test because a deployment pipeline is a trust boundary; signed artifacts and automated policy tests reduce the risk of unreviewed configurations reaching production.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Apply GitOps reconciliation with a version-controlled desired state”, but not the required result. For this case, insert a deliberately unsigned test image into staging and confirm the release gate blocks production promotion while logging a reason.

C:

This check would help evaluate the distinct objective “Distinguish ClusterRoles from Roles and binding scope”, but not the required result. For this case, insert a deliberately unsigned test image into staging and confirm the release gate blocks production promotion while logging a reason.

D:

This check would help evaluate the distinct objective “Configure Deployment rolling updates with availability safeguards”, but not the required result. For this case, insert a deliberately unsigned test image into staging and confirm the release gate blocks production promotion while logging a reason.

Question 819

A college shares a Kubernetes production cluster and wants an auditable promotion gate for student applications. The change review contains this proposal: “Disable the container registry and admission checks for all namespaces to accelerate one urgent developer demonstration.” What risk matters most?

  1. Security decisions overlook shared-kernel attack surfaces and workload-specific resource contention.
  2. New Pods can remain Pending even when the controller increases desired replica count.
  3. The application never becomes operational because packaging metadata is confused with cluster reconciliation.
  4. Untrusted images or privileged settings can enter production without an auditable approval decision.

Explanation

Correct Answer

D:

The situation is that a college shares a Kubernetes production cluster and wants an auditable promotion gate for student applications. Untrusted images or privileged settings can enter production without an auditable approval decision. The shortcut creates this risk because a deployment pipeline is a trust boundary; signed artifacts and automated policy tests reduce the risk of unreviewed configurations reaching production.

Incorrect Answers

A:

That outcome concerns the distinct objective “Explain Linux namespaces and cgroups as distinct container isolation mechanisms”; it is not the most direct consequence of this shortcut. The relevant consequence is that untrusted images or privileged settings can enter production without an auditable approval decision.

B:

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 untrusted images or privileged settings can enter production without an auditable approval decision.

C:

The situation is that a college shares a Kubernetes production cluster and wants an auditable promotion gate for student applications. 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 untrusted images or privileged settings can enter production without an auditable approval decision.

Question 820

A college shares a Kubernetes production cluster and wants an auditable promotion gate for student applications. Which implementation together with matching acceptance evidence best meets this case?

  1. Choose an appropriate RollingUpdate strategy with maxSurge and maxUnavailable, and verify readiness and service traffic during replacement. Acceptance evidence: Upgrade a synthetic four-replica app, monitor old/new ReplicaSets and ready endpoints, then compare observed minimum availability.
  2. Choose a CRI-compatible container runtime on worker nodes and investigate image and container creation separately from API scheduling. Acceptance evidence: Inspect node runtime information and compare a Pod's scheduling success with a runtime-reported image or sandbox failure.
  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

C:

The situation is that a college shares a Kubernetes production cluster and wants an auditable promotion gate for student applications. 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. This pairing is justified because a deployment pipeline is a trust boundary; signed artifacts and automated policy tests reduce the risk of unreviewed configurations reaching production.

Incorrect Answers

A:

The situation is that a college shares a Kubernetes production cluster and wants an auditable promotion gate for student applications. This action and check address the distinct objective “Configure Deployment rolling updates with availability safeguards” instead of the stated acceptance requirement. The matching action is to require reviewed image provenance, admission policy checks and staged traffic validation before promoting a cloud-native application. Its confirming test is to insert a deliberately unsigned test image into staging and confirm the release gate blocks production promotion while logging a reason.

B:

This action and check address the distinct objective “Explain the container runtime interface without conflating it with the control plane” instead of the stated acceptance requirement. The matching action is to require reviewed image provenance, admission policy checks and staged traffic validation before promoting a cloud-native application. Its confirming test is to insert a deliberately unsigned test image into staging and confirm the release gate blocks production promotion while logging a reason.

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 require reviewed image provenance, admission policy checks and staged traffic validation before promoting a cloud-native application. Its confirming test is to insert a deliberately unsigned test image into staging and confirm the release gate blocks production promotion while logging a reason.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests