Reading mode Engineer Decision-maker
Decision-maker reading: bridges first.
Ten questions to check what you retain from the course. Each answer is corrected immediately, with an explanation and a link to the relevant lesson. Nothing is sent: your best score stays in this browser.
Question 1 of 10 According to the silent failure model, what is the right question to ask about a signal you do not measure? One answer Review: Part I: The framework
Question 2 of 10 A trusted MCP server changes the definition of one of its tools between two calls (rug pull). Which signal from the MCP grid makes this change visible? One answer Review: Part III: Measurement grid
Question 3 of 10 Which of these practices match how the method defines and monitors a quality SLO? Several answers possible Review: Part IV: Quality SLOs
Question 4 of 10 The agreement rate between your LLM judge and the golden set drops sharply. What should you conclude? One answer Review: Part IV: Quality SLOs
Question 5 of 10 Bridge: business To defend an observability budget in front of finance, how does the method estimate the value of a signal? One answer Review: Part V: Quantified impact
Question 6 of 10 Bridge: business In the worked example of part V (50,000 calls per day), what does an achievable 30 percent cache hit rate left unused represent? One answer About 9,600 calls per month 9,600 calls is the volume of a single runaway agent over one night (20 requests per minute for 8 hours).
About 1,800 million input tokens per month About 1,800 million input tokens is the cumulative overconsumption of prompt bloat over four months, not the cache.
About 450,000 avoidable calls per month, that is 30 percent of the base cost The missed saving is h times the base cost: 0.30 x 50,000 x 30 = 450,000 calls per month, to value with your own prices, with no alert at all.
Nothing, since no latency or error alert fires That is precisely the silent failure: no alert does not mean no loss.
Review: Part V: Quantified impact
Question 7 of 10 Bridge: organization In the method's RACI, who is accountable (A) for quality SLOs? One answer Review: Part VII: Organization
Question 8 of 10 Bridge: people Your team is setting up quality on-call. Which actions belong to the mitigation playbook described by the method? Several answers possible Review: Part VII: Organization
Question 9 of 10 Bridge: business lines Your compliance team asks how you demonstrate the security of your supply chain under NIS2. Which signal does the evidence matrix tie to this obligation? One answer Review: Part VI: Compliance
Question 10 of 10 Where and how should the content of exchanges (prompts, responses) be handled in telemetry, to avoid two costly anti-patterns? Several answers possible Put it in a metric label so dashboards can be filtered by prompt That is the high-cardinality pitfall (guide, 9.6, recalled in Part VIII): cardinality explodes and can bring down the metrics database.
Keep it out of metric labels, which stay limited to low cardinality dimensions (model, operation, error type), and, if its capture is enabled (opt-in), place it outside indexed span attributes (event or dedicated log), masked That is the fix for the high-cardinality pitfall, applied in the reference collector configuration; even once capture is enabled, the content stays outside indexed attributes and masked, following the capture rule (next option).
Do not capture it by default, redact it at the collector and, if it must be kept, store it externally encrypted with a reference on the span That is the content capture rule (guide, 9.3, and Part I): capture is opt-in and, in production, the OpenTelemetry GenAI conventions recommend storing content externally with a reference on the span.
Review: Part VIII: Anti-patterns
Start over
Revised on 4 October 2026: explanations of the questions on dashboards and content updated (pointers to chapter 9 of the guide, content capture rule aligned with the OpenTelemetry specification).
Bridges What this page changes beyond the technical team.
BusinessValue, cost, risk You can put a figure on a blind spot (accumulation rate times detection delay) and justify observability in euros in front of finance.
OrganizationWho decides, who owns You know who owns what: the RACI splits eight capabilities between platform, data science, security, product and compliance.
PeopleTeams, on-call, skills You know why quality on-call differs from classical SRE on-call and why its playbooks are written before the incident.
Business linesProduct, finance, risk, customer You can tie an AI Act, NIS2 or GDPR obligation to the telemetry signal that proves it. Why bridges matter →