Bird
0
0

Why does the 'restricted' Pod Security Standard forbid running containers as root user by default?

hard📝 Conceptual Q10 of 15
Kubernetes - RBAC and Security
Why does the 'restricted' Pod Security Standard forbid running containers as root user by default?
ARoot user containers cannot access network resources
BRoot user containers consume more CPU resources
CRunning as root is required only for privileged pods
DRunning as root increases the risk of privilege escalation attacks
Step-by-Step Solution
Solution:
  1. Step 1: Understand security risks of root user containers

    Containers running as root have elevated privileges, increasing risk of attacks.
  2. Step 2: Explain why restricted forbids root

    Restricted policy forbids root to reduce privilege escalation and improve security.
  3. Final Answer:

    Running as root increases the risk of privilege escalation attacks -> Option D
  4. Quick Check:

    Restricted forbids root to prevent privilege escalation [OK]
Quick Trick: Root user containers risk privilege escalation, so restricted forbids them [OK]
Common Mistakes:
  • Thinking root containers use more CPU
  • Believing root containers lack network access
  • Assuming root is only for privileged pods

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes