McAfee Secure

CNCF CKA Bundle

Exam Code: CKA

Exam Name Certified Kubernetes Administrator

Certification Provider: CNCF

Corresponding Certification: CKA

CNCF CKA Bundle $44.99
CKA Sample 1 CKA Sample 2 CKA Sample 3 CKA Sample 4 CKA Sample 5 CKA Sample 6 CKA Sample 7 CKA Sample 8 CKA Sample 9 CKA Sample 10

100% CNCF CKA Guaranteed Success With Testking Training Materials

Get Real CKA Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

  • Questions & Answers

    CKA Questions & Answers

    58 Questions & Answers

    The ultimate exam preparation tool, Questions & Answers mirrors the actual CKA exam while allowing you to hone and measure every aspect of your test-taking ability.

  • CKA Video Course

    CKA Training Course

    138 Video Lectures

    CKA Video Course is developed by CNCF Professionals to help you pass the CKA exam.

    Description

    This course will improve your knowledge and skills required to pass Certified Kubernetes Administrator exam.
  • Study Guide

    CKA Study Guide

    268 PDF Pages

    Developed by industry experts, this 268-page guide spells out in painstaking detail all of the information you need to ace CKA exam.

Certified Kubernetes Administrator (CKA) Practice Tests

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Total Cost: $194.97
Bundle Price: $149.98

Purchase Individually

  • Questions & Answers

    Questions & Answers

    58 Questions

    $124.99
  • CKA Video Course

    Training Course

    138 Video Lectures

    $39.99
  • Study Guide

    Study Guide

    268 PDF Pages

    $29.99

CNCF CKA Practice Test 50

Question 490

At Pinecrest logistics, in a sandbox Kubernetes cluster during a recovery tabletop exercise: Deployment dispatch-api in namespace fulfillment needs an internal ClusterIP Service dispatch-svc exposing port 9090 to container port 9000. Work only within the stated target and verify before declaring success. Which Kubernetes behavior best explains the required change or diagnosis?

  1. Gateway API separates infrastructure listener ownership from application route attachments and depends on controller support.
  2. A NodePort Service allocates a cluster-configured host port on each node while retaining its cluster IP routing.
  3. DNS resolution may fail when CoreDNS replicas are unhealthy even when the requested Service and Pod endpoints exist.
  4. A ClusterIP Service provides stable in-cluster virtual addressing and directs traffic to selected ready Pod endpoints.

Explanation

Correct Answer

D:

A ClusterIP Service provides stable in-cluster virtual addressing and directs traffic to selected ready Pod endpoints. This explains the stated condition. The corresponding action is: Run kubectl -n fulfillment expose deployment dispatch-api --name=dispatch-svc --type=ClusterIP --port=9090 --target-port=9000. The direct acceptance evidence is: Run kubectl -n fulfillment get service dispatch-svc and inspect its EndpointSlices and port mapping.

Incorrect Answers

A:

The offered statement is true for this other mechanism: Gateway API separates infrastructure listener ownership from application route attachments and depends on controller support. It does not explain the facts described here, which follow from: A ClusterIP Service provides stable in-cluster virtual addressing and directs traffic to selected ready Pod endpoints.

B:

This principle describes a separate cause: A NodePort Service allocates a cluster-configured host port on each node while retaining its cluster IP routing. The reported condition is governed by: A ClusterIP Service provides stable in-cluster virtual addressing and directs traffic to selected ready Pod endpoints. The two mechanisms should not be conflated.

C:

DNS resolution may fail when CoreDNS replicas are unhealthy even when the requested Service and Pod endpoints exist. That explanation applies to a different technical failure. Here the controlling principle is: A ClusterIP Service provides stable in-cluster virtual addressing and directs traffic to selected ready Pod endpoints.

Question 491

At Pinecrest logistics, in a sandbox Kubernetes cluster during a recovery tabletop exercise: Deployment dispatch-api in namespace fulfillment needs an internal ClusterIP Service dispatch-svc exposing port 9090 to container port 9000. Work only within the stated target and verify before declaring success. Which observation best verifies the requested outcome rather than an unrelated state?

  1. Run kubectl -n fulfillment get service dispatch-svc and inspect its EndpointSlices and port mapping.
  2. Run kubectl -n ledger get service invoice-svc -o wide and inspect the allocated node port and endpoints.
  3. Run an in-Pod nslookup dispatch-svc.fulfillment.svc.cluster.local and confirm name resolution under isolation.
  4. Run kubectl -n kube-system logs deployment/coredns --tail=50 and compare to an in-Pod resolution test.

Explanation

Correct Answer

A:

Run kubectl -n fulfillment get service dispatch-svc and inspect its EndpointSlices and port mapping. This validates the affected object or control path, rather than only showing a command completed. The underlying reason is: A ClusterIP Service provides stable in-cluster virtual addressing and directs traffic to selected ready Pod endpoints. The intended action is: Run kubectl -n fulfillment expose deployment dispatch-api --name=dispatch-svc --type=ClusterIP --port=9090 --target-port=9000.

Incorrect Answers

B:

The alternative verifies a different condition: A NodePort Service allocates a cluster-configured host port on each node while retaining its cluster IP routing. The current case instead depends on: A ClusterIP Service provides stable in-cluster virtual addressing and directs traffic to selected ready Pod endpoints. Confirm that “Run kubectl -n fulfillment get service dispatch-svc and inspect its EndpointSlices and port mapping”.

C:

That test belongs to another control with this basis: NetworkPolicy egress rules are additive and DNS lookup requires permitted traffic to the DNS server, not only a correct Service record. In the current case, the governing reason is: A ClusterIP Service provides stable in-cluster virtual addressing and directs traffic to selected ready Pod endpoints. The direct verification is “Run kubectl -n fulfillment get service dispatch-svc and inspect its EndpointSlices and port mapping”.

D:

This observation would test a different technical dependency: DNS resolution may fail when CoreDNS replicas are unhealthy even when the requested Service and Pod endpoints exist. The current issue is governed by: A ClusterIP Service provides stable in-cluster virtual addressing and directs traffic to selected ready Pod endpoints. Its decisive check is “Run kubectl -n fulfillment get service dispatch-svc and inspect its EndpointSlices and port mapping”.

Question 492

At Pinecrest logistics, in a sandbox Kubernetes cluster during a recovery tabletop exercise: Deployment dispatch-api in namespace fulfillment needs an internal ClusterIP Service dispatch-svc exposing port 9090 to container port 9000. Work only within the stated target and verify before declaring success. Which operational control most directly prevents this failure or configuration drift?

  1. Check exposed Service port mappings against actual container listeners and named ports before releases.
  2. Manage Service selectors and target ports alongside the Deployment labels and container listening port.
  3. Track TLS Secret renewal and enforce appropriate ingress-controller security policies.
  4. Treat cross-namespace route attachment and backend references as controlled trust boundaries.

Explanation

Correct Answer

B:

Manage Service selectors and target ports alongside the Deployment labels and container listening port. This reduces recurrence of the specific operational failure. It reinforces the action: Run kubectl -n fulfillment expose deployment dispatch-api --name=dispatch-svc --type=ClusterIP --port=9090 --target-port=9000. The relevant mechanism is: A ClusterIP Service provides stable in-cluster virtual addressing and directs traffic to selected ready Pod endpoints.

Incorrect Answers

A:

The suggested review tracks a different technical risk: The Service port is what clients connect to, while targetPort must reach the actual backend listener. Here the sustained control must address: A ClusterIP Service provides stable in-cluster virtual addressing and directs traffic to selected ready Pod endpoints. Choose “Manage Service selectors and target ports alongside the Deployment labels and container listening port”.

C:

This routine guards against another mechanism: Ingress TLS termination relies on a controller and a referenced TLS Secret; updating a Service alone does not install certificates. The recurring exposure in the current case is: A ClusterIP Service provides stable in-cluster virtual addressing and directs traffic to selected ready Pod endpoints. The matching preventive check is “Manage Service selectors and target ports alongside the Deployment labels and container listening port”.

D:

The suggested review tracks a different technical risk: Gateway API HTTPRoutes express matching and backend behavior while Gateway resources own compatible listeners. Here the sustained control must address: A ClusterIP Service provides stable in-cluster virtual addressing and directs traffic to selected ready Pod endpoints. Choose “Manage Service selectors and target ports alongside the Deployment labels and container listening port”.

Question 493

At Northstar finance, in an isolated training cluster during a scheduled maintenance rehearsal: A temporary lab Service invoice-svc for Deployment invoice-api in ledger needs access through an automatically allocated NodePort, not a public load balancer. Work only within the stated target and verify before declaring success. Which command or initial safe diagnostic step best addresses the stated lab task?

  1. Run kubectl -n ledger apply -f ./ingress/invoice-api-tls.yaml after checking secret type and host match.
  2. Run kubectl -n ledger port-forward service/invoice-svc 18080:80 in a temporary session.
  3. Run kubectl -n ledger apply -f ./policies/invoice-api-dns.yaml where egress grants UDP and TCP 53 to validated DNS destinations.
  4. Run kubectl -n ledger expose deployment invoice-api --name=invoice-svc --type=NodePort --port=80 --target-port=8080.

Explanation

Correct Answer

D:

Run kubectl -n ledger expose deployment invoice-api --name=invoice-svc --type=NodePort --port=80 --target-port=8080. This is the appropriate command-line action or first safe diagnostic. The technical reason is: A NodePort Service allocates a cluster-configured host port on each node while retaining its cluster IP routing. Validate the result with: Run kubectl -n ledger get service invoice-svc -o wide and inspect the allocated node port and endpoints. Execute changes only in an authorized disposable lab or after normal production change controls.

Incorrect Answers

A:

The offered action targets: Ingress TLS termination relies on a controller and a referenced TLS Secret; updating a Service alone does not install certificates. The case facts point instead to: A NodePort Service allocates a cluster-configured host port on each node while retaining its cluster IP routing. Implement “Run kubectl -n ledger expose deployment invoice-api --name=invoice-svc --type=NodePort --port=80 --target-port=8080” to address that specific condition.

B:

This alternative is a response to another technical cause: Port-forwarding creates a client-side tunnel to a selected backend and does not change the Service type or network exposure. The reported case instead depends on: A NodePort Service allocates a cluster-configured host port on each node while retaining its cluster IP routing. The action that directly addresses it is “Run kubectl -n ledger expose deployment invoice-api --name=invoice-svc --type=NodePort --port=80 --target-port=8080”.

C:

The proposed action belongs to the mechanism: NetworkPolicy egress rules are additive and DNS lookup requires permitted traffic to the DNS server, not only a correct Service record. Here the stated fault follows a different mechanism: A NodePort Service allocates a cluster-configured host port on each node while retaining its cluster IP routing. The corrective choice is “Run kubectl -n ledger expose deployment invoice-api --name=invoice-svc --type=NodePort --port=80 --target-port=8080”.

Question 494

At Northstar finance, in an isolated training cluster during a scheduled maintenance rehearsal: A temporary lab Service invoice-svc for Deployment invoice-api in ledger needs access through an automatically allocated NodePort, not a public load balancer. Work only within the stated target and verify before declaring success. Which Kubernetes behavior best explains the required change or diagnosis?

  1. A NodePort Service allocates a cluster-configured host port on each node while retaining its cluster IP routing.
  2. A ClusterIP Service provides stable in-cluster virtual addressing and directs traffic to selected ready Pod endpoints.
  3. The Service port is what clients connect to, while targetPort must reach the actual backend listener.
  4. A selecting NetworkPolicy with ingress isolation and no allow rules denies new ingress to selected Pods except protocol-specific policy behavior; it does not itself control egress.

Explanation

Correct Answer

A:

A NodePort Service allocates a cluster-configured host port on each node while retaining its cluster IP routing. This explains the stated condition. The corresponding action is: Run kubectl -n ledger expose deployment invoice-api --name=invoice-svc --type=NodePort --port=80 --target-port=8080. The direct acceptance evidence is: Run kubectl -n ledger get service invoice-svc -o wide and inspect the allocated node port and endpoints.

Incorrect Answers

B:

A ClusterIP Service provides stable in-cluster virtual addressing and directs traffic to selected ready Pod endpoints. That explanation applies to a different technical failure. Here the controlling principle is: A NodePort Service allocates a cluster-configured host port on each node while retaining its cluster IP routing.

C:

The offered statement is true for this other mechanism: The Service port is what clients connect to, while targetPort must reach the actual backend listener. It does not explain the facts described here, which follow from: A NodePort Service allocates a cluster-configured host port on each node while retaining its cluster IP routing.

D:

This principle describes a separate cause: A selecting NetworkPolicy with ingress isolation and no allow rules denies new ingress to selected Pods except protocol-specific policy behavior; it does not itself control egress. The reported condition is governed by: A NodePort Service allocates a cluster-configured host port on each node while retaining its cluster IP routing. The two mechanisms should not be conflated.

Question 495

At Northstar finance, in an isolated training cluster during a scheduled maintenance rehearsal: A temporary lab Service invoice-svc for Deployment invoice-api in ledger needs access through an automatically allocated NodePort, not a public load balancer. Work only within the stated target and verify before declaring success. Which observation best verifies the requested outcome rather than an unrelated state?

  1. Run kubectl -n ledger get gateway internal-gw -o yaml and inspect Accepted and Programmed conditions.
  2. Run kubectl -n ledger get service invoice-svc -o wide and inspect the allocated node port and endpoints.
  3. Run kubectl -n observability get service metrics-svc and inspect external address assignment plus ready EndpointSlices.
  4. Run kubectl -n ledger describe networkpolicy invoice-api-deny-egress and test expected blocked destinations.

Explanation

Correct Answer

B:

Run kubectl -n ledger get service invoice-svc -o wide and inspect the allocated node port and endpoints. This validates the affected object or control path, rather than only showing a command completed. The underlying reason is: A NodePort Service allocates a cluster-configured host port on each node while retaining its cluster IP routing. The intended action is: Run kubectl -n ledger expose deployment invoice-api --name=invoice-svc --type=NodePort --port=80 --target-port=8080.

Incorrect Answers

A:

The alternative verifies a different condition: Gateway API separates infrastructure listener ownership from application route attachments and depends on controller support. The current case instead depends on: A NodePort Service allocates a cluster-configured host port on each node while retaining its cluster IP routing. Confirm that “Run kubectl -n ledger get service invoice-svc -o wide and inspect the allocated node port and endpoints”.

C:

This observation would test a different technical dependency: LoadBalancer Services request external routing from a supported infrastructure controller; a bare cluster does not guarantee an external address. The current issue is governed by: A NodePort Service allocates a cluster-configured host port on each node while retaining its cluster IP routing. Its decisive check is “Run kubectl -n ledger get service invoice-svc -o wide and inspect the allocated node port and endpoints”.

D:

The alternative verifies a different condition: An egress-isolating NetworkPolicy can block Pod outbound connections; DNS and required dependencies need explicit allowances. The current case instead depends on: A NodePort Service allocates a cluster-configured host port on each node while retaining its cluster IP routing. Confirm that “Run kubectl -n ledger get service invoice-svc -o wide and inspect the allocated node port and endpoints”.

Question 496

At Northstar finance, in an isolated training cluster during a scheduled maintenance rehearsal: A temporary lab Service invoice-svc for Deployment invoice-api in ledger needs access through an automatically allocated NodePort, not a public load balancer. Work only within the stated target and verify before declaring success. Which operational control most directly prevents this failure or configuration drift?

  1. Include EndpointSlice and readiness checks in Service connectivity runbooks.
  2. Prefer short-lived diagnostic tunnels and avoid treating port-forward as a production ingress path.
  3. Limit NodePort exposure through network controls and remove temporary external test services.
  4. Include DNS as an explicit dependency when designing egress policies for isolated Pods.

Explanation

Correct Answer

C:

Limit NodePort exposure through network controls and remove temporary external test services. This reduces recurrence of the specific operational failure. It reinforces the action: Run kubectl -n ledger expose deployment invoice-api --name=invoice-svc --type=NodePort --port=80 --target-port=8080. The relevant mechanism is: A NodePort Service allocates a cluster-configured host port on each node while retaining its cluster IP routing.

Incorrect Answers

A:

That safeguard is relevant to: EndpointSlices represent Service backend addresses and readiness; Service existence alone does not prove endpoints exist. The current failure instead follows from: A NodePort Service allocates a cluster-configured host port on each node while retaining its cluster IP routing. Its prevention measure is “Limit NodePort exposure through network controls and remove temporary external test services”.

B:

This routine guards against another mechanism: Port-forwarding creates a client-side tunnel to a selected backend and does not change the Service type or network exposure. The recurring exposure in the current case is: A NodePort Service allocates a cluster-configured host port on each node while retaining its cluster IP routing. The matching preventive check is “Limit NodePort exposure through network controls and remove temporary external test services”.

D:

That safeguard is relevant to: NetworkPolicy egress rules are additive and DNS lookup requires permitted traffic to the DNS server, not only a correct Service record. The current failure instead follows from: A NodePort Service allocates a cluster-configured host port on each node while retaining its cluster IP routing. Its prevention measure is “Limit NodePort exposure through network controls and remove temporary external test services”.

Question 497

At Horizon observability, in a disposable simulated environment during a monitored release window: A temporary lab Service metrics-svc for Deployment metrics-api in observability needs access through an automatically allocated NodePort, not a public load balancer. Work only within the stated target and verify before declaring success. Which command or initial safe diagnostic step best addresses the stated lab task?

  1. Run kubectl -n observability expose deployment metrics-api --name=metrics-svc --type=NodePort --port=8080 --target-port=3000.
  2. Run kubectl -n fulfillment expose deployment dispatch-api --name=dispatch-svc --type=LoadBalancer --port=9090 --target-port=9000.
  3. Run kubectl -n ledger expose deployment invoice-api --name=invoice-svc --type=ClusterIP --port=80 --target-port=8080.
  4. Run kubectl -n observability run metrics-api-dns-test --image=busybox:1.36 --restart=Never --command -- nslookup metrics-svc.observability.svc.cluster.local and inspect the Pod logs.

Explanation

Correct Answer

A:

Run kubectl -n observability expose deployment metrics-api --name=metrics-svc --type=NodePort --port=8080 --target-port=3000. This is the appropriate command-line action or first safe diagnostic. The technical reason is: A NodePort Service allocates a cluster-configured host port on each node while retaining its cluster IP routing. Validate the result with: Run kubectl -n observability get service metrics-svc -o wide and inspect the allocated node port and endpoints. Execute changes only in an authorized disposable lab or after normal production change controls.

Incorrect Answers

B:

The proposed action belongs to the mechanism: LoadBalancer Services request external routing from a supported infrastructure controller; a bare cluster does not guarantee an external address. Here the stated fault follows a different mechanism: A NodePort Service allocates a cluster-configured host port on each node while retaining its cluster IP routing. The corrective choice is “Run kubectl -n observability expose deployment metrics-api --name=metrics-svc --type=NodePort --port=8080 --target-port=3000”.

C:

The offered action targets: A ClusterIP Service provides stable in-cluster virtual addressing and directs traffic to selected ready Pod endpoints. The case facts point instead to: A NodePort Service allocates a cluster-configured host port on each node while retaining its cluster IP routing. Implement “Run kubectl -n observability expose deployment metrics-api --name=metrics-svc --type=NodePort --port=8080 --target-port=3000” to address that specific condition.

D:

This alternative is a response to another technical cause: Cluster DNS should resolve Service names inside its configured domain; host-side DNS results do not prove in-cluster resolution. The reported case instead depends on: A NodePort Service allocates a cluster-configured host port on each node while retaining its cluster IP routing. The action that directly addresses it is “Run kubectl -n observability expose deployment metrics-api --name=metrics-svc --type=NodePort --port=8080 --target-port=3000”.

Question 498

At Horizon observability, in a disposable simulated environment during a monitored release window: A temporary lab Service metrics-svc for Deployment metrics-api in observability needs access through an automatically allocated NodePort, not a public load balancer. Work only within the stated target and verify before declaring success. Which Kubernetes behavior best explains the required change or diagnosis?

  1. An ingress rule with a podSelector selects source Pods in its own namespace unless combined with other peer selectors.
  2. A NodePort Service allocates a cluster-configured host port on each node while retaining its cluster IP routing.
  3. Cluster DNS should resolve Service names inside its configured domain; host-side DNS results do not prove in-cluster resolution.
  4. Services select matching Pods; an unmatched selector can leave EndpointSlices without usable backends despite healthy Pods.

Explanation

Correct Answer

B:

A NodePort Service allocates a cluster-configured host port on each node while retaining its cluster IP routing. This explains the stated condition. The corresponding action is: Run kubectl -n observability expose deployment metrics-api --name=metrics-svc --type=NodePort --port=8080 --target-port=3000. The direct acceptance evidence is: Run kubectl -n observability get service metrics-svc -o wide and inspect the allocated node port and endpoints.

Incorrect Answers

A:

An ingress rule with a podSelector selects source Pods in its own namespace unless combined with other peer selectors. That explanation applies to a different technical failure. Here the controlling principle is: A NodePort Service allocates a cluster-configured host port on each node while retaining its cluster IP routing.

C:

This principle describes a separate cause: Cluster DNS should resolve Service names inside its configured domain; host-side DNS results do not prove in-cluster resolution. The reported condition is governed by: A NodePort Service allocates a cluster-configured host port on each node while retaining its cluster IP routing. The two mechanisms should not be conflated.

D:

Services select matching Pods; an unmatched selector can leave EndpointSlices without usable backends despite healthy Pods. That explanation applies to a different technical failure. Here the controlling principle is: A NodePort Service allocates a cluster-configured host port on each node while retaining its cluster IP routing.

Question 499

At Horizon observability, in a disposable simulated environment during a monitored release window: A temporary lab Service metrics-svc for Deployment metrics-api in observability needs access through an automatically allocated NodePort, not a public load balancer. Work only within the stated target and verify before declaring success. Which observation best verifies the requested outcome rather than an unrelated state?

  1. Run kubectl -n observability describe ingress metrics-ingress and test the route through the controller address using the expected Host header.
  2. Run kubectl -n observability get networkpolicy metrics-api-deny-ingress -o yaml and perform an authorized denied-connection probe.
  3. Run kubectl -n observability get service metrics-svc -o wide and inspect the allocated node port and endpoints.
  4. Compare listed endpoints against the matching ready Pods and expected selector for metrics-svc.

Explanation

Correct Answer

C:

Run kubectl -n observability get service metrics-svc -o wide and inspect the allocated node port and endpoints. This validates the affected object or control path, rather than only showing a command completed. The underlying reason is: A NodePort Service allocates a cluster-configured host port on each node while retaining its cluster IP routing. The intended action is: Run kubectl -n observability expose deployment metrics-api --name=metrics-svc --type=NodePort --port=8080 --target-port=3000.

Incorrect Answers

A:

That test belongs to another control with this basis: An Ingress resource declares HTTP host/path routing but requires an actual installed Ingress controller. In the current case, the governing reason is: A NodePort Service allocates a cluster-configured host port on each node while retaining its cluster IP routing. The direct verification is “Run kubectl -n observability get service metrics-svc -o wide and inspect the allocated node port and endpoints”.

B:

This observation would test a different technical dependency: A selecting NetworkPolicy with ingress isolation and no allow rules denies new ingress to selected Pods except protocol-specific policy behavior; it does not itself control egress. The current issue is governed by: A NodePort Service allocates a cluster-configured host port on each node while retaining its cluster IP routing. Its decisive check is “Run kubectl -n observability get service metrics-svc -o wide and inspect the allocated node port and endpoints”.

D:

That test belongs to another control with this basis: EndpointSlices represent Service backend addresses and readiness; Service existence alone does not prove endpoints exist. In the current case, the governing reason is: A NodePort Service allocates a cluster-configured host port on each node while retaining its cluster IP routing. The direct verification is “Run kubectl -n observability get service metrics-svc -o wide and inspect the allocated node port and endpoints”.

Question 500

At Horizon observability, in a disposable simulated environment during a monitored release window: A temporary lab Service metrics-svc for Deployment metrics-api in observability needs access through an automatically allocated NodePort, not a public load balancer. Work only within the stated target and verify before declaring success. Which operational control most directly prevents this failure or configuration drift?

  1. Manage Service selectors and target ports alongside the Deployment labels and container listening port.
  2. Prefer short-lived diagnostic tunnels and avoid treating port-forward as a production ingress path.
  3. Include DNS as an explicit dependency when designing egress policies for isolated Pods.
  4. Limit NodePort exposure through network controls and remove temporary external test services.

Explanation

Correct Answer

D:

Limit NodePort exposure through network controls and remove temporary external test services. This reduces recurrence of the specific operational failure. It reinforces the action: Run kubectl -n observability expose deployment metrics-api --name=metrics-svc --type=NodePort --port=8080 --target-port=3000. The relevant mechanism is: A NodePort Service allocates a cluster-configured host port on each node while retaining its cluster IP routing.

Incorrect Answers

A:

This routine guards against another mechanism: A ClusterIP Service provides stable in-cluster virtual addressing and directs traffic to selected ready Pod endpoints. The recurring exposure in the current case is: A NodePort Service allocates a cluster-configured host port on each node while retaining its cluster IP routing. The matching preventive check is “Limit NodePort exposure through network controls and remove temporary external test services”.

B:

The suggested review tracks a different technical risk: Port-forwarding creates a client-side tunnel to a selected backend and does not change the Service type or network exposure. Here the sustained control must address: A NodePort Service allocates a cluster-configured host port on each node while retaining its cluster IP routing. Choose “Limit NodePort exposure through network controls and remove temporary external test services”.

C:

That safeguard is relevant to: NetworkPolicy egress rules are additive and DNS lookup requires permitted traffic to the DNS server, not only a correct Service record. The current failure instead follows from: A NodePort Service allocates a cluster-configured host port on each node while retaining its cluster IP routing. Its prevention measure is “Limit NodePort exposure through network controls and remove temporary external test services”.