Parks IT reports that the reservation site was available 99.9% of the month for citizen bookings. Which service-level idea is being measured?
Select an answer to reveal the explanation.
Short Explanation
Uptime is simply whether the parks reservation site stayed open for citizen bookings. Sprint velocity and invoice totals are different scoreboards entirely.
Full Explanation
Uptime, or availability, measures whether a service was reachable and usable over a period—commonly expressed as a percentage of successful time or successful requests. Parks IT reporting that the reservation site was available 99.9% of the month for citizen bookings is measuring uptime/availability for that citizen-facing reservation site, not team process velocity or cloud spend.
Mean time between code reviews for the parks team is a process metric about review cadence, not whether residents could complete bookings. Number of new features shipped in the sprint is delivery throughput, orthogonal to whether the reservation site stayed up for citizens. Cost of the cloud invoice for the parks account is financial operations, not a reliability availability measure for the booking channel.
Exam caveat: define whether uptime excludes announced maintenance and how partial degradation (slow but reachable pages) counts; inconsistent definitions make monthly 99.9% claims incomparable across reports and vendors. Operational check: compute reservation-site availability from synthetic or probe data for the month, apply the published exclusion policy, and publish the same definition leadership used when stating 99.9%.