Cisco 300-445 Practice Test Questions Answers

In theDesigning and Implementing Enterprise Network Assurance (300-445 ENNA)curriculum, monitoring the digital experience of internal employees requires leveragingThousandEyes Endpoint Agentsto simulate or record traffic from the user's specific vantage point. When an engineer needs to monitor a specific, potentially internal or non-standard web application, they must utilize theCustom Applicationworkflow within the Endpoint Experience settings.

According to the ENNA implementation standards, the first necessary action is toCreate a new custom application monitor(Option A). In the ThousandEyes portal underEndpoint Experience > Test Settings > Synthetic Tests, the "Monitor Application" button provides access to pre-defined templates for popular services like Microsoft 365 or Webex. However, for a unique enterprise application, the engineer must select "Custom Application" to define the application's identity, including its name and the relevant domain or URL.

The second required action is toAdd a new scheduled test to the monitor(Option C). Endpoint Agents performScheduled Testsat regular, predefined intervals—such as every 5 or 10 minutes—to proactively check the application's availability, response time, and network path health without requiring user interaction. By adding a scheduled HTTP Server or Network test to the custom monitor, the engineer ensures a consistent baseline of the application's performance as seen from the employee's machine.

Reviewing the incorrect options:

Google Suite monitor (Option B):This is a specific template for Google Workspace and is not suitable for a custom application.

Dynamic Tests (Option D):These are specifically designed for collaboration tools like Zoom or Microsoft Teams to capture ad-hoc sessions; they are generally not used for baselining a standard custom web application.

Test Template (Option E):While all monitors are based on templates, "adding a new template" is not a configuration action but rather a result of the monitoring setup.

According to theDesigning 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 ofScheduled 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 theTeams 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 aDynamic Testto 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 Teamsdesktop clientrather 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 byDynamic Tests, combined with the proactive health checks ofScheduled Tests, constitutes the complete assurance strategy for Microsoft Teams.

In the framework ofDesigning and Implementing En8terprise Network Assurance (300-445 ENNA), selecting the correct agent type depends heavily on the vantage point required for the specific observation. For this scenario, the architect must collect metrics from theinternal network access layer—the point closest to where the users or devices reside within the corporate perimeter—towards a cloud-hosted destination.

TheEnterprise Agent(Option B) is the most appropriate choice because it is specifically designed to be deployed on infrastructure owned and managed by the organization. These agents are "inside-out" vantage points that can be installed directly onCisco Catalyst 9300 or 9400 Series switchesat the access layer using Docker containers. By deploying an Enterprise Agent at the access layer, the architect gains visibility into the entire network path, starting from the internal LAN, traversing the edge/WAN, and reaching into the cloud-hosted web server. This allows for the identification of issues such as local congestion, ISP peering problems, or cloud provider latency.

Other options do not meet the criteria:

Synthetic Agent (Option A):This is a distractor term. All ThousandEyes agents (Cloud, Enterprise, and Endpoint) are synthetic agents because they all perform active synthetic testing.

Cloud Agent (Option C):These are pre-deployed by Cisco in global ISP data centers and provide an "outside-in" view.14While useful for monitoring public-facing availability, they cannot provide visibility into the internal network or the access layer of the organization.

Endpoint Agent (Option D):While these are installed on end-user machines and provide a "user-centric" view, they are generally not used for infrastructure-level path analysis from the access layer switches themselves.

Thus, theEnterprise Agentis the definitive choice for monitoring from the access layer to the cloud.

In theDesigning and Implementing Enterprise Network Assurance (300-445 ENNA)curriculum, monitoring modern APIs often requires handling complex authentication flows, such as OAuth 2.0 with specific client credential parameters. The provided exhibit illustrates theHTTP Authenticationoptions available within a standard HTTP Server test: None, Basic, NTLM, Kerberos, and OAuth.

According to the ENNA implementation standards, while the HTTP Server test type supportsOAuth(Option C), its native implementation is limited. Specifically, it is designed to use a pre-existing token or a simple token refresh flow; it does not support the injection of custom parameters in the initial POST request required to obtain a token in many enterprise client-credential scenarios. Basic and NTLM (Options A and B) are legacy protocols that rely on simple username/password headers and cannot facilitate the multi-step token exchange process described.

To fulfill the requirement of a two-step flow (POST for token, followed by GET for resource), engineers must use more flexible test types:

Transaction scripts (Option D):These allow the engineer to write custom JavaScript using the ThousandEyes transaction library to programmatically handle the POST request, parse the resulting JSON token, and then pass that token into the subsequent GET request's header.

API tests (Option E):These are purpose-built for API monitoring and natively support the definition of variables and multi-step requests where the output of one call (the token) serves as the input for the next.

By utilizing these advanced test types, the engineer can successfully navigate complex authentication requirements that the standard HTTP Server test cannot accommodate.

Under theDesigning and Implementing Enterprise Network Assurance (300-445 ENNA)guidelines, the integration between ThousandEyes andCisco Secure Client(formerly AnyConnect) is designed to provide visibility into the hybrid workforce experience. The integration primarily leveragesnetwork performance data from the user's device(Option C) to diagnose connectivity and application issues.

This data is collected by theThousandEyes Endpoint Agent, which is deployed as a module within the Cisco Secure Client.10The agent captures real-time telemetry from the user's laptop or workstation, includingWi-Fi signal strength,CPU and memory utilization, andlocal network gateway latency. Specifically, for remote users, it monitors the health of the VPN tunnel and the performance of applications as seen from the end-user's vantage point.

When a user reports a "slow application," this integrated telemetry allows IT teams to determine if the root cause is the user's home Wi-Fi, a saturated VPN concentrator, or an issue within the ISP underlay. The agent performsAutomated Session Testing (AST), which maps the network path as soon as a user joins a critical meeting or accesses a SaaS tool, providing a granular view of every hop between the device and the service destination. Unlike hardware configuration data (Option A) or behavioral analytics (Option B), the focus here is strictly on thenetwork performance metricsthat impact digital experience.

Therefore, the collection of device-centric network performance data is the core function of the Cisco Secure Client and ThousandEyes integration.