Cisco 350-101 Exam Dumps

RSSI, or Received Signal Strength Indicator, is a measure of the detected power level of a radio signal at the receiver, expressed in dBm. It reflects the strength of the wireless signal received by the client or access point and is a critical metric for assessing coverage, link quality, and roaming decisions. Higher RSSI values (closer to 0 dBm) indicate stronger signals, while lower values (more negative) represent weaker signals. RSSI is used by Cisco wireless controllers and clients to make roaming decisions, select access points, and optimize transmit power levels. Option B, noise generated by interference, affects signal-to-noise ratio but does not define RSSI. Option C, QoS packet marking, pertains to network traffic prioritization, not RF measurements. Option D, wireless radio service ID, refers to identifying services on a network and is unrelated to signal strength measurement. Understanding RSSI is fundamental in RF planning, AP placement, and troubleshooting wireless coverage issues. Cisco Wireless Core Technologies emphasize monitoring RSSI to maintain adequate signal levels across the deployment, ensuring seamless connectivity and performance in high-density or challenging RF environments. Reference topics: RF Fundamentals --- RSSI, signal strength, link quality, roaming, RF planning.

The correct action is to expose only encrypted management services: HTTPS for WebUI administration and SSH for remote CLI administration. The exhibit confirms the WLC wireless management interface is VLAN 10 with IP address 10.10.1.2, but interface placement alone does not enforce secure management protocol policy. Cisco Catalyst 9800 documentation identifies web admin settings as controller management configuration that determines administrator access, protocols, and interfaces for remote management. Cisco further states that administrators can connect securely over HTTPS, while HTTP ''is not a secure connection,'' and that HTTPS encrypts data to and from the server.

For CLI access, Cisco's Catalyst 9800 Secure Shell guidance states that SSH enables secure remote access, and using transport input ssh prevents non-SSH Telnet connections, limiting the device to SSH-only access. Therefore, options A and B violate policy because they permit Telnet and/or HTTP. Option C fails because console access is local, not remote, and disabling only HTTP still leaves Telnet exposure unresolved. Reference topics: Wireless Monitoring and Management --- WLC management access, secure administration, HTTPS, SSH, and management-plane hardening.

In wireless networks, the 20 MHz channel width is the standard and narrowest channel allocation in the 2.4 GHz frequency band. Using narrower channels reduces adjacent-channel interference and allows for better coexistence in high-density environments, which is particularly important in the crowded 2.4 GHz spectrum. A 20 MHz channel uses less RF bandwidth than 40 MHz or 80 MHz channels, providing more non-overlapping channels (channels 1, 6, and 11 in 2.4 GHz) to reduce co-channel interference. Option B is incorrect, as channel width does not inherently increase authentication handoff frequency; handoff behavior is determined by RSSI, client roaming thresholds, and 802.11r fast roaming settings. Option C describes client reassociation support, which is handled by the wireless controller and client firmware, not the channel width itself. Option D is incorrect because wider channels (40 MHz, 80 MHz) provide higher throughput than 20 MHz, at the expense of increased interference potential. Cisco Wireless Core Technologies emphasize that 20 MHz channels are preferred for dense deployments in the 2.4 GHz band to maximize non-overlapping channels and reduce interference, ensuring predictable coverage and reliable client connectivity. Reference topics: RF Fundamentals --- 20 MHz channels, 2.4 GHz spectrum planning, interference management, channel allocation.

The correct expression is accessPoints[0].interfaces[1].macAddress. The JSON object contains a top-level key named accessPoints, whose value is an array. Array indexing begins at zero, so accessPoints[0] selects the first access point object, ap-west-1. Inside that object, the interfaces key also contains an array. Therefore, interfaces[1] selects the second interface object, which has slot: 1, status: 'down', and macAddress: 'CC:FA:00:11:22:34'. The final selector, .macAddress, returns that MAC address value.

This structure is directly aligned with Cisco automation workflows, where RESTCONF and Catalyst Center APIs exchange structured data in JSON. Cisco documents that Catalyst Center REST API payloads are JSON-formatted, and its example describes JSON as key-value data separated by colons. Cisco also states that Catalyst 9800 RESTCONF uses structured XML or JSON with YANG models for programmatic device access. Option B selects ap-east-2. Option C selects the first interface on ap-west-1. Option D references a non-existent second interface on ap-east-2. Reference topics: Automation and AI --- JSON parsing, REST APIs, Catalyst Center programmability, RESTCONF, and wireless telemetry data structures.

MIMO, or Multiple-Input Multiple-Output, is a core 802.11n and later wireless technology that uses multiple transmit and receive radio chains and antennas to improve wireless performance. Cisco's Wireless RF Reference Guide explains that IEEE 802.11n introduced MIMO, replacing the older single-radio SISO model with multiple radios, each using its own antenna, to increase data rates and improve reception in multipath environments. Cisco also notes that weak or distorted multipath signals can be received by more than one radio and reconstructed, improving decode quality and reliability.

This directly supports option A: MIMO exploits multiple RF paths rather than treating multipath as purely destructive. Depending on implementation, MIMO can use spatial diversity, maximal ratio combining, and spatial streams to increase throughput, improve signal-to-noise ratio, reduce retries, and make more efficient use of airtime. Cisco describes spatial stream notation such as 4x4:4 as four transmitters, four receivers, and four spatial streams. Option B describes frequency hopping, not MIMO. Option C is not a MIMO function. Option D is the opposite of MIMO because MIMO deliberately uses multiple antennas and radio paths. Reference topics: 802.11 Technology Fundamentals --- MIMO, spatial streams, multipath, SISO versus MIMO, and 802.11n/ac/ax PHY enhancements.