Cisco 350-101 Exam Questions

Client exclusion is a feature in Cisco Catalyst 9800 WLCs that allows the administrator to temporarily block clients exhibiting misbehavior, such as excessive retries, excessive bandwidth usage, or roaming issues. The IOS XE CLI command for enabling client exclusion in a WLAN policy is client-exclusion <timeout>, where <timeout> defines the duration (in seconds) the client is prevented from associating with the WLAN. Option D correctly uses client-exclusion 120 to block the misbehaving clients for 120 seconds. Option A (exclude 120) is not valid IOS XE syntax. Option B (exclusionlist timeout 120) is also incorrect as it refers to internal exclusion lists, not the WLAN policy applied to live clients. Option C (security exclusion timeout 120) is invalid and does not configure client exclusion at the WLAN policy level. Cisco Wireless Core Technologies emphasize using client exclusion policies during high-density events or temporary network congestion to ensure network fairness, protect overall WLAN performance, and maintain connectivity for well-behaving clients. Reference topics: Client Connectivity Configuration --- Client exclusion, WLAN policy, misbehaving client mitigation, Cisco Catalyst 9800 IOS XE.

The correct configuration approach is to enable Application Visibility and Control on the policy profile. On the Catalyst 9800, WLANs are not configured as isolated monolithic objects; the WLAN profile is mapped to a policy profile through a policy tag, and many client traffic services are applied from that policy profile. Cisco defines AVC as the wireless feature set that identifies and monitors applications using DPI, creates rules to manage application bandwidth and usage, and integrates with Flexible NetFlow for per-application or per-protocol statistics. Cisco further states that AVC benefits from NBAR running on the AP or controller, and that the NBAR2 engine analyzes and recognizes traffic flows.

Operationally, Cisco's 9800 AVC guide shows that AVC is enabled by navigating to Configuration > Services > Application Visibility and selecting the relevant Policy Profile. It also shows the CLI form under the policy profile: wireless profile policy AVC_testing followed by ip nbar protocol-discovery, with verification showing NBAR Protocol Discovery : Enabled. Options A and B are incorrect because the feature is not enabled directly on the WLAN. Option C is generic and incomplete; the Cisco feature construct is AVC. Reference topics: AVC, NBAR2, Flexible NetFlow, Catalyst 9800 policy profiles, and wireless application visibility.

For Cisco Catalyst 9176 APs deployed at remote sites without DHCP option 43, automatic WLC discovery can be accomplished using DNS-based CAPWAP controller discovery. By creating a DNS A record named cisco-capwap-controller.<domain> that resolves to the WLC management IP address, APs can query DNS and locate their centralized controller automatically, eliminating the need for site visits or manual configuration. This method is preferred for large-scale or satellite deployments where APs may exist on different subnets and traditional DHCP-based discovery is unavailable. Option A is impractical because manually assigning static IPs to hundreds of APs is operationally complex and error-prone. Option B, using a multicast group, is not supported for cross-subnet controller discovery in CAPWAP; multicast is limited to local subnets. Option D (ap-discovery) is not a recognized standard for WLC discovery; Cisco specifically documents cisco-capwap-controller as the required DNS entry for CAPWAP-based automatic discovery. This approach ensures zero-touch provisioning, simplifies network operations, and guarantees that APs join the correct controller, supporting centralized management and consistent configuration across multiple campuses. Reference topics: Wireless Network Implementation --- CAPWAP discovery, DNS-based controller discovery, Catalyst 9800 WLC onboarding, zero-touch provisioning.

Dynamic endpoint profiling in Cisco wireless networks is used to classify devices based on type, behavior, and attributes, enabling policy enforcement that adapts to device posture. In a deployment integrated with Cisco ISE, profiling groups are created to define rules and categories for device types such as smartphones, laptops, printers, and IoT devices. These profiling groups allow the wireless controller to map devices to the correct ISE policy sets dynamically, ensuring that security policies, VLAN assignments, and access controls are applied according to the device profile. Option A (device-type groups) is a generic categorization that does not fully leverage ISE dynamic profiling capabilities. Option C (user ID groups) focuses on user identity rather than device characteristics. Option D (endpoint group mapping) is typically applied after device profiling and classification, but initial enforcement requires creating profiling groups. By configuring profiling groups, the IT team ensures that the network can classify endpoints automatically, enforce access policies consistently, and integrate with ISE for context-aware security and compliance monitoring. Reference topics: Wireless Monitoring and Management --- Dynamic endpoint profiling, Cisco ISE policy integration, profiling groups, device classification for secure access.

Wi-Fi antenna gain is measured in dBi, meaning decibels referenced to an isotropic radiator. Cisco's Wireless RF Reference Guide states that antennas have gain measured in decibels relative to isotropic gain, or dBi, and further explains that antenna gain is a ratio comparing the gain of a specific antenna to a theoretical isotropic antenna. Cisco's RF design documentation also defines dBi as the power gain rating of antennas, where real antennas are compared to an isotropic antenna that radiates the same power density equally in all directions.

Option B is therefore the correct selection, although the technically precise phrase is decibels relative to isotropic, abbreviated dBi. Antenna length can influence resonance and design, but it is not the measurement unit for gain. Voltage against dBm is incorrect because dBm references absolute power relative to 1 milliwatt, not antenna gain. Analog/digital signal blending is unrelated to RF antenna performance. Reference topics: RF Fundamentals --- antenna gain, dBi, isotropic radiator, EIRP, antenna patterns, and WLAN RF design.