Question 838 of 997
Minimize Microservice VulnerabilitieshardMultiple SelectObjective-mapped

Which Security Context Settings Reduce Microservice Vulnerabilities?

This CKS practice question tests your understanding of minimize microservice vulnerabilities. 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.

Which THREE of the following are recommended practices for minimizing microservice vulnerabilities related to container security?

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

Set securityContext.runAsNonRoot: true

Setting `securityContext.runAsNonRoot: true` forces the container to run with a user ID (UID) other than 0 (root). This is a critical defense-in-depth measure because if an attacker exploits a vulnerability in the application or runtime, they will not gain root privileges on the host, limiting the blast radius. It enforces the principle of least privilege at the container level, and Kubernetes will reject the pod if the container image attempts to run as root.

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.

  • Set securityContext.runAsNonRoot: true

    Why this is correct

    Prevents the container from running as root, reducing the impact of a compromise.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Drop all capabilities via securityContext.capabilities.drop: ["ALL"]

    Why this is correct

    Removes all Linux capabilities, following the principle of least privilege.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Set high CPU requests to ensure performance

    Why it's wrong here

    CPU requests do not impact security; they are for resource management.

  • Set securityContext.readOnlyRootFilesystem: true

    Why this is correct

    Prevents writing to the root filesystem, limiting the ability to modify binaries or write malicious files.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Expose secrets as environment variables for convenience

    Why it's wrong here

    Secrets in environment variables can be leaked via logs, /proc, or debug endpoints; prefer mounted volumes.

Common exam traps

Common exam trap: answer the scenario, not the keyword

Kubernetes CKS exams often test the misconception that resource limits (CPU/memory) are security controls, but they are only for resource isolation and DoS prevention, not for mitigating container escape or privilege escalation vulnerabilities.

Detailed technical explanation

How to think about this question

Under the hood, `runAsNonRoot: true` leverages the container runtime's user namespace support and the kernel's UID check to reject any container that attempts to start with UID 0. Dropping all capabilities via `capabilities.drop: ["ALL"]` removes all Linux capabilities (e.g., CAP_NET_RAW, CAP_SYS_ADMIN) from the container's bounding set, preventing even a non-root user from performing privileged operations like creating raw sockets or mounting filesystems. Setting `readOnlyRootFilesystem: true` mounts the container's root filesystem as read-only, which prevents attackers from writing malicious binaries or modifying configuration files even if they gain code execution, forcing all writes to explicitly mounted writable volumes.

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 junior network technician can log in to a core router but cannot reach the enable prompt or configuration mode. The AAA server is authenticating the login — but the authorisation policy only grants privilege level 1, not 15. Authentication (who you are) is working; authorisation (what you can do) is not.

Quick reference

AAA Protocol Comparison

ProtocolPort(s)EncryptionTransportPrimary Use
RADIUS1812 / 1813Password onlyUDPNetwork access control
TACACS+49Full packetTCPDevice administration
Diameter3868Full sessionTCP / SCTPCarrier / mobile networks
802.1XEAP-basedLayer 2Port-based access control

TACACS+ encrypts the entire packet; RADIUS only encrypts the password field — a key exam distinction.

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.

Related practice questions

Related CKS practice-question pages

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

Practice this exam

Start a free CKS 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 CKS question test?

Minimize Microservice Vulnerabilities — This question tests Minimize Microservice Vulnerabilities — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Set securityContext.runAsNonRoot: true — Setting `securityContext.runAsNonRoot: true` forces the container to run with a user ID (UID) other than 0 (root). This is a critical defense-in-depth measure because if an attacker exploits a vulnerability in the application or runtime, they will not gain root privileges on the host, limiting the blast radius. It enforces the principle of least privilege at the container level, and Kubernetes will reject the pod if the container image attempts to run as root.

What should I do if I get this CKS 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 →

How Courseiva writes practice questions · Editorial policy

Keep practising

More CKS practice questions

Last reviewed: Jul 4, 2026

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.

Loading comments…

Sign in to join the discussion.

This CKS practice question is part of Courseiva's free CNCF 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 CKS exam.