Practice Test Geeks(PCA) Prometheus Certified Associate Practice Test
← All PCA Flashcard Decks

PCA Exporters & Integrations Flashcards

6 cards from real PCA practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.

Read the first 6 PCA Exporters & Integrations flashcards as text

  1. Which HTTP path does a Prometheus-native instrumented application typically expose its metrics on?

    Answer: /metrics

    By convention, Prometheus-instrumented applications serve metrics at the `/metrics` HTTP path in the Prometheus text exposition format.

  2. What content type must a Prometheus metrics endpoint return for the text exposition format?

    Answer: text/plain; version=0.0.4

    The standard Prometheus text format requires the Content-Type header `text/plain; version=0.0.4; charset=utf-8` so scrapers can parse it correctly.

  3. Which exporter exposes metrics from a JMX-enabled Java application?

    Answer: jmx_exporter

    The `jmx_exporter` can run as a Java agent or standalone process, scraping JMX MBeans and exposing them in Prometheus format.

  4. What is the recommended approach for instrumenting a new Go application with Prometheus?

    Answer: Import the prometheus/client_golang library and register metrics with the default registry

    The official `prometheus/client_golang` library provides Counter, Gauge, Histogram, and Summary types that auto-register with the default registry and expose via an HTTP handler.

  5. What does the `--collector.disable-defaults` flag do when added to node_exporter?

    Answer: Disables all default metric collectors, requiring explicit --collector.X flags to enable each one

    Passing `--collector.disable-defaults` starts node_exporter with no collectors active; only collectors explicitly enabled via `--collector.` will run.

  6. Which node_exporter collector exposes filesystem usage metrics such as available bytes per mount point?

    Answer: filesystem

    The `filesystem` collector reads `/proc/mounts` and `statfs` syscalls to expose metrics like `node_filesystem_avail_bytes` per device and mount point.