- A
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
Run all namespaces on the same privileged worker nodes so scaling is easier.
Why wrong: 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
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
Store secrets as plain environment variables because container images are already isolated.
Why wrong: 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
Grant every service account cluster-admin so deployments fail less often.
Why wrong: 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.
Quick Answer
The correct answer is to apply network policies or microsegmentation and move production workloads to a separate cluster. This is because Kubernetes namespace isolation alone is insufficient for strong security boundaries—namespaces share the same control plane and node resources, meaning a staging compromise can easily lead to lateral movement toward production secrets. Network policies act as a software firewall between pods, restricting traffic so staging containers cannot reach production services, while separate clusters enforce physical or logical tenancy, eliminating the shared attack surface entirely. On the Security+ SY0-701 exam, this tests your understanding of defense-in-depth and the principle of least privilege in containerized environments; a common trap is assuming namespaces provide full isolation. Remember the mnemonic “Namespaces are for organization, not isolation”—always pair them with network policies or separate clusters for real security.
SY0-701 Security Architecture Practice Question
This SY0-701 practice question tests your understanding of security architecture. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
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
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Move production workloads into a separate cluster or dedicated node pool with stricter tenancy boundaries.
Option A is correct because moving production workloads to a separate cluster or dedicated node pool enforces stronger tenancy boundaries, preventing a compromise in staging from directly accessing production secrets or pods. Kubernetes namespaces alone do not provide strong isolation, as a single cluster shares the same control plane and node resources, making lateral movement possible. This architectural change reduces the attack surface by physically or logically separating production from staging and development environments.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Move production workloads into a separate cluster or dedicated node pool with stricter tenancy boundaries.
Why this is correct
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.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Run all namespaces on the same privileged worker nodes so scaling is easier.
Why it's wrong here
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.
- ✓
Apply network policies or microsegmentation so staging pods cannot talk freely to production services.
Why this is correct
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.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Store secrets as plain environment variables because container images are already isolated.
Why it's wrong here
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.
- ✗
Grant every service account cluster-admin so deployments fail less often.
Why it's wrong here
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 traps
Common exam trap: answer the scenario, not the keyword
CompTIA often tests the misconception that Kubernetes namespaces provide sufficient security isolation, but the trap here is that namespaces share the same control plane and node resources, so without separate clusters or node pools, a compromise in one namespace can lead to lateral movement to others.
Trap categories for this question
Scenario analysis trap
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.
Detailed technical explanation
How to think about this question
Kubernetes network policies (Option C) use label selectors and namespace selectors to control ingress/egress traffic at the CNI layer (e.g., Calico, Cilium), enforcing microsegmentation between staging and production pods. Under the hood, these policies translate to iptables or eBPF rules that filter traffic based on IP addresses and ports, preventing staging pods from reaching production services even if they are on the same cluster. In a real-world scenario, a compromised staging pod could attempt to access the production database endpoint; a network policy denying all traffic from staging namespaces to production namespaces blocks this at the network layer.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A SOC analyst notices unusual lateral movement in the network at 2 AM. The IR playbook dictates: identify and contain (isolate the affected machine), then eradicate (remove the malware), then recover (restore from backup), then document. Skipping containment before eradication risks the attacker regaining access. Questions like this test the sequence and rationale of incident response phases.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Security Architecture — study guide chapter
Learn the concepts, then practise the questions
- →
Security Architecture practice questions
Targeted practice on this topic area only
- →
All SY0-701 questions
1,152 questions across all exam domains
- →
Security+ SY0-701 study guide
Full concept coverage aligned to exam objectives
- →
SY0-701 practice test guide
How to use practice tests most effectively before exam day
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.
General Security Concepts practice questions
Practise SY0-701 questions linked to General Security Concepts.
Threats, Vulnerabilities, and Mitigations practice questions
Practise SY0-701 questions linked to Threats, Vulnerabilities, and Mitigations.
Security Architecture practice questions
Practise SY0-701 questions linked to Security Architecture.
Security Operations practice questions
Practise SY0-701 questions linked to Security Operations.
Security Program Management and Oversight practice questions
Practise SY0-701 questions linked to Security Program Management and Oversight.
Security+ social engineering questions
Practise SY0-701 questions linked to Security+ social engineering questions.
Security+ cryptography practice questions
Practise SY0-701 questions linked to Security+ cryptography.
Security+ IAM questions
Practise SY0-701 questions linked to Security+ IAM questions.
Security+ risk management questions
Practise SY0-701 questions linked to Security+ risk management questions.
Security+ incident response questions
Practise SY0-701 questions linked to Security+ incident response questions.
Security+ malware questions
Practise SY0-701 questions linked to Security+ malware questions.
Security+ vulnerability management questions
Practise SY0-701 questions linked to Security+ vulnerability management questions.
Practice this exam
Start a free SY0-701 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this SY0-701 question test?
Security Architecture — This question tests Security Architecture — Read the scenario before looking for a memorised answer..
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. — Option A is correct because moving production workloads to a separate cluster or dedicated node pool enforces stronger tenancy boundaries, preventing a compromise in staging from directly accessing production secrets or pods. Kubernetes namespaces alone do not provide strong isolation, as a single cluster shares the same control plane and node resources, making lateral movement possible. This architectural change reduces the attack surface by physically or logically separating production from staging and development environments.
What should I do if I get this SY0-701 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Keep practising
More SY0-701 practice questions
- An HR analyst must send a salary file to an external auditor. The auditor only needs names, departments, and salary tota…
- An investigator receives a suspect laptop drive that may be used in court. Which approach best supports a forensically s…
- An investigator must collect data from a suspected insider-threat laptop so the evidence could be used in an HR and lega…
- An NDR tool shows a production web server sending small, periodic DNS queries to random-looking subdomains under a domai…
- An investigator needs to make a forensic image of a suspect laptop without changing the original drive contents. Which t…
- An operations team manages Linux servers over SSH. The security team wants to stop direct management access from employe…
Last reviewed: Jun 30, 2026
This SY0-701 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SY0-701 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.