ThousandEyes offers several native integrations for receiving instant event notifications triggered by alerts.Which of the following integrations are available directly within the ThousandEyes platform? Select all that apply.
Answer(s): A,B,C,D,F,G,H
According to the Designing and Implementing Enterprise Network Assurance (300-445 ENNA) architecture, ThousandEyes provides a suite of native, "out-of-the-box" integrations specifically designed for alert notifications. These integrations are configured via the Manage > Integrations or Alert Rules > Notifications tabs and allow the platform to push instant event data to a variety of collaboration, IT operations, and observability tools.The verified list of native notification integrations includes:ServiceNow (A): Facilitates direct incident management and automated ticketing workflows.PagerDuty (B): Allows for automated incident escalation and on-call routing based on ThousandEyes alerts.MS Teams (C) & Slack (H): Enable real-time chatops by pushing alert details and permalinks directly into specified channels for team collaboration.Splunk (D): Utilizes the Cisco ThousandEyes App for Splunk to ingest alert data for historical analysis and correlation within a SIEM or logging platform.AppDynamics (F): Sends alert notifications directly into an AppDynamics instance, allowing application owners to correlate network issues with APM metrics.12Webex (G): Integrates with the Webex Control Hub and specific Webex spaces to provide unified visibility for collaboration performance.34AWS (Option E) is not a native alert notification destination 5in this context; instead, ThousandEyes integrates with AWS for "Cloud Insights" (ingesting VPC Flow Logs) and "Test Recommendations" rather than acting as a receiver for event notifications like a chat or ITSM tool. By utilizing these native integrations, enterprise teams ensure that the right stakeholders are notified through their preferred communication channels the moment a performance threshold is breached, drastically improving response times across the organization.
A network engineer deploys a ThousandEyes Docker agent on a switch using app-hosting. The agent needs to communicate through a proxy server, but this configuration was missed during the initial deployment. The engineer adds the proxy settings to the app-hosting configuration.What is the next step to ensure the agent uses the proxy and appears online in the ThousandEyes portal?
Answer(s): C
In the Designing and Implementing Enterprise Network Assurance (300-445 ENNA) implementation guide, the Cisco IOS XE Application Hosting lifecycle is a critical concept for troubleshooting and configuration management.When an application environment variable--such as proxy settings--is modified in the app-hosting configuration, a simple restart of the container is insufficient.The correct procedure involves moving the application back to the Configured state before bringing it back to Running. This requires a four-step lifecycle execution (Option C):Stop: Terminates the current running instance of the container.Deactivate: Releases the hardware resources (CPU, Memory, Virtual Interfaces) and, crucially, detaches the previous runtime configuration.Activate: Re-allocates the resources and injects the new configuration parameters (including the updated proxy settings) into the container's environment.Start: Initiates the container with the newly applied configuration.Without the deactivate/activate sequence, the container will continue to use the environment variables present at the time of its initial activation, causing the agent to remain offline as it fails to reach the ThousandEyes portal without the proxy. Reinstalling (Option B) is an unnecessary and time- consuming step that involves re-downloading or re-copying the image, while No action (Option D) will result in no change to the agent's connectivity status.
What are the different ways to deploy a ThousandEyes Agent in a Switch? (Choose all that apply)
Answer(s): E
In the Designing and Implementing Enterprise Network Assurance (300-445 ENNA) architecture, the deployment of ThousandEyes Enterprise Agents on switching infrastructure is designed to be highly flexible, catering to different management styles and network scales. Modern Cisco switches, specifically the Catalyst 9300 and 9400 Series, support the execution of containerized applications directly on the switch's hardware through the Cisco IOS XE Application Hosting framework.1Application Hosting (Option A) refers to the manual method using the Cisco IOS XE Command Line Interface (CLI). An engineer can use app-hosting commands to install, configure, and manage the Docker-based Enterprise Agent.2 This provides granular control over resource allocation and networking for the container. Catalyst Center (Option B) provides a GUI-driven, automated workflow to deploy agents at scale across an entire campus fabric.3 It simplifies the lifecycle management by handling the installation and activation across multiple switches simultaneously. For switches acting as edge devices in an SD-WAN fabric, Catalyst SD-WAN Manager (Option C) orchestrates the deployment through centralized policies and templates, allowing the agent to be pushed as part of a device configuration. Finally, while the ThousandEyes Portal (Option D) is the management plane for tests, it is also where the Docker image and Account Group Token are obtained for any of the aforementioned deployment methods.Each method provides the same end result: an Enterprise Agent running "on-box" to provide deep visibility into the network path starting directly from the access or core layer. Therefore, All of the above (Option E) is the correct answer as it encompasses the manual, automated, and orchestrated methods available for switch-based deployment as per the 300-445 ENNA official guidelines.
What Meraki platform supports ThousandEyes?
Answer(s): A
According to the Designing and Implementing Enterprise Network Assurance (300-445 ENNA) curriculum, the native integration of ThousandEyes within the Meraki portfolio is specifically focused on the Meraki MX security and SD-WAN appliances. This integration allows users to install ThousandEyes Enterprise Agents directly on supported Meraki MX hardware, providing critical visibility into the performance of services that distributed users rely on.4The Meraki MX (Option A) supports the ThousandEyes Enterprise Agent as a containerized service that can be activated with a single click within the Meraki Dashboard.5 This integration is designed to provide better monitoring and testing capabilities for customers interested in improving the quality of their experience and adding the appropriate SD-WAN policies to optimize network performance. By running the agent natively on the MX, administrators can monitor the performance of external applications and services directly from the SD-WAN sites, bridging the gap between local branch health and global internet performance.6While Cisco continues to expand its assurance integrations across the portfolio, the MR (Wireless), MS (Switching), MV (Camera), and MG (Cellular) series do not currently support the native, "on-box" execution of the ThousandEyes Enterprise Agent. For these other platforms, visibility is typically achieved through passive monitoring via Meraki Insight (MI) or by deploying ThousandEyes agents on connected client devices (Endpoint Agents) or nearby infrastructure. Therefore, the Meraki MX is the only verified platform supporting native ThousandEyes agent deployment in this context.
A network engineer deploys a ThousandEyes Docker agent on a switch using app-hosting.7 The agent needs to communicate through a proxy server, but this configuration was missed during the initial deployment. The engineer adds the proxy settings to the app-hosting configuration.What is the next step to ensure the agent uses the proxy and appears online in the ThousandEyes portal?
In the Designing and Implementing Enterprise Network Assurance (300-445 ENNA) implementation guide, the Cisco IOS XE Application Hosting lifecycle is a critical concept for troubleshooting and configuration management.When an application environment variable--such as proxy settings or account tokens--is modified in the app-hosting configuration, a simple restart of the container is insufficient to apply those changes.The correct procedure involves moving the application back through its lifecycle states to ensure the new environment variables are injected. This requires executing the full agent lifecycle (Option C):Stop, Deactivate, Activate, and Start.Stop: Terminates the current running process of the container.Deactivate: Releases the allocated hardware resources (CPU, Memory) and, most importantly, clears the runtime environment.Activate: Re-allocates the resources and injects the updated configuration parameters into the container's environment variables.Start: Initiates the container with the newly applied configuration settings.After the application is up and running, the ThousandEyes-agent process attempts to connect to the controller in the cloud environment. Without the deactivate/activate sequence, the container continues to use the environment variables present at the time of its initial activation, causing the agent to remain offline as it fails to reach the ThousandEyes portal without the proxy. Reinstalling (Option B) would work but is an unnecessarily lengthy process, while No action (Option D) will result in no change to the agent's connectivity status.
Post your Comments and Discuss Cisco 300-445 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the 300-445 content, but please register or login to continue.