A hotel chain reports that guest-room call setup fails in the evening, while synthetic web tests to the booking site stay successful. Which test matches the failing service?
Select an answer to reveal the explanation.
Short Explanation
The booking site is the front door, and the guest phones are a different building. You match the failed call setup with a voice test, because the web tests are already green. A name check, another page load, or a gateway reachability probe covers a service that is not the one failing.
Full Explanation
Call setup is failing while synthetic web tests to the booking site stay successful, so the matching test is a voice test that exercises call setup and the media path. A green web test is evidence about the booking page, not about signaling or voice media from the guest room. A DNS test checks whether the booking name resolves, and the report does not describe a bad name for that site or for the phones. A web transaction that reloads the public booking page repeats a test that is already succeeding. A network test that checks reachability of the hotel default gateway can show that the local gateway responds and still not place a call or score media. The exam trap is retesting the green web service, or checking the gateway, when the failing service is call setup. In production, run a voice test from the guest-room network that exercises call setup, and keep the successful web test as a control rather than as the diagnosis. If call setup fails while that web control stays green, the voice test is the result the hotel should act on.