refactor(scenarios): split monolithic configuration into individual files

- 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]>
2026-06-15 07:52:47 +05:30
parent 2104c5fea6
commit 124e5276d4
94 changed files with 4256 additions and 4217 deletions
@@ -0,0 +1,39 @@
+{
+  "id": "dns-resolution-mcq",
+  "title": "Kubernetes DNS Resolution",
+  "category": "Services & Networking",
+  "difficulty": "Easy",
+  "type": "mcq",
+  "weight": 3,
+  "description": "## Kubernetes DNS Resolution\n\nA pod in namespace `frontend` needs to reach a service named `db-service` in namespace `backend`. Which DNS name correctly resolves to that service from within the cluster?",
+  "options": [
+    {
+      "id": "a",
+      "text": "`db-service`"
+    },
+    {
+      "id": "b",
+      "text": "`db-service.backend`"
+    },
+    {
+      "id": "c",
+      "text": "`db-service.backend.svc.cluster.local`"
+    },
+    {
+      "id": "d",
+      "text": "`backend.db-service.cluster.local`"
+    }
+  ],
+  "correct_option": "c",
+  "explanation": "The full Kubernetes DNS format is `<service>.<namespace>.svc.<cluster-domain>`. The default cluster domain is `cluster.local`, so the FQDN is `db-service.backend.svc.cluster.local`. When pods are in the **same namespace**, just `db-service` works. Across namespaces, you need at minimum `db-service.backend` (short form). Option C is the fully-qualified name that always works regardless of the caller's namespace.",
+  "hints": [
+    {
+      "title": "Kubernetes DNS format",
+      "body": "CoreDNS resolves: `<svc-name>.<namespace>.svc.cluster.local`. You can verify with: `kubectl exec <pod> -- nslookup <service-name>`.",
+      "command": "kubectl exec -it <pod-name> -- nslookup db-service.backend.svc.cluster.local"
+    }
+  ],
+  "setup_commands": [],
+  "default_namespace": "default",
+  "teardown_commands": []
+}