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 6 · Modern DevOps Stack
›
Helm: charts, templates, releases
quiz
79 / 104
🇺🇸
EN
▼
↗
Share
⋯
More
+100 XP
📋
Task
📖
Theory
🤖
AI Help
Task
📝 **Question:** Why use Helm vs raw `kubectl apply`? 📋 Pick the right answer. 💡 **Hint:** Re-read the theory above if unsure.
🎯 Quiz
Question
📝 **Question:** Why use Helm vs raw `kubectl apply`? 📋 Pick the right answer. 💡 **Hint:** Re-read the theory above if unsure.
A
Helm renders templates server-side via the Tiller controller — values evaluation runs inside the K8s API.
B
Parameterized templates per environment, release history, atomic rollback, dependency management.
C
Helm is the only client that supports Server-Side Apply field ownership for shared CRD spec ownership.
D
Helm v3 ships an embedded etcd-like store that survives cluster wipes and re-applies manifests on restart.
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…