City IT announces a Sunday maintenance window for the assessor site and wants that planned downtime excluded from monthly availability. What service-level practice applies?
Select an answer to reveal the explanation.
Short Explanation
Announced maintenance windows are scheduled pit stops that availability math can exclude when policy says so. Counting them as surprise outages—or hiding the notice—misleads citizens and reports.
Full Explanation
Service-level policies commonly exclude announced, scheduled maintenance from availability calculations when the window is published and within agreed rules. City IT announcing a Sunday maintenance window for the assessor site and wanting that planned downtime excluded from monthly availability is applying that practice: exclude the announced window per the published policy so planned work is not scored as an unplanned outage against citizens or leadership reports.
Counting announced maintenance as an unplanned outage against the SLA automatically misrepresents reliability and punishes transparent scheduling. Hiding the maintenance notice so citizens cannot prepare violates communication expectations and may invalidate the exclusion rationale under policy. Disabling backups during maintenance so restore time is unknown adds risk unrelated to correct uptime accounting and endangers assessor recovery after the window.
Exam caveat: exclusions usually require advance notice, defined duration, and sometimes acknowledgment—overlong or unannounced “maintenance” should still count against availability. Operational check: publish the Sunday assessor window in standard channels, record start and stop, exclude only that interval in the monthly availability report per policy, and verify backups remain intact through the window.