A state agency SLA for a shared municipal identity portal requires measurable monthly uptime and p99 API latency. Today the city only pages on host-down events. Which improvement best aligns monitoring to the SLA and KPIs?
Select an answer to reveal the explanation.
Short Explanation
An SLA without gauges is a promise you cannot prove. Wire uptime and p99 latency into CloudWatch so the identity portal’s scoreboard matches what the state agency actually wrote down.
Full Explanation
Professional architectures map SLAs to concrete SLIs and alerting. CloudWatch metrics, alarms, and dashboards should track availability and latency thresholds that mirror contractual KPIs for shared civic platforms. Disk-only views, static instance inventories, and annual questionnaires do not provide continuous evidence against uptime and latency commitments.