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
›
Istio / Linkerd: service mesh
quiz
86 / 104
🇺🇸
EN
▼
↗
Share
⋯
More
+100 XP
📋
Task
📖
Theory
🤖
AI Help
Task
📝 **Question:** When does service mesh pay off? 📋 Pick the right answer. 💡 **Hint:** Re-read the theory above if unsure.
🎯 Quiz
Question
📝 **Question:** When does service mesh pay off? 📋 Pick the right answer. 💡 **Hint:** Re-read the theory above if unsure.
A
Day 1 — adding the mesh before any services exist costs nothing and locks in mTLS hygiene from the start of the cluster.
B
When you have 20+ services AND need ≥3 of: mTLS, canaries, retries, per-service telemetry — and a dedicated platform team.
C
Once the cluster crosses 5 nodes — the per-sidecar memory cost stays under 50 MB at that scale and the L7 features start to matter.
D
Never — Linkerd and Istio both add latency and overhead; ambient mesh with eBPF is the only modern alternative worth running.
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…