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
›
Observability: Prometheus + Grafana
quiz
87 / 104
🇺🇸
EN
▼
↗
Share
⋯
More
+100 XP
📋
Task
📖
Theory
🤖
AI Help
Task
📝 **Question:** Why pull-based (Prometheus scrapes) vs push? 📋 Pick the right answer. 💡 **Hint:** Re-read the theory above if unsure.
🎯 Quiz
Question
📝 **Question:** Why pull-based (Prometheus scrapes) vs push? 📋 Pick the right answer. 💡 **Hint:** Re-read the theory above if unsure.
A
Push is fine — StatsD-style UDP push scales further on Kubernetes than scrape-based service discovery does today.
B
Pull = central control, easy service discovery in K8s; push fits short-lived jobs (use Pushgateway).
C
Required by OpenMetrics — the spec mandates pull semantics so federated Prom servers can rebuild lost samples.
D
Pull is strictly slower than push because each scrape opens a new TCP connection and traverses the kube-proxy IPVS table.
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…