A hospital campus already collects Meraki Insight at the clinic, and nurses report that one clinical application is slow while basic connectivity stays up. Which view should the team use?
Select an answer to reveal the explanation.
Short Explanation
The clinic already has a camera on the waiting room, so you watch that feed before you invent a new errand. Application slowness, with Meraki Insight already collecting at the clinic, is read from that application view. A name check, a call test, or a path test that skips the application describes a different symptom.
Full Explanation
Meraki Insight is already collecting at the clinic, and the complaint is that one clinical application is slow while basic connectivity stays up, so the team should use the Meraki Insight application view for that application. The collection already in place is aimed at how applications behave on that network, and the symptom names an application rather than a failed lookup or a failed call. A DNS test of the clinic resolvers looks for a bad or missing name, which is not what the nurses reported. A voice test of the campus nurse-call system exercises call setup and media for a different service than the slow clinical application. A network test that reports loss and jitter and skips the application describes the path, and that path can look ordinary while the application is slow. The exam trap is standing up a name test, a call test, or a path-only test when the application view is already collected for this complaint. In production, use the Meraki Insight view of that clinical application at the clinic and set it beside path loss and jitter, keeping the application as the thing under test. If connectivity stays up and the application view shows the slowness, the DNS and voice tests are not the match for this report.