- Split `scenarios/scenarios.json` into individual JSON files under `scenarios/data/` named `<scenario-id>.json` - Split `scenarios/bundles.json` into individual JSON files under `scenarios/bundles/` named `<bundle-id>.json` - Updated `backend/server.js` to dynamically load scenario and bundle files from their respective directories - Updated documentation in `scenarios/SCHEMA.md` and `README.md` to reflect the new repository layout and contributor workflow Signed-off-by: Abhinav Sinha <[email protected]>
34 lines
993 B
JSON
34 lines
993 B
JSON
{
|
|
"id": "cks-mcq-psp-replacement",
|
|
"title": "Pod Security Evolution",
|
|
"category": "Cluster Security",
|
|
"difficulty": "Easy",
|
|
"type": "mcq",
|
|
"weight": 2,
|
|
"description": "PodSecurityPolicies (PSP) were completely removed from Kubernetes in version 1.25. What is the built-in native replacement that enforces Pod Security Standards at the namespace level?",
|
|
"options": [
|
|
{
|
|
"id": "a",
|
|
"text": "NetworkPolicies"
|
|
},
|
|
{
|
|
"id": "b",
|
|
"text": "OPA Gatekeeper"
|
|
},
|
|
{
|
|
"id": "c",
|
|
"text": "Pod Security Admission (PSA)"
|
|
},
|
|
{
|
|
"id": "d",
|
|
"text": "AppArmor Profiles"
|
|
}
|
|
],
|
|
"correct_option": "c",
|
|
"explanation": "Pod Security Admission (PSA) is the built-in admission controller that evaluates Pods against the predefined Pod Security Standards (Privileged, Baseline, and Restricted) based on namespace labels.",
|
|
"hints": [],
|
|
"setup_commands": [],
|
|
"default_namespace": "default",
|
|
"teardown_commands": []
|
|
}
|