AI Observability Quiz

Answers and explanations appear as you take the quiz.

1. Which observability signal connects stages of a single request?
   • A dashboard theme
   • A trace
   • A model card
   • A weekly training report
2. A model call returns successfully but the user task is incomplete. What does transport health show?
   • That the output is factually supported
   • That the user’s goal was met
   • Only that the call returned, not that the requested task succeeded
   • That the tool action was authorized
3. Why correlate logs, traces, and metrics with stable request and version identifiers?
   • They prove internal model reasoning
   • They eliminate privacy review
   • They make every output reproducible
   • Together they help explain patterns and locate the affected release
4. Why avoid recording every prompt and response by default?
   • Telemetry can create a sensitive data store and should be minimized for its diagnostic purpose
   • Logs cannot store text
   • More logs always improve privacy
   • Prompts contain no user information
5. What should an actionable alert include?
   • Every event from every service
   • An owner, threshold, diagnostic context, and recovery procedure
   • Only a severity color
   • A prompt telling the model to explain itself
6. A model reports a chain of reasoning about a tool action. Is that an authoritative execution record?
   • Yes, if the explanation is detailed
   • Yes, if the answer is confident
   • No; use actual tool records, timestamps, and verified state changes
   • Only when the action succeeded
7. How can a team test whether its observability path works?
   • Wait for a major production incident
   • Check only that dashboards load
   • Ask an operator whether they remember seeing an alert
   • Induce a controlled failure and verify the expected signal and traceability
8. Which is a task-level measurement for a model application?
   • Evidence coverage or verified outcome
   • GPU model number
   • Count of log lines
   • The model’s answer length