350-101 Exam Dumps - Implementing and Operating Cisco Wireless Core Technologies (350-101 WLCOR)v1.0

In wireless antenna design, gain refers to the measure of an antenna’s ability to focus energy in a particular direction compared to a reference antenna, usually an isotropic radiator. Gain does not generate additional power; instead, it redistributes radiated energy to increase signal strength in the intended direction, enhancing the effective range and performance of the wireless link. This directional amplification is crucial in both point-to-point and point-to-multipoint deployments, as higher gain antennas can concentrate RF energy to overcome path loss and improve received signal strength at the target. Option A describes system loss calculation, which relates to link budgets, not antenna gain. Option B is unrelated, as checksum figures are part of digital error detection in wireless frames. Option D pertains to environmental tolerance, not RF signal characteristics. In Cisco Wireless Core Technologies, antenna gain is considered during RF planning, coverage modeling, and site surveys to ensure optimal signal distribution, proper overlap, and minimal interference, particularly for high-density deployments. Using high-gain directional antennas in corridors or long hallways, for instance, improves coverage and throughput while minimizing interference outside the target area. Reference topics:RF Fundamentals — Antenna gain, directional radiation patterns, link budget, site survey planning.

To enforce endpoint compliance using Cisco ISE, the WLC must allow AAA policies configured on the ISE tooverride the WLAN default access policies. Enablingaaa-overrideon the WLAN allows the WLC to apply RADIUS-supplied attributes from Cisco ISE, including user roles, VLAN assignment, and posture evaluation outcomes, to connected clients. This is essential for enterprise environments where a posture policy (e.g., checking device security posture, anti-virus status, OS updates) must be applied prior to granting full network access.

Without enablingaaa-override, the WLC would ignore the RADIUS-supplied attributes and enforce only the WLAN-level defaults, preventing compliance-based enforcement. Option B (wireless profile policy WLAN-Staffnac) is invalid syntax; the WLAN profile must be configured via AAA overrides rather than a standalone NAC profile. Options C and D incorrectly attempt to manipulate radius enable commands at the WLAN or profile level but do not facilitate endpoint posture assessment enforcement.

Cisco’s official wireless deployment guides recommendaaa-overridewhenever integration with Cisco ISE or other RADIUS servers is used for role assignment, VLAN mapping, or posture policy enforcement. Reference topic:Client Connectivity Configuration — WLAN AAA override, Cisco ISE integration, posture policy enforcement, and compliance-based access.

To enforce adaptive policies based on user identity, device posture, and provide comprehensive visibility into device activity and location, Cisco recommends integrating Cisco Catalyst Center, Cisco ISE, and Cisco Spaces. Cisco ISE provides identity-based access control and posture assessment, allowing dynamic policy enforcement for users and devices. Mobile device management integration further extends posture checks for endpoint compliance. Cisco Catalyst Center enables real-time assurance and monitoring of network performance, device activity, and service health, while Cisco Spaces provides location analytics and visibility of client devices across the wireless environment. Option B relies solely on ACLs and MDM, which cannot provide full network-wide visibility or context-aware policy enforcement. Option C enables visibility via Catalyst Center but lacks dynamic identity and posture-based policies because it omits ISE integration. Option D integrates ISE but neglects device posture and location visibility, failing to meet all requirements. The combination in Option A ensures that adaptive policies can respond to real-time user and device conditions, enforce compliance, and provide actionable insights for network operations. Reference topics:Wireless Monitoring and Management — Catalyst Center assurance, Cisco ISE integration, mobile device posture, Cisco Spaces location analytics.

In decibel calculations, the formula used to convert a power ratio to decibels (dB) is:

Thus, the power ratio of 10:1 corresponds to a10 dBchange in power.

Option A: -20 dBwould correspond to a ratio of 0.01:1, not 10:1.

Option B: 5 dBwould correspond to a power ratio of approximately 3.16:1, not 10:1.

Option D: 15 dBwould correspond to a ratio of 31.62:1, not 10:1.

Therefore,Option C: 10 dBis the correct answer, as it is the result of a power ratio of 10:1.

Thus, the power ratio of 10:1 corresponds to a10 dBchange in power.

Option A: -20 dBwould correspond to a ratio of 0.01:1, not 10:1.

Option B: 5 dBwould correspond to a power ratio of approximately 3.16:1, not 10:1.

Option D: 15 dBwould correspond to a ratio of 31.62:1, not 10:1.

Therefore,Option C: 10 dBis the correct answer, as it is the result of a power ratio of 10:1.

Layer 3 roaming is the process that allows a wireless client to retain its original IP address when roaming across different Layer 3 client subnets or controller client VLAN contexts. Cisco describes intercontroller Layer 3 roaming as occurring when wireless LAN interfaces are on different IP subnets. During this roam, the controllers exchange mobility messages, but instead of simply moving the client database entry, the original controller marks the client as anAnchor, while the new controller marks the copied client entry asForeign. Cisco explicitly states that the roam remains transparent to the wireless client and that the client maintains its original IP address.

The correct expression isaccessPoints[0].interfaces[1] .macAddress. The JSON object contains a top-level key namedaccessPoints, whose value is an array. Array indexing begins at zero, soaccessPoints[0]selects the first access point object,ap-west-1. Inside that object, theinterfaceskey also contains an array. Therefore,interfaces[1] selects the second interface object, which hasslot: 1,status: "down", andmacAddress: "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 selectsap-east-2. Option C selects the first interface onap-west-1. Option D references a non-existent second interface onap-east-2. Reference topics:Automation and AI — JSON parsing, REST APIs, Catalyst Center programmability, RESTCONF, and wireless telemetry data structures.

The correct method issoftware image management workflows, specifically Cisco Catalyst Center Software Image Management, commonly referenced as SWIM. Cisco documents SWIM as the mechanism used to manage software upgrades and maintain consistency of image versions across the network. It provides an image repository, golden-image assignment, image distribution, activation, readiness checks, and scheduled execution. Cisco’s wireless automation guidance specifically states that SWIM is used to update Catalyst 9800 Series Wireless Controller software by distributing the image from the Catalyst Center repository to wireless controllers and upgrading the images running on those controllers; both stages can run immediately or be scheduled for a defined maintenance window.

Option C is also validated by Catalyst Center’s update-status and workflow views. Cisco documentsImage Update Statusas the view that shows all update tasks, filters by in-progress, success, or failure, and displays a progress bar for active updates. The workflow view then exposes distribution and activation task status, timing, prechecks, postchecks, checksum verification, and AP pre-image download details. Inventory snapshots and templates do not execute controller firmware upgrades, and “lifecycle workflow” is too generic. Reference topics:Wireless Monitoring and Management — Catalyst Center SWIM, image compliance, golden images, controller upgrade automation, and update progress reporting.

Meraki AP onboarding is designed around cloud-initiated registration, not manual controller discovery. A Meraki AP must obtain network reachability, resolve Meraki cloud services, and establish outbound connectivity to the Meraki dashboard. Cisco Meraki documentation states that the dashboard provides centralized management and that, for dashboard management, a Meraki device must communicate with the Cisco Meraki cloud over a secure tunnel. The MR quick-start process further describes that, after power-on, the AP requests an IP address by DHCP, reaches the Meraki cloud through the Internet, and checks in to the dashboard.

Therefore, the required action is to connect the APs to a network with Internet access and permit the necessary outbound firewall flows to Meraki cloud services. A site-to-site VPN is unnecessary for dashboard discovery. Static management addressing may be used in constrained environments, but it increases manual work and is not required for automatic registration. DHCP lease-table serial registration is not a Meraki onboarding mechanism. Reference topics:Wireless Network Implementation — Meraki AP cloud onboarding, DHCP/DNS reachability, outbound firewall policy, and dashboard-based AP lifecycle management.