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 9

Question 80

A financial cooperative asks whether a billing API and a separately scalable reporting job should share one Pod. Which implementation together with matching acceptance evidence best meets this case?

  1. Use container runtime namespaces to isolate views of processes and networks while using cgroups to account for and constrain resources. Acceptance evidence: In a training namespace inspect PID views and a controlled memory limit, noting which mechanism changes identity or resource behavior.
  2. Require approved image registries, signature or digest verification and patch ownership when admitting production container images. Acceptance evidence: Deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.
  3. Treat etcd as Kubernetes control-plane state storage and protect its snapshots, keys, and access separately from an application's database or PVC. Acceptance evidence: Inspect the cluster backup policy for etcd snapshots and separately restore synthetic application data from its own backup.
  4. Group tightly coupled containers that require the same Pod networking identity and optionally shared volumes into one Pod while keeping independently scalable services separate. Acceptance evidence: Deploy a test sidecar and main container, verify localhost communication and compare their shared Pod IP with a separate Pod.

Explanation

Correct Answer

D:

The situation is that a financial cooperative asks whether a billing API and a separately scalable reporting job should share one Pod. Group tightly coupled containers that require the same Pod networking identity and optionally shared volumes into one Pod while keeping independently scalable services separate. Acceptance evidence: Deploy a test sidecar and main container, verify localhost communication and compare their shared Pod IP with a separate Pod. This pairing is justified because containers in a Pod share a network namespace and IP address and can coordinate on localhost, while the Pod is scheduled as one unit.

Incorrect Answers

A:

This action and check address the distinct objective “Explain Linux namespaces and cgroups as distinct container isolation mechanisms” instead of the stated acceptance requirement. The matching action is to group tightly coupled containers that require the same Pod networking identity and optionally shared volumes into one Pod while keeping independently scalable services separate. Its confirming test is to deploy a test sidecar and main container, verify localhost communication and compare their shared Pod IP with a separate Pod.

B:

This action and check address the distinct objective “Use image provenance and policy controls without trusting mutable tags” instead of the stated acceptance requirement. The matching action is to group tightly coupled containers that require the same Pod networking identity and optionally shared volumes into one Pod while keeping independently scalable services separate. Its confirming test is to deploy a test sidecar and main container, verify localhost communication and compare their shared Pod IP with a separate Pod.

C:

This action and check address the distinct objective “Distinguish etcd persistence from running workload data” instead of the stated acceptance requirement. The matching action is to group tightly coupled containers that require the same Pod networking identity and optionally shared volumes into one Pod while keeping independently scalable services separate. Its confirming test is to deploy a test sidecar and main container, verify localhost communication and compare their shared Pod IP with a separate Pod.

Question 81

A grocery chain wants rolling releases of four customer-facing API replicas. Which Kubernetes or cloud-native implementation decision best solves the stated problem?

  1. Keep desired workload YAML in version control and use kubectl apply to reconcile supported object fields through the API.
  2. Use a Deployment for a replicated stateless application requiring rolling updates and replacement of failed Pods.
  3. Choose a CRI-compatible container runtime on worker nodes and investigate image and container creation separately from API scheduling.
  4. Inspect probe configuration, Pod Ready conditions and restart events to identify whether traffic eligibility or container execution is failing.

Explanation

Correct Answer

B:

Use a Deployment for a replicated stateless application requiring rolling updates and replacement of failed Pods. This resolves the issue because a Deployment owns ReplicaSets that manage matching Pods and supports declarative rollout history, unlike an independent Pod object. To verify, scale a test Deployment and inspect its ReplicaSet and owned Pods, then compare deleting a standalone Pod.

Incorrect Answers

A:

This option addresses the distinct objective “Apply resource manifests declaratively instead of depending on imperative drift”, not the immediate requirement. Declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management. For the stated case, a Deployment owns ReplicaSets that manage matching Pods and supports declarative rollout history, unlike an independent Pod object.

C:

This option addresses the distinct objective “Explain the container runtime interface without conflating it with the control plane”, not the immediate requirement. A supported runtime such as containerd executes container operations requested through kubelet using the Container Runtime Interface. For the stated case, a Deployment owns ReplicaSets that manage matching Pods and supports declarative rollout history, unlike an independent Pod object.

D:

This option addresses the distinct objective “Investigate readiness failures separately from liveness-related restarts”, not the immediate requirement. A failed readiness probe removes a Pod from ready Service endpoints, while failed liveness checks can restart a process; their operational consequences differ. For the stated case, a Deployment owns ReplicaSets that manage matching Pods and supports declarative rollout history, unlike an independent Pod object.

Question 82

A grocery chain wants rolling releases of four customer-facing API replicas. Which platform mechanism explains why the suitable approach works?

  1. A Deployment owns ReplicaSets that manage matching Pods and supports declarative rollout history, unlike an independent Pod object.
  2. A StorageClass defines how storage is provisioned and may use WaitForFirstConsumer to delay provisioning until scheduling requirements are known.
  3. The API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.
  4. The scheduler selects a suitable node for an unscheduled Pod; kubelet on that node uses the runtime to start and monitor containers.

Explanation

Correct Answer

A:

A Deployment owns ReplicaSets that manage matching Pods and supports declarative rollout history, unlike an independent Pod object. It supports this action: Use a Deployment for a replicated stateless application requiring rolling updates and replacement of failed Pods. To confirm, scale a test Deployment and inspect its ReplicaSet and owned Pods, then compare deleting a standalone Pod.

Incorrect Answers

B:

That statement explains the distinct objective “Use StorageClass for dynamic volume provisioning rather than handcrafting every disk” rather than the cause in this case. The deciding mechanism here is that a Deployment owns ReplicaSets that manage matching Pods and supports declarative rollout history, unlike an independent Pod object.

C:

That statement explains the distinct objective “Explain desired state versus observed status in Kubernetes objects” rather than the cause in this case. The deciding mechanism here is that a Deployment owns ReplicaSets that manage matching Pods and supports declarative rollout history, unlike an independent Pod object.

D:

That statement explains the distinct objective “Separate kube-scheduler decisions from kubelet execution” rather than the cause in this case. The deciding mechanism here is that a Deployment owns ReplicaSets that manage matching Pods and supports declarative rollout history, unlike an independent Pod object.

Question 83

A grocery chain wants rolling releases of four customer-facing API replicas. Which controlled observation would best validate the intended improvement?

  1. Scale a test Deployment and inspect its ReplicaSet and owned Pods, then compare deleting a standalone Pod.
  2. Run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.
  3. Create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.
  4. Send a synthetic request with a correlation ID and confirm it appears in the trace and relevant logs while latency metrics change.

Explanation

Correct Answer

A:

Scale a test Deployment and inspect its ReplicaSet and owned Pods, then compare deleting a standalone Pod. This is the relevant test because a Deployment owns ReplicaSets that manage matching Pods and supports declarative rollout history, unlike an independent Pod object.

Incorrect Answers

B:

This check would help evaluate the distinct objective “Interpret ReplicaSet ownership and selectors in a Deployment”, but not the required result. For this case, scale a test Deployment and inspect its ReplicaSet and owned Pods, then compare deleting a standalone Pod.

C:

This check would help evaluate the distinct objective “Distinguish memory limits from CPU throttling for scheduling and runtime symptoms”, but not the required result. For this case, scale a test Deployment and inspect its ReplicaSet and owned Pods, then compare deleting a standalone Pod.

D:

This check would help evaluate the distinct objective “Explain metrics, logs and traces as complementary observability signals”, but not the required result. For this case, scale a test Deployment and inspect its ReplicaSet and owned Pods, then compare deleting a standalone Pod.

Question 84

A grocery chain wants rolling releases of four customer-facing API replicas. An engineer proposes: “Create three unowned Pods and assume Kubernetes will preserve their collective replica count during updates.” What adverse outcome would be most direct?

  1. Controllers may fail to recognize intended Pods or adopt unwanted matches, producing confusing replacement behavior.
  2. The claim remains Pending and dependent Pods cannot mount the missing volume.
  3. Availability and rollout behavior diverge because no workload controller owns the independent Pods.
  4. The container may enter a restart loop before completing initialization, prolonging unavailability.

Explanation

Correct Answer

C:

Availability and rollout behavior diverge because no workload controller owns the independent Pods. The shortcut creates this risk because a Deployment owns ReplicaSets that manage matching Pods and supports declarative rollout history, unlike an independent Pod object.

Incorrect Answers

A:

That outcome concerns the distinct objective “Interpret ReplicaSet ownership and selectors in a Deployment”; it is not the most direct consequence of this shortcut. The relevant consequence is that availability and rollout behavior diverge because no workload controller owns the independent Pods.

B:

That outcome concerns the distinct objective “Use StorageClass for dynamic volume provisioning rather than handcrafting every disk”; it is not the most direct consequence of this shortcut. The relevant consequence is that availability and rollout behavior diverge because no workload controller owns the independent Pods.

D:

That outcome concerns the distinct objective “Understand readiness, liveness and startup probes as different signals”; it is not the most direct consequence of this shortcut. The relevant consequence is that availability and rollout behavior diverge because no workload controller owns the independent Pods.

Question 85

A grocery chain wants rolling releases of four customer-facing API replicas. What pair of supported action and practical verification should be approved?

  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. 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.
  3. Use a Deployment for a replicated stateless application requiring rolling updates and replacement of failed Pods. Acceptance evidence: Scale a test Deployment and inspect its ReplicaSet and owned Pods, then compare deleting a standalone Pod.
  4. Treat etcd as Kubernetes control-plane state storage and protect its snapshots, keys, and access separately from an application's database or PVC. Acceptance evidence: Inspect the cluster backup policy for etcd snapshots and separately restore synthetic application data from its own backup.

Explanation

Correct Answer

C:

Use a Deployment for a replicated stateless application requiring rolling updates and replacement of failed Pods. Acceptance evidence: Scale a test Deployment and inspect its ReplicaSet and owned Pods, then compare deleting a standalone Pod. This pairing is justified because a Deployment owns ReplicaSets that manage matching Pods and supports declarative rollout history, unlike an independent Pod object.

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 use a Deployment for a replicated stateless application requiring rolling updates and replacement of failed Pods. Its confirming test is to scale a test Deployment and inspect its ReplicaSet and owned Pods, then compare deleting a standalone Pod.

B:

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 use a Deployment for a replicated stateless application requiring rolling updates and replacement of failed Pods. Its confirming test is to scale a test Deployment and inspect its ReplicaSet and owned Pods, then compare deleting a standalone Pod.

D:

This action and check address the distinct objective “Distinguish etcd persistence from running workload data” instead of the stated acceptance requirement. The matching action is to use a Deployment for a replicated stateless application requiring rolling updates and replacement of failed Pods. Its confirming test is to scale a test Deployment and inspect its ReplicaSet and owned Pods, then compare deleting a standalone Pod.

Question 86

A university deploys several bare Pods and wonders why no replacement is created after one is deleted. 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. Run a logging or node monitoring agent as a DaemonSet when every eligible worker needs its own instance.
  3. Choose a CRI-compatible container runtime on worker nodes and investigate image and container creation separately from API scheduling.
  4. Use a Deployment for a replicated stateless application requiring rolling updates and replacement of failed Pods.

Explanation

Correct Answer

D:

The situation is that a university deploys several bare Pods and wonders why no replacement is created after one is deleted. Use a Deployment for a replicated stateless application requiring rolling updates and replacement of failed Pods. This resolves the issue because a Deployment owns ReplicaSets that manage matching Pods and supports declarative rollout history, unlike an independent Pod object. To verify, scale a test Deployment and inspect its ReplicaSet and owned Pods, then compare deleting a standalone Pod.

Incorrect Answers

A:

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

B:

This option addresses the distinct objective “Select DaemonSet for node-local agents rather than Deployment replica counts”, not the immediate requirement. A DaemonSet controller targets eligible nodes for a Pod each, adapting to node additions and labels rather than maintaining a global arbitrary replica count. For the stated case, a Deployment owns ReplicaSets that manage matching Pods and supports declarative rollout history, unlike an independent Pod object.

C:

The situation is that a university deploys several bare Pods and wonders why no replacement is created after one is deleted. This option addresses the distinct objective “Explain the container runtime interface without conflating it with the control plane”, not the immediate requirement. A supported runtime such as containerd executes container operations requested through kubelet using the Container Runtime Interface. For the stated case, a Deployment owns ReplicaSets that manage matching Pods and supports declarative rollout history, unlike an independent Pod object.

Question 87

A university deploys several bare Pods and wonders why no replacement is created after one is deleted. What infrastructure principle makes the correct treatment effective?

  1. Under pressure, a higher-priority pending Pod may preempt eligible lower-priority Pods, but constraints and eviction rules still apply.
  2. A Deployment owns ReplicaSets that manage matching Pods and supports declarative rollout history, unlike an independent Pod object.
  3. The scheduler selects a suitable node for an unscheduled Pod; kubelet on that node uses the runtime to start and monitor containers.
  4. A PV reclaim policy controls how underlying storage is treated after claim release; deleting the Pod and deleting the PVC are distinct events with different effects.

Explanation

Correct Answer

B:

The situation is that a university deploys several bare Pods and wonders why no replacement is created after one is deleted. A Deployment owns ReplicaSets that manage matching Pods and supports declarative rollout history, unlike an independent Pod object. It supports this action: Use a Deployment for a replicated stateless application requiring rolling updates and replacement of failed Pods. To confirm, scale a test Deployment and inspect its ReplicaSet and owned Pods, then compare deleting a standalone Pod.

Incorrect Answers

A:

That statement explains the distinct objective “Use PriorityClasses and understand preemption without assuming they guarantee availability” rather than the cause in this case. The deciding mechanism here is that a Deployment owns ReplicaSets that manage matching Pods and supports declarative rollout history, unlike an independent Pod object.

C:

The situation is that a university deploys several bare Pods and wonders why no replacement is created after one is deleted. That statement explains the distinct objective “Separate kube-scheduler decisions from kubelet execution” rather than the cause in this case. The deciding mechanism here is that a Deployment owns ReplicaSets that manage matching Pods and supports declarative rollout history, unlike an independent Pod object.

D:

That statement explains the distinct objective “Compare PV reclaim policies and explain data retention on PVC deletion” rather than the cause in this case. The deciding mechanism here is that a Deployment owns ReplicaSets that manage matching Pods and supports declarative rollout history, unlike an independent Pod object.

Question 88

A university deploys several bare Pods and wonders why no replacement is created after one is deleted. What verification result would most convincingly distinguish a working solution from a claim?

  1. Label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.
  2. Scale a test Deployment and inspect its ReplicaSet and owned Pods, then compare deleting a standalone Pod.
  3. Deploy a test sidecar and main container, verify localhost communication and compare their shared Pod IP with a separate Pod.
  4. Test a synthetic standard API manifest and OpenTelemetry trace export across two platforms, documenting any unsupported extensions.

Explanation

Correct Answer

B:

The situation is that a university deploys several bare Pods and wonders why no replacement is created after one is deleted. Scale a test Deployment and inspect its ReplicaSet and owned Pods, then compare deleting a standalone Pod. This is the relevant test because a Deployment owns ReplicaSets that manage matching Pods and supports declarative rollout history, unlike an independent Pod object.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Use nodeSelector to place a workload on nodes with required labels”, but not the required result. For this case, scale a test Deployment and inspect its ReplicaSet and owned Pods, then compare deleting a standalone Pod.

C:

This check would help evaluate the distinct objective “Use Pods as the shared network and storage execution unit”, but not the required result. For this case, scale a test Deployment and inspect its ReplicaSet and owned Pods, then compare deleting a standalone Pod.

D:

This check would help evaluate the distinct objective “Understand open standards and vendor-neutral community collaboration”, but not the required result. For this case, scale a test Deployment and inspect its ReplicaSet and owned Pods, then compare deleting a standalone Pod.

Question 89

A university deploys several bare Pods and wonders why no replacement is created after one is deleted. The change review contains this proposal: “Create three unowned Pods and assume Kubernetes will preserve their collective replica count during updates.” What risk matters most?

  1. Availability and rollout behavior diverge because no workload controller owns the independent Pods.
  2. The image-pull issue stays unresolved because etcd is not the node component managing container starts.
  3. Credentials can leak through registries and the binaries cannot be compared as the same tested artifact.
  4. The service can remain under capacity because a standalone Pod has no ReplicaSet controller to recreate it.

Explanation

Correct Answer

A:

The situation is that a university deploys several bare Pods and wonders why no replacement is created after one is deleted. Availability and rollout behavior diverge because no workload controller owns the independent Pods. The shortcut creates this risk because a Deployment owns ReplicaSets that manage matching Pods and supports declarative rollout history, unlike an independent Pod object.

Incorrect Answers

B:

That outcome concerns the distinct objective “Recognize the kubelet role in local Pod lifecycle management”; it is not the most direct consequence of this shortcut. The relevant consequence is that availability and rollout behavior diverge because no workload controller owns the independent Pods.

C:

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 availability and rollout behavior diverge because no workload controller owns the independent Pods.

D:

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 availability and rollout behavior diverge because no workload controller owns the independent Pods.

Question 90

A university deploys several bare Pods and wonders why no replacement is created after one is deleted. Which implementation together with matching acceptance evidence best meets this case?

  1. Separate compile and runtime stages to retain only required binary and runtime dependencies in the deployed container image. Acceptance evidence: Compare SBOM and file inventory of the builder image with the published runtime stage and confirm the service still starts.
  2. Define a user-centered service level indicator and objective, such as percentage of successful requests within a latency threshold over a stated window. Acceptance evidence: Calculate a synthetic seven-day success ratio from request metrics and compare it to the agreed target before a risky rollout.
  3. Use a Deployment for a replicated stateless application requiring rolling updates and replacement of failed Pods. Acceptance evidence: Scale a test Deployment and inspect its ReplicaSet and owned Pods, then compare deleting a standalone Pod.
  4. Treat etcd as Kubernetes control-plane state storage and protect its snapshots, keys, and access separately from an application's database or PVC. Acceptance evidence: Inspect the cluster backup policy for etcd snapshots and separately restore synthetic application data from its own backup.

Explanation

Correct Answer

C:

The situation is that a university deploys several bare Pods and wonders why no replacement is created after one is deleted. Use a Deployment for a replicated stateless application requiring rolling updates and replacement of failed Pods. Acceptance evidence: Scale a test Deployment and inspect its ReplicaSet and owned Pods, then compare deleting a standalone Pod. This pairing is justified because a Deployment owns ReplicaSets that manage matching Pods and supports declarative rollout history, unlike an independent Pod object.

Incorrect Answers

A:

This action and check address the distinct objective “Build smaller images with multistage builds and remove unnecessary tooling” instead of the stated acceptance requirement. The matching action is to use a Deployment for a replicated stateless application requiring rolling updates and replacement of failed Pods. Its confirming test is to scale a test Deployment and inspect its ReplicaSet and owned Pods, then compare deleting a standalone Pod.

B:

This action and check address the distinct objective “Use SLI and SLO measures to focus reliability objectives” instead of the stated acceptance requirement. The matching action is to use a Deployment for a replicated stateless application requiring rolling updates and replacement of failed Pods. Its confirming test is to scale a test Deployment and inspect its ReplicaSet and owned Pods, then compare deleting a standalone Pod.

D:

The situation is that a university deploys several bare Pods and wonders why no replacement is created after one is deleted. This action and check address the distinct objective “Distinguish etcd persistence from running workload data” instead of the stated acceptance requirement. The matching action is to use a Deployment for a replicated stateless application requiring rolling updates and replacement of failed Pods. Its confirming test is to scale a test Deployment and inspect its ReplicaSet and owned Pods, then compare deleting a standalone Pod.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests