Question 550
At Maplewood Schools, the district server administration team maintains education identity and web servers under requirements for approved access and repeatable configuration. Following a proposed correction, the team checks: A monitoring dashboard displays average CPU only and misses repeated five-minute service outages because no application health checks exist. Which observed result BEST demonstrates that the correction works?
Explanation
Correct Answer
A controlled application outage is detected within the intended interval and its availability SLI reflects the failed requests. This measurable outcome verifies correction of: A monitoring dashboard displays average CPU only and misses repeated five-minute service outages because no application health checks exist. The associated technical action is: Define service-specific availability probes and measurable service-level indicators with an appropriate sampling interval. The Maplewood Schools review checks actual behavior rather than an untested change claim.
Incorrect Answers
A load replay no longer exceeds the defined task ceiling and administrative logins still succeed. This evidence pertains to an unrelated remediation: Identify process and cgroup limits, fix the worker spawning policy and enforce appropriate per-service task limits. The alternative issue is: An application exhausts available process slots after spawning unbounded workers, making SSH sessions and system tools fail to start. The current Maplewood Schools problem is: A monitoring dashboard displays average CPU only and misses repeated five-minute service outages because no application health checks exist. The decisive expected evidence is instead: A controlled application outage is detected within the intended interval and its availability SLI reflects the failed requests.
The blocked-process count decreases after storage repair and user-facing request latency returns to its established baseline. This evidence pertains to an unrelated remediation: Inspect process states and I/O wait using ps, top and storage latency tools rather than assuming runnable CPU saturation. The alternative issue is: A Linux application has high load average but CPUs are mostly idle because multiple threads are stuck in uninterruptible disk wait. The current Maplewood Schools problem is: A monitoring dashboard displays average CPU only and misses repeated five-minute service outages because no application health checks exist. The decisive expected evidence is instead: A controlled application outage is detected within the intended interval and its availability SLI reflects the failed requests.
The inode free count increases and a controlled new file is successfully created on the repaired filesystem. This evidence pertains to an unrelated remediation: Inspect inode counts and remove or redesign the verified excessive tiny-file workload rather than simply increasing bytes. The alternative issue is: A filesystem reports zero available inodes even though a storage capacity dashboard shows free gigabytes. The current Maplewood Schools problem is: A monitoring dashboard displays average CPU only and misses repeated five-minute service outages because no application health checks exist. The decisive expected evidence is instead: A controlled application outage is detected within the intended interval and its availability SLI reflects the failed requests.