Question 570
At Granite SaaS, the site reliability team maintains multi-tenant Linux application instances under requirements for per-service isolation and reliable automated scaling. The acceptance reviewer must validate: A service monitoring agent reports success despite TLS health-check failures because its probe tests only whether a TCP port is open. Which observed result BEST demonstrates that the correction works?
Explanation
Correct Answer
A test with an invalid certificate fails health while a complete valid application request passes. This measurable outcome verifies correction of: A service monitoring agent reports success despite TLS health-check failures because its probe tests only whether a TCP port is open. The associated technical action is: Add an authenticated or validated protocol-level health check matching the actual service's readiness and certificate requirements. The Granite SaaS review checks actual behavior rather than an untested change claim.
Incorrect Answers
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 Granite SaaS problem is: A service monitoring agent reports success despite TLS health-check failures because its probe tests only whether a TCP port is open. The decisive expected evidence is instead: A test with an invalid certificate fails health while a complete valid application request passes.
ip route shows the proper connected network and bidirectional communication succeeds without an accidental default-gateway detour. This evidence pertains to an unrelated remediation: Correct the interface subnet prefix in the persistent network configuration and verify the connected route. The alternative issue is: Two Linux servers on the same subnet cannot communicate because one has a prefix length that incorrectly treats its peer as a remote network. The current Granite SaaS problem is: A service monitoring agent reports success despite TLS health-check failures because its probe tests only whether a TCP port is open. The decisive expected evidence is instead: A test with an invalid certificate fails health while a complete valid application request passes.
A controlled connection to the protected subnet uses the tunnel interface and ordinary public traffic retains normal egress. This evidence pertains to an unrelated remediation: Correct the route priority or policy routing for the specific remote network while preserving the normal default route. The alternative issue is: A VPN-connected Linux host can reach its peer IP but its route selects a public gateway rather than the approved tunnel subnet. The current Granite SaaS problem is: A service monitoring agent reports success despite TLS health-check failures because its probe tests only whether a TCP port is open. The decisive expected evidence is instead: A test with an invalid certificate fails health while a complete valid application request passes.