Cisco Updated 300-445 Exam Questions and Answers by ayesha

According to the Designing and Implementing Enterprise Network Assurance (300-445 ENNA) best practices for collaboration monitoring, Microsoft Teams (as well as Webex and Zoom) is monitored using a combination of Scheduled and Dynamic tests (Option D).

Scheduled Tests: These are used to proactively monitor the reachability and performance of the Microsoft Teams infrastructure. The Teams template typically includes scheduled HTTP Server tests to teams.microsoft.com and login.microsoftonline.com, along with network-layer tests to the Teams Transport Relay (e.g., worldaz.tr.teams.microsoft.com). These provide a continuous baseline of connectivity regardless of whether a user is currently in a call.

Dynamic Tests: These are a unique feature for collaboration monitoring. When an Endpoint Agent detects that the Teams application has initiated a real-time media session (audio or video call), it automatically triggers a Dynamic Test to the specific IP and port being used for that call. This allows IT teams to see the exact network path—including hop-by-hop latency and loss—of the actual call traffic while the session is active.

Real User Tests (Option C) are generally not used for Teams monitoring in the same way they are for web-based SaaS apps. Because most users utilize the Teams desktop client rather than the browser, the RUM browser extension cannot capture the rich telemetry of the desktop application ' s internal signaling and media streams. Therefore, the specialized " Automated Session Testing " provided by Dynamic Tests , combined with the proactive health checks of Scheduled Tests , constitutes the complete assurance strategy for Microsoft Teams.

According to the Designing and Implementing Enterprise Network Assurance (300-445 ENNA) curriculum, the integration between ThousandEyes and Webex Control Hub provides a streamlined troubleshooting experience for collaboration services. For the VoIP team to access the specific ThousandEyes network telemetry—such as latency, loss, and jitter—they must navigate to the Network Path (Option B) section within the Troubleshooting tab of the Control Hub. 15

The Network Path visualization is a direct result of the ThousandEyes Endpoint Agent data being pulled into the Webex interface. 16 When a user or RoomOS device experiences poor audio or video quality during a meeting, the Control Hub ' s troubleshooting view displays a " Network Path " line under the participant ' s details. 17 By clicking on this line, the VoIP team can see a hop-by-hop breakdown of the entire route from the collaboration device to the Webex media node. This view highlights specific hops where performance is " Poor " (red), " Fair " (yellow), or " Good " (green) based on predefined thresholds for latency ( > 400ms) or loss ( > 5%).

While " Devices " (Option A) is where the agents are activated, and " Users " (Option C) allows for selecting a specific participant, the actual telemetry metrics and the visualization of the network route are strictly located in the Network Path view. This integration eliminates the need for the VoIP team to leave the Webex environment for initial triage, as they can identify if a problem is local to the branch office or deep within a service provider ' s network directly from the " Network Path " dashboard.