Free CWDP-305 practice test: 30 questions with answers

Legacy 2.4 GHz-only carts need the 2.4 GHz radios, while band steering moves dual-band tablets onto 5 GHz for more capacity. Removing 2.4 GHz strands the carts, and wider 2.4 GHz channels do not solve the problem because 2.4 GHz has few non-overlapping channels.

Wider channels leave fewer non-overlapping channels, so narrowing them in dense areas lets neighbors avoid contention. Higher power and more SSIDs make co-channel overlap worse, and 2.4 GHz has fewer non-overlapping channels than 5 GHz, not more.

A slow legacy transmission occupies the shared medium for a long time, which reduces capacity for everyone on the channel. Low rates do not use more power or change channels, and they are not limited to 802.11ax clients.

A separate guest SSID mapped to its own VLAN, backed by firewall rules, enforces the separation at the network layer on the shared access points. Channel plans, host firewalls and passphrase sharing do not stop guest traffic from reaching internal servers.

Overlap gives a roaming client time to associate with the next access point before the current link degrades. It does not double capacity, remove channel planning, or let the switch balance radio load.

Reducing power shrinks each cell, which lowers co-channel interference and allows channel reuse in a dense space. Lower power shortens range rather than extending it, and no standard mandates lower power for shared channels.

Directional antennas concentrate energy along the corridor and reduce spillover into the neighboring ward, at the cost of less coverage to the sides. Raising power increases leakage, and the claim that 2.4 GHz is confined to one room is false.

DFS channels must be vacated when radar is detected, so critical coverage should rely on non-DFS channels with enough fallback options. Disabling radar detection is not allowed, DFS rules apply outdoors as well as indoors, and putting every AP on one DFS channel makes the failure worse.

Shopper experience and uninterrupted point-of-sale service are business goals that the designer later turns into technical targets such as capacity and availability. The other options mislabel the goals as technical requirements or confuse them with existing documentation and environmental factors.

Floor plans, cable records and earlier survey reports supply the building constraints that decide where access points can go. They do not prove old results still hold after changes to the building, and they do not set business goals or final channel plans.

Steel machinery and racking reflect and block RF energy, which creates dead spots and multipath behavior that a coverage model must include. The other options wrongly claim that metal boosts power, affects only cabling, or always improves SNR.

Microwave ovens and many Bluetooth and cordless phone devices transmit in the 2.4 GHz band and raise the noise there. The switch, the 5 GHz channel width and the printer do not interfere with a 2.4 GHz radio signal in this way.

Authentication method and roaming behavior are measurable technical requirements that drive configuration choices. Completion date and budget are business constraints on the project rather than radio or network behavior.

The new floor has different walls, materials and layout, so the old radio behavior does not carry over. A new predictive model and site survey are needed, and the old survey is useful only as background, while the other options assume coverage depends only on headcount or ignore construction.

Sheet metal and reinforced concrete with metal mesh absorb and reflect far more energy than the other materials listed. Wood doors, plasterboard and clear glass attenuate the signal much less, so they produce smaller losses in the model.

Technical requirements are measurable targets the network must meet, such as throughput, roaming behavior or a security method. Stakeholder goals are business requirements, while existing records and physical conditions belong to documentation and environmental inputs.

Access points that are online but cannot authenticate usually have a RADIUS reachability or configuration mismatch, so that is checked first. Transmit power, SSID length and mounting position do not explain failed 802.1X authentication.

The RF validation survey measures what the installed network actually delivers and compares it with the design targets. Business goals, firmware installation and wired port planning are outside its purpose.

Packet loss, jitter and handoff time directly affect how a call sounds during movement. The SSID count and a datasheet PHY rate do not describe the performance of a real session.

Moving an access point to cover the shadowed area and separating the overlapping neighbors addresses both problems at once. Metal blocks both bands, so a band swap does not fix it, and raising power to maximum worsens co-channel overlap.

As-built records, survey results, open issues and a signed acceptance form let the customer operate and support the network. Marketing material, serial numbers alone and a private working file do not give the customer what it needs.

Reachability between VLANs is governed by firewall or access control policy, so that is where the engineer looks first. Channel count, transmit power and basic data rate do not control which subnets a client can reach.

Client drivers, radio chipsets and roaming logic vary, and they shape the experience users actually get. Test tools can measure throughput and latency, and no standard requires real devices for acceptance, nor are test tools limited to 2.4 GHz.

The 100 m channel limit applies to twisted-pair Ethernet, so the access point must move or an intermediate switch must extend the run. PoE does not raise that limit, cable category does not change it, and a wall adapter still leaves the data run too long.

Checking each installed item against the design documents, and logging the differences, confirms the deployment matches the plan. A powered-on light, one speed test, or a signed purchase order does not verify placement or settings.

Installers need the physical plan, the per-access-point settings and the cable routes to build what was designed. Invoices, brochures and vendor lists do not help the installation.

A changed mounting location affects coverage, so the installer should stop, document the change, and have the designer confirm the new spot before mounting. Guessing, silently moving other access points or raising power everywhere are unsafe workarounds.

Labels tie each physical device to its position on the design map, so validation and troubleshooting refer to the right place. Labels do not carry encryption keys, set radio settings or report PoE class.

Cable certification confirms the wiring map and run length before the access point is mounted, so faults are found before they stall the installation. A status light, skipping older drops or testing after mounting each leave faults hidden or costlier to fix.

The switch port, VLAN mapping and PoE class are what the switch needs for each access point to power up and join the right networks. Light colors, staff counts and marketing summaries do not affect that connection.