How many Troubleshooting Scenario Questions questions are on this page?

This page has 5 Troubleshooting Scenario Questions scenario questions for the PCA exam, each with detailed explanations and wrong-answer analysis.

How should I approach PCA scenario questions?

Read the full scenario before looking at the answer options. Identify the constraint or requirement in the scenario, then eliminate options that are generally true but wrong for this specific case. Scenario questions reward careful reading over pattern matching.

← Back to Prometheus Certified Associate (PCA, CNCF/Linux Foundation) (PCA) questions

Scenario-based practice

Troubleshooting Scenario Questions

Practise Prometheus Certified Associate (PCA, CNCF/Linux Foundation) (PCA) practice questions — original exam-style scenarios covering every exam domain, with detailed explanations, wrong-answer analysis, and common exam traps.

Start full practice test Read exam guide

scenario questions

PCA

exam code

CNCF / Linux Foundation

vendor

Scenario guide

How to approach troubleshooting scenario questions

These questions describe a network symptom and ask you to identify the root cause or the correct fix. They appear across all certification exams and reward systematic thinking over memorisation. The best candidates follow a consistent troubleshooting framework even under time pressure.

Quick answer

Troubleshooting Scenario Questions questions test whether you can apply the concept in context, not just recognise a definition.

How the topic appears in realistic exam-style scenarios.

Which detail in the question changes the correct answer.

How to eliminate plausible but wrong options.

How to connect the question back to the wider exam objective.

Practice scenarios

Question 1mediummultiple choice

Full question →

You are troubleshooting high cardinality in your metrics. What is a common cause for this in a custom exporter?

A
Using too many different metrics.
Why wrong: While having many metrics impacts memory, cardinality is driven by label value combinations.
B
Scraping the exporter too frequently.
Why wrong: Frequent scraping affects performance but does not create high cardinality.
C
Using the wrong metric type for a simple count.
Why wrong: Choosing a gauge instead of a counter does not impact cardinality.
D
Including dynamic values like IDs or timestamps in label values.
Including unique identifiers as labels creates a new time series for every single value, leading to cardinality explosion.

Full breakdown with real-world context →

Question 2hardmultiple choice

Full question →

You have a recording rule that fails to evaluate because of a 'labels conflict'. What is the most likely cause?

A
The aggregation results in duplicate label sets
Prometheus requires unique labels for each time series; conflicts occur if the result isn't unique.
B
The rule file has invalid YAML indentation
Why wrong: This would cause a parse error.
C
The evaluation interval is too low
Why wrong: This would impact performance, not cause label conflicts.
D
The metric name is already in use
Why wrong: This usually leads to an error, but not necessarily a 'label conflict'.

Full breakdown with real-world context →

Question 3mediummultiple choice

Full question →

You are monitoring server hardware metrics using node_exporter. You observe that the metrics are not showing up in Prometheus. Which initial troubleshooting step is most effective?

A
Verify node_exporter is listening on the expected port and accessible.
Connectivity to the exporter endpoint is the first requirement for successful scraping.
B
Increase the scrape interval in the Prometheus configuration.
Why wrong: The scrape interval does not affect connectivity, only the frequency of data collection.
C
Disable all collectors in node_exporter to reduce overhead.
Why wrong: Disabling collectors would result in missing metrics, not connectivity.
D
Check if the Prometheus server is running in high availability mode.
Why wrong: Prometheus HA status does not affect the target's ability to expose metrics.

Full breakdown with real-world context →

Question 4hardmultiple choice

Full question →

A dashboard shows a latency spike that doesn't correlate with CPU usage. What should you investigate next?

A
Increase the number of replicas.
Why wrong: This is a reactive scaling action, not an investigation.
B
Disk I/O and network saturation.
These are common non-CPU bottlenecks.
C
Check the memory limit.
Why wrong: Memory limits rarely cause latency spikes unless swapping occurs.
D
Delete old metrics.
Why wrong: This is unrelated to latency.

Full breakdown with real-world context →

Question 5hardmultiple choice

Full question →

You are troubleshooting a query and notice that label_replace is being used. What is the primary function of label_replace(v, dst_label, replacement, src_label, regex)?

A
It renames the Prometheus server instance in federated environments.
Why wrong: Federation handles instance naming differently.
B
It drops all time series that do not contain the specified source label.
Why wrong: It does not drop series; it modifies label sets.
C
It matches a regex against a source label value and writes the result into a destination label.
Correct. label_replace modifies or creates labels based on regular expression extractions.
D
It replaces the metric name with a new string.
Why wrong: Metric names are stored in the special label __name__, but label_replace is generally used for arbitrary labels.

Full breakdown with real-world context →

These PCA practice questions are part of Courseiva's free CNCF / Linux Foundation certification practice question bank. Courseiva provides original exam-style PCA questions with detailed explanations, topic-based practice, mock exams, readiness tracking, and study analytics.

Troubleshooting Scenario Questions

How to approach troubleshooting scenario questions

Quick answer

Related PCA topic practice pages

Observability Concepts practice questions

Prometheus Fundamentals practice questions

Alerting And Dashboarding practice questions

Promql practice questions

Instrumentation And Exporters practice questions

PCA fundamentals practice questions

PCA scenario practice questions

PCA troubleshooting practice questions

Practice scenarios

You are troubleshooting high cardinality in your metrics. What is a common cause for this in a custom exporter?

You have a recording rule that fails to evaluate because of a 'labels conflict'. What is the most likely cause?

You are monitoring server hardware metrics using node_exporter. You observe that the metrics are not showing up in Prometheus. Which initial troubleshooting step is most effective?

A dashboard shows a latency spike that doesn't correlate with CPU usage. What should you investigate next?

You are troubleshooting a query and notice that label_replace is being used. What is the primary function of label_replace(v, dst_label, replacement, src_label, regex)?