Question 150
While investigating a telemetry quality investigation for fictional Sable Valley Power, the team reports: A time-series database stores each raw API request ID as a permanent metric label, causing explosive series cardinality. Which engineering principle explains the described system behavior?
Explanation
Correct Answer
Time-series cardinality grows with combinations of labels; volatile unique IDs defeat aggregation and strain metric storage. The corresponding repair is: Normalize telemetry dimensions to stable device and interface identifiers and avoid high-cardinality ephemeral labels. Acceptance should show: The series count remains bounded while operators can still filter reliably by site, device and interface.
Incorrect Answers
The offered statement is true for this other mechanism: The corresponding repair is: Trace correlated event IDs and earliest causal errors through the pipeline instead of treating the final propagated exception as root cause. It does not explain the facts described here, which follow from: The corresponding repair is: Normalize telemetry dimensions to stable device and interface identifiers and avoid high-cardinality ephemeral labels.
This principle describes a separate cause: The corresponding repair is: Generate and store private keys in restricted secret systems and deploy only to the authorized TLS termination endpoint. The reported condition is governed by: The corresponding repair is: Normalize telemetry dimensions to stable device and interface identifiers and avoid high-cardinality ephemeral labels. The two mechanisms should not be conflated.
The corresponding repair is: Classify authentication failures and authorization denials separately, then correct token validity or RBAC scope accordingly. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Normalize telemetry dimensions to stable device and interface identifiers and avoid high-cardinality ephemeral labels.