Courseiva
Cloud Native Observability →mediumMultiple Choice

KCNA Cloud Native Observability Practice Question

Which of the following is true about Prometheus's pull-based model for collecting metrics?

⚠ Common exam trap

KCNA often tests the misconception that Prometheus receives pushed metrics; candidates confuse the pull model with push-based systems like StatsD or Graphite.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Prometheus scrapes metrics from HTTP endpoints

Prometheus uses a pull-based model where it periodically scrapes metrics from HTTP endpoints exposed by targets, typically at /metrics. This means targets do not push data; instead, Prometheus initiates the HTTP GET requests on a schedule defined by scrape_interval. This design simplifies target discovery and allows Prometheus to control scrape frequency and timeout.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✗

    Targets push metrics to Prometheus

    Why it's wrong here

    Prometheus actively scrapes configured targets over HTTP at set intervals; targets expose metrics but do not push them. It is tempting because push-based collection is common in monitoring agents, and would be correct for short-lived jobs that cannot be scraped reliably.

  • ✗

    Prometheus only collects metrics from Kubernetes API server

    Why it's wrong here

    Prometheus scrapes any HTTP endpoint exposing metrics, including node exporters, applications and custom jobs across many environments, not just the Kubernetes API server. It is tempting because Kubernetes service discovery is a common Prometheus use case, but that is one target among many, not the model's scope.

  • ✓

    Prometheus scrapes metrics from HTTP endpoints

    Why this is correct

    Prometheus actively initiates scrapes against configured HTTP endpoints, retrieving metrics at fixed intervals. This pull architecture satisfies the stem's requirement by having the server discover and fetch data itself, rather than passively receiving pushed measurements. Targets expose a `/metrics` path that Prometheus polls, giving it control over collection timing and target health.

  • ✗

    Prometheus stores metrics in a relational database

    Why it's wrong here

    Prometheus stores samples in its own time-series database using a custom TSDB format, not a relational database. It is tempting because relational databases are the familiar default for storing structured data, and would be correct for systems requiring SQL queries and transactional integrity.

About these practice questions

Courseiva writes every KCNA question from scratch — 930 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written and reviewed by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

Last reviewed September 2026 · checked against the official CNCF exam blueprint

This KCNA practice question is part of Courseiva's free CNCF certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the KCNA exam.