In theDesigning and Implementing Enterprise Network Assurance (300-445 ENNA)framework, managing a large-scale deployment of Endpoint Agents requires efficient categorization throughAgent Labels
. Agent labels are used to group agents for targeted test assignment and data filtering based on specific attributes like location, OS, or naming conventions.
ThousandEyes supports the use ofwildcards (specifically the * symbol)within label filters to allow for dynamic and scalable grouping. In this scenario, the organization has adopted a naming convention of agentname-network. To capture all agents connected to the "corporate" network regardless of the unique agentname prefix, the engineer should use the filter*-corporate(Option A) in the hostname or agent name field. The asterisk functions as a placeholder for any string of characters, ensuring that any agent ending with
"-corporate" is automatically added to the label as soon as it registers with the ThousandEyes platform.
Other options are incorrect for the following reasons:
* agentname-* (Option B):This would only match agents that literally start with the string "agentname-
", which is a placeholder and not a representative filter for a group of uniquely named agents.
* agent*corporate (Option C):This filter is overly broad and lacks the specific hyphen delimiter used in the organization's naming convention, potentially leading to the inclusion of unintended agents.
* No wildcard (Option D):Wildcards are a documented and essential feature of the ThousandEyes label system to facilitate automated management in enterprise environments.
By implementing wildcard-based labels, the network administrator ensures that new agents are seamlessly integrated into the assurance strategy without the need for manual manual intervention.

In wireless network assurance, high channel utilization and increased retransmissions are clear indicators of RF interference or over-subscription. Retransmissions are particularly damaging to voice call quality because they introduce significant jitter and late-arrival packet loss that the jitter buffer cannot overcome.
The recommended optimization is tochange the access point to a different, less congested channel(Option B). This directly reduces the competition for airtime (Channel Utilization) and the likelihood of collisions from neighboring access points (Co-Channel Interference), which in turn lowers the retransmission rate.
Modern wireless controllers usingRadio Resource Management (RRM)often automate this, but a manual adjustment based on SNMP telemetry is a valid operational fix.
Other options are technically flawed:
* Option A:Increasing transmit power oftenincreasesinterference and channel utilization for surrounding cells, making the problem worse for everyone.
* Option C:Disabling all non-voice traffic is an extreme measure that is rarely feasible in a real business environment.
* Option D:Admission control limits thenumberof users but doesn't solve the underlying issue of poor channel health for those already connected.

In theDesigning and Implementing Enterprise Network Assurance (300-445 ENNA)curriculum, capacity planning and optimization are driven by telemetry data such as NetFlow. When NetFlow identifies that delay and jitter-metrics highly impactful to real-time traffic-spike during peak hours, it indicates that high- priority packets are competing for resources with bulk data.
The most appropriate recommendation is totune the existing QoS configuration(Option C). This involves adjusting the Queuing and Scheduling policies on the routers to ensure that voice and video traffic (typically marked with EF and AF41/AF42 DSCP values) is serviced before other traffic classes during periods of congestion. This solution is targeted, cost-effective, and directly addresses the observed jitter issues without the need for massive capital expenditure.
Reviewing other options:
* Option A:A complete QoS redesign is often unnecessary and too invasive for solving peak-hour jitter if a basic QoS framework is already in place.
* Option B:Increasing bandwidth on "all" links is a "brute force" approach that is expensive and fails to address the underlying problem of traffic prioritization.
* Option D:Hardware replacement is a last resort and would not resolve delay/jitter if the new hardware still lacks a properly tuned QoS policy.

In theDesigning and Implementing Enterprise Network Assurance (300-445 ENNA)curriculum, transaction monitoring is essential for validating complex, multi-step user workflows. When an engineer with limited scripting experience needs to monitor a OneDrive file download process, the ThousandEyes ecosystem provides several tools to simplify the creation of robustTransaction tests.
The correct approach is to leverage all available resources, makingOption Dthe definitive answer. First, the ThousandEyes Recorder IDE(Option B) is a critical tool for non-scripters. It allows an engineer to perform the actual workflow-navigating to OneDrive, logging in, and initiating the download-in a browser environment on their local machine while the tool records every click and keyboard entry. The Recorder automatically generates the corresponding JavaScript code using theThousandEyes transaction library.
Second, the platform provides pre-builtscript templates(Option A), such as those forOffice 365andOneDrive
, which include baseline logic and best practices for these specific services. Third, the officialtransaction- scripting-examplesrepository on GitHub (Option C) is a maintained source of code snippets. This is particularly useful for implementing advanced logic, such as aretry mechanism, which ensures that the test does not report a "failure" due to a transient network hiccup but instead attempts the action again before triggering an alert.
As shown in the provided exhibit, a typical script uses import statements from @thousandeyes and selenium- webdriver to control the browser. By combining theRecorderfor the basic flow, aTemplatefor service- specific nuances, andSample Scriptsfor logic enhancements like retries, the engineer can deploy a highly reliable assurance test without deep coding expertise. Therefore, all three actions are highly recommended and valid within the ENNA implementation framework.

In the context ofDesigning and Implementing Enterprise Network Assurance (300-445 ENNA), capacity planning requires accurate baselining of interface bandwidth against its theoretical and provisioned limits.
AnalyzingExhibit 4.5 Question 4(image_79d4fc.jpg) reveals a significant discrepancy between the physical reality of the link and its configuration within the monitoring tool.
The exhibit displays a capacity planning dashboard with a calendar heatmap and traffic graphs. The heatmap for February through May shows a high frequency of "Severe" (red) utilization blocks. Looking at theEgress graph forTue May 07 2024, the traffic spikes clearly exceed 40.0 Mbps. Crucially, the dashboard indicates an
"Egress Capacity" of49.5 Mbpsand reports that the "Highest consumption" was 48.0 Mbps, representing97% of the available bandwidth.
However, the question states that the ISP provides a1 Gbps (1000 Mbps) connection. Since the actual traffic being sent is less than 50 Mbps, the link is nowhere near physical saturation. The "Severe" alerts and high utilization percentages are occurring only because the monitoring software (likely ThousandEyes or a similar NMS) is configured with aMaximum Capacityof only 49.5 Mbps for this interface. This misconfiguration causes the tool to calculate utilization based on a much smaller "pipe" than what actually exists, leading to false-positive alerts.
Therefore, the most likely action to fix this observed behavior is toreconfigure maximum capacity for the interface(Option B) to match the 1 Gbps specification.
* Option Ais unnecessary because the current link is only being utilized at ~5% of its 1 Gbps potential.
* Option Cis a restrictive policy change that is not justified given the actual available headroom.
* Option Dmight shift how data is displayed but will not fix the underlying mathematical error in utilization calculations.