Correct Answer: Pod Security Standards (PSS) with 'restricted' or 'baseline' profile
Pod Security Standards (enforced via Pod Security Admission) allow namespaces to be configured to require the 'baseline' or 'restricted' profiles, which automatically block pods th...
Correct Answer
Pod Security Standards (PSS) with 'restricted' or 'baseline' profile
Why This Answer Is Correct
Pod Security Standards (enforced via Pod Security Admission) allow namespaces to be configured to require the 'baseline' or 'restricted' profiles, which automatically block pods that run as root.
This question evaluates your knowledge of Kubernetes Security — a core concept tested in cloud certification exams. Understanding Kubernetes Security is essential for designing scalable, secure, and cost-effective cloud architectures. Mastery of this topic will help you answer scenario-based questions confidently on exam day.
To securely store and inject passwords, API keys, or certificates into a Pod, which Kubernetes resource should you use?
Which Kubernetes concept acts as an identity for processes that run in a Pod, giving them access to the Kubernetes API?
How can you restrict Pod communication so that 'frontend' pods can only talk to 'backend' pods on port 8080?
You are defining a ClusterRole in Kubernetes to grant read access to secrets. However, you want to ensure this role only applies to a specific Namespace rather than the entire cluster. How should you bind this role to a ServiceAccount?