Question 500
A database team wants to prevent a recurrence of this issue: A team's on-call dashboard reports 100% database availability while many transactions fail due to recurring timeouts. Which preventive practice is most relevant?
Explanation
Correct Answer
Review SLO definitions with application owners after service architecture changes. The original failure arose from: The SLO is based only on instance uptime rather than successful application transactions. The control reduces that failure mode.
Incorrect Answers
This control would require peer approval and deletion safeguards for database resource plans; it responds to the risk in which database infrastructure Terraform plans delete the only production instance because its resource identifier changed. It would not address the current root cause: the SLO is based only on instance uptime rather than successful application transactions.
This would rehearse alert routing and owner turnover during operational readiness reviews. It is useful when a team deploys database monitoring alerts without an escalation owner and receives critical notifications in an unmonitored mailbox, but it does not prevent the issue here: the SLO is based only on instance uptime rather than successful application transactions.
The failure in the question arises because the SLO is based only on instance uptime rather than successful application transactions. A safeguard to measure backup and export impact as part of operating capacity planning serves situations where a company runs full database exports every hour and production query latency degrades during each export rather than this one.