hardmultiple choiceObjective-mapped

During an internal penetration test, a tester compromises a server that is part of a Kubernetes cluster. The tester has access to the node's operating system but not to the cluster's administrative credentials. Which of the following techniques would most likely allow the tester to escalate privileges to cluster-admin or access sensitive resources within the cluster?

Question 1hardmultiple choice
Full question →

During an internal penetration test, a tester compromises a server that is part of a Kubernetes cluster. The tester has access to the node's operating system but not to the cluster's administrative credentials. Which of the following techniques would most likely allow the tester to escalate privileges to cluster-admin or access sensitive resources within the cluster?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Best answer

Extracting a service account token from a running container and using it to access the Kubernetes API

Service account tokens are mounted inside pods. By entering a container (e.g., via the container runtime), the tester can read the token and authenticate to the API server, potentially with elevated rights.

B

Distractor review

Exploiting a kernel vulnerability on the node to escape to the host and then compromise the Kubernetes API server

The tester already has access to the node OS. Exploiting a kernel vulnerability would give root on the node but does not directly provide cluster-admin privileges.

C

Distractor review

Searching for a kubeconfig file on the node that contains a cluster-admin token

While possible, kubeconfig files on nodes typically have limited or node-specific permissions, not full cluster-admin. This is less reliable than using a service account token.

D

Distractor review

Modifying a ConfigMap to inject a malicious pod that runs with elevated privileges

Modifying a ConfigMap requires API access. The tester does not have authentication to the API server yet.

Common exam trap

Common exam trap: authentication is not authorization

Logging in proves the user can authenticate. It does not automatically mean the user is allowed to enter privileged or configuration mode. Watch for AAA authorization, privilege level and command authorization details.

Technical deep dive

How to think about this question

This kind of question is testing the difference between identity and permission. A user may successfully log in to a router because authentication is working, but still fail to enter configuration mode because authorization is missing, misconfigured or mapped to a lower privilege level.

KKey Concepts to Remember

  • Authentication checks who the user is.
  • Authorization controls what the user is allowed to do after login.
  • Privilege levels affect access to EXEC and configuration commands.
  • AAA, TACACS+ and RADIUS can separate login success from command access.

TExam Day Tips

  • Do not assume successful login means full administrative access.
  • Look for words such as cannot enter configuration mode, privilege level, authorization or command access.
  • Separate login problems from permission problems before choosing the answer.

Related practice questions

Related PT0-002 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this PT0-002 question test?

Authentication checks who the user is.

What is the correct answer to this question?

The correct answer is: Extracting a service account token from a running container and using it to access the Kubernetes API — In Kubernetes, service account tokens are mounted into pods automatically. A tester on a node can access the kubelet API or retrieve tokens from running containers (e.g., via 'docker exec' or 'crictl exec') or from the node's filesystem under /var/lib/kubelet or /run/secrets. These tokens may have high privileges depending on the service account's RBAC bindings. The other options are incorrect: exploiting a node vulnerability is less direct; kubeconfig files on the node are often present but may not have admin rights; modifying configmaps via API requires authentication first.

What should I do if I get this PT0-002 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.