hardmulti selectObjective-mapped

A platform team runs production, staging, and developer containers on the same Kubernetes cluster. After a staging compromise, the team wants to reduce the chance of access to production secrets or lateral movement to other namespaces. Which two architecture changes are most effective? Select two.

Question 1hardmulti select
Full question →

A platform team runs production, staging, and developer containers on the same Kubernetes cluster. After a staging compromise, the team wants to reduce the chance of access to production secrets or lateral movement to other namespaces. Which two architecture changes are most effective? Select two.

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

Move production workloads into a separate cluster or dedicated node pool with stricter tenancy boundaries.

Separating production from less trusted workloads reduces the blast radius of a compromise and keeps sensitive workloads away from shared resources. A dedicated cluster or node pool also makes it easier to apply stricter controls, monitoring, and change management to production. This is an effective way to limit cross-environment impact.

B

Distractor review

Run all namespaces on the same privileged worker nodes so scaling is easier.

Sharing privileged workers across all environments makes compromise much more damaging and weakens separation between production and lower-trust workloads. Ease of scaling is not worth the increase in blast radius when the goal is to isolate production from staging and development risks.

C

Best answer

Apply network policies or microsegmentation so staging pods cannot talk freely to production services.

Network policies and microsegmentation limit east-west traffic inside the cluster, which directly addresses lateral movement between namespaces and services. If staging is compromised, the attacker should not be able to reach production APIs or secrets stores without explicit permission. This is a key control in shared orchestration platforms.

D

Distractor review

Store secrets as plain environment variables because container images are already isolated.

Environment variables are still visible to processes, debugging tools, and sometimes logs or crashes. They are not a strong secret boundary, especially in a shared cluster. Container isolation alone does not make plaintext secret storage acceptable when the scenario asks to reduce the chance of secret exposure.

E

Distractor review

Grant every service account cluster-admin so deployments fail less often.

Giving all service accounts cluster-admin destroys least privilege and makes any compromise immediately far more dangerous. It also makes it harder to trace which workload performed a sensitive action. Convenience cannot justify turning every service account into a full-privilege administrator.

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 SY0-701 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 SY0-701 question test?

Authentication checks who the user is.

What is the correct answer to this question?

The correct answer is: Move production workloads into a separate cluster or dedicated node pool with stricter tenancy boundaries. — The best defenses are environment separation and east-west traffic control. Keeping production on separate nodes or a separate cluster reduces the impact of a staging compromise, while network policies or microsegmentation prevent pods from moving laterally into production services. Together, these controls protect both workload trust boundaries and secrets associated with higher-value environments. Why others are wrong: Running everything on the same privileged nodes increases the blast radius and defeats the purpose of environment separation. Plain environment variables are not a strong secret store and can leak through inspection or logging. Cluster-admin for every service account is the opposite of least privilege and would make a minor compromise catastrophic.

What should I do if I get this SY0-701 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.