Browse Linux Foundation and CNCF Guides

Linux Foundation PCA Cheat Sheet: Metrics, Alerts, and Dashboards

April 24, 2026

Linux Foundation PCA cheat sheet for metrics, alerts, dashboards, traps, and final review.

On this page

Use this cheat sheet for Prometheus Certified Associate (PCA) after you know the basics but before you start a timed practice block. The goal is not to memorize a vendor catalog; the goal is to classify the scenario and reject attractive wrong answers quickly.

PCA answer sequence

Use this when the stem mixes metrics, query shape, scrape behavior, alerting, or retention.

    flowchart TD
	  S["Scenario"] --> M["Classify the metrics lane"]
	  M --> Q["Check PromQL or metric shape"]
	  Q --> S2["Check scraping, discovery, or alerting"]
	  S2 --> V["Verify with evidence and retention fit"]

First-pass question triage

  1. Name the tested lane before reading the answer choices.
  2. Underline the constraint: security, cost, reliability, latency, governance, implementation effort, or evidence.
  3. Reject answers that solve a neighboring problem but not the stated requirement.
  4. Prefer the smallest correct control, service, workflow, or command that satisfies the constraint.
  5. Look for proof: logs, tests, metrics, policy evidence, deployment status, evaluation results, or user-visible recovery.

What to know cold

Lane Decision rule Reject when
Metrics model Understand time series, labels, samples, counters, gauges, histograms, and cardinality. Using labels that explode cardinality or make queries unmanageable.
PromQL Filter, aggregate, rate, join, and reason about ranges and instant vectors. Using raw counters instead of rate or increase for time-window behavior.
Scraping and service discovery Configure targets, jobs, exporters, relabeling, and Kubernetes discovery. Assuming a metric is missing when the scrape target is down or relabeled away.
Alerting Build useful alert rules, thresholds, for durations, labels, routing, and silencing. Alerting on noisy symptoms without runbook or ownership.
Operations Understand retention, storage, federation, remote write, HA patterns, and dashboard usage. Treating Prometheus as long-term storage without considering retention and scale.

Common traps and better instincts

Trap Better instinct
High-cardinality labels Avoid user IDs, request IDs, and unbounded labels in metrics.
Wrong counter query Use rate or increase over a range for counters.
No alert context Include labels, annotations, severity, route, and runbook intent.
Target discovery blind spots Check scrape config, service discovery, relabeling, and target health.

Final 15-minute review

If the stem says Start with
least privilege, private access, compliance, or audit identity scope, data boundary, policy enforcement, logging, and ownership
least operational effort managed service, native integration, simple workflow, and fewer moving parts
high availability, recovery, or outage failure domain, recovery objective, health check, rollback, and validation
performance, scale, or cost bottleneck evidence, traffic pattern, sizing, caching, batching, and quotas
troubleshoot, diagnose, or investigate symptom, recent change, logs, metrics, status, dependency, and smallest safe test

Practice fit

Use IT Mastery for the exact product route, practice status, spaced review when available, and close-answer explanation practice as coverage expands.

Open the exact IT Mastery route here: PCA on MasteryExamPrep.

Decision order

Prometheus questions reward metric-shape discipline: label design, correct PromQL, target health, alert quality, and scale limits.

Revised on Sunday, May 10, 2026
Study Plan