Skip to main content
🔒 Preview mode. The first 15 Foundations lessons are free; this one is Pro. Start a 7-day trial to unlock the editor, AI hints and the rest of the curriculum. Card required, cancel any time in Dashboard.
Start 7-day trial →
⚡
← Courses
›
DevOps for Python services
›
Module 5 · Cloud, IaC, Secrets, Cost · Recap
›
Secrets in K8s: never as env vars
quiz
98 / 104
🇺🇸
EN
▼
↗
Share
⋯
More
+100 XP
📋
Task
📖
Theory
🤖
AI Help
Task
📝 **Question:** Right way to handle DB password in K8s? 📋 Pick the right answer. 💡 **Hint:** Re-read the theory above if unsure.
🎯 Quiz
Question
📝 **Question:** Right way to handle DB password in K8s? 📋 Pick the right answer. 💡 **Hint:** Re-read the theory above if unsure.
A
Inject via env var from a native `Secret` — base64 encoding is the recommended at-rest protection by the K8s docs.
B
External Secrets Operator pulling from Vault, mounted as a file at runtime; KMS-encrypted at rest.
C
Hard-code the password into the Deployment YAML — encrypted Git history protects it as long as the repo stays private.
D
Stuff the password into a `ConfigMap` — ConfigMaps and Secrets behave identically in modern Kubernetes since 1.27.
Submit answer
💬 Discussion
Be the first to ask a question or share a tip.
Sign in
to join the discussion. Reading is free.
Loading discussion…