A root-cellar tour chart is live. One board shows pod readiness and reply delay; another asks “is the voice a real steward?” Which board is Domain 6?
Select an answer to reveal the explanation.
Short Explanation
Domain 6 watches whether pods are ready and how long replies take. “Does this sound like a real steward?” is a trust question for another domain—do not confuse the dashboards.
Full Explanation
On a root-cellar tour with one board showing pod readiness and reply delay and another asking “is the voice a real steward?”, the Domain 6 board is the one with pod readiness and reply delay—scale metrics, not a trust or authenticity rubric.
Treating the authenticity question board as the Domain 6 metric fails: that is Domain 7 trust territory. Claiming neither board counts because Domain 6 only measures CUDA kernel occupancy fails the associate Helm/scale focus. Claiming only authenticity reviews count and latency dashboards belong to Domain 3 fails domain assignment for performance metrics.
Exam caveat: Domain 6 watches readiness, latency, throughput, replicas. Authenticity of voice is Domain 7 even when both boards hang in the same parlor.
Operational check: wire pod-ready and reply-delay panels to the civic ops channel; route “real steward?” questions to the trust/authenticity checklist; keep the boards labeled by domain in the tour script. In municipal platform operations, record the chosen performance lever and the rejected alternatives in the change record so future on-call engineers understand the failure modes avoided for citizen services. Re-check the decision after the next traffic spike or model update to ensure the same answer still holds for the city's estate.