CWSS common mistakes
CWSS · Understand the traps and how to avoid them.
Treating dBm and mW as interchangeable and reporting a 20 mW access point as '20 dBm', then miscomputing the EIRP when antenna gain is added.
Candidates memorize the dBm scale as a set of magic numbers without internalizing that dBm is an absolute logarithmic power reference to 1 mW, so they convert only when a question explicitly says 'convert' and skip the conversion when gain or loss is added in dB.
What to do instead
Drill the two anchor points until automatic: 0 dBm = 1 mW and 10 dBm = 10 mW, with every 3 dB doubling and every 10 dB multiplying by ten. Practice chained problems such as 20 mW (+13 dBm) plus a 6 dBi antenna giving roughly 19 dBm EIRP, and always state units on every intermediate line before adding decibels.
Confusing dB of loss in a cable with dBi of gain in an antenna and adding both as gain when computing EIRP.
Both quantities are expressed in decibels and the sign convention feels arbitrary, so candidates apply the arithmetic without tracking direction of the change, especially when the question presents the numbers in an unusual order.
What to do instead
Adopt a fixed bookkeeping habit: write the link as a signed sum, transmitter dBm, minus cable and connector loss in dB, plus antenna gain in dBi, equals EIRP dBm. Rehearse a worked example where a 3 dB cable loss and an 8 dBi antenna net to +5 dB, and verify the answer is plausible against the transmitter power.
Assuming higher frequency always means shorter range and answering range questions from frequency alone, ignoring transmit power, antenna gain, receiver sensitivity, and noise floor.
Simplified study material reduces propagation to a single rule of thumb, and candidates under time pressure reach for the memorable rule instead of the full link budget the question actually supplies.
What to do instead
Before answering any range or coverage question, list the four controlling factors and check which ones the stem provides. If power, sensitivity, and gain are given, compute the link margin; only fall back on the general frequency trend when the stem gives no other data, and say so in your reasoning.
Mixing up 2.4 GHz and 5 GHz channel numbering, for example calling channel 36 a 2.4 GHz channel or claiming 2.4 GHz channel 14 is usable in every regulatory domain.
The two bands use different numbering conventions and different regulatory limits, and candidates learn a single channel list without attaching each number to its band and its regional restriction.
What to do instead
Build a mental table: 2.4 GHz channels 1 to 14 with 1, 6, and 11 as the classic non-overlapping set in North America, and 5 GHz numbered in blocks of four (36, 40, 44, 48 and so on) with UNII sub-bands. Attach the regulatory note, such as channel 14 being limited to Japan, to each row so the number and the rule travel together.
Describing CSMA/CA as if it detected collisions the way wired Ethernet does, rather than avoiding them through a contention window and acknowledgements.
Candidates carry over the wired CSMA/CD model because the acronyms look similar, and half-duplex radio cannot listen while transmitting, so the mental model quietly breaks without being noticed.
What to do instead
State the mechanism in order: listen, wait a random backoff inside the contention window, transmit, and require a link-layer acknowledgement. Explain that a missing acknowledgement is the only collision evidence available, which is why the window doubles on failure. Contrast this explicitly with wired collision detection in one sentence.
Treating WPA2-PSK and WPA2-Enterprise as differing only in password length, or claiming WPA3-Enterprise is required to protect management frames.
Security modes are learned as a list of names with vague strength rankings, so the actual differentiator, per-user authentication against a RADIUS server versus a shared passphrase, is never anchored.
What to do instead
For each mode, name the credential and the verifier: PSK uses a shared passphrase that every client knows, Enterprise uses 802.1X with per-user credentials checked by a RADIUS server. Separately note that management frame protection is a feature of the 802.11 standard family, not a WPA3-Enterprise exclusive, and check the standard version before attributing it.
Confusing roaming behaviour with mesh behaviour, asserting that a client automatically hands off to the strongest access point or that mesh backhaul is always wireless.
Both features describe multiple access points cooperating, and vendor marketing blurs them, so candidates merge the two into one concept and then answer questions about either with the same sentence.
What to do instead
Define each separately. Roaming is a client decision, aided by standards such as 802.11k neighbour reports and 802.11r fast transition, and the client ultimately chooses. Mesh is an infrastructure decision about how access points reach the wired network, and backhaul may be wireless or wired. Answer each question with the side that owns the decision.
Recommending a specific antenna or access point model before establishing the requirement, so the answer names hardware when the question asked which capability is needed.
Hardware questions reward recall of part numbers and specifications, and candidates over-apply that recall to scenario questions where the correct answer is a capability such as directional coverage or PoE budget.
What to do instead
Read the question's final clause to see whether it asks for a capability or a component. If it asks what is needed, answer in capability terms first, for example a high-gain directional antenna to cover a long narrow aisle, and only name a product class when the stem supplies a constraint that forces one.
Ignoring power sourcing when specifying access points, assuming any PoE switch will power any access point.
Power over Ethernet is taught as a single checkbox feature, so the differences between the 802.3af, 802.3at, and 802.3bt power classes and the resulting per-port budget are never connected to access point power draw.
What to do instead
Memorize the approximate per-port ceilings for 802.3af, 802.3at, and 802.3bt, then always check the access point's stated maximum draw against the switch's per-port and total budget. In scenario questions, state the budget arithmetic explicitly, including how many ports are already committed.
Answering organizational-goal questions with a technical preference, such as choosing the newest standard, instead of tying the recommendation to the stated business constraint like cost, coverage, or compliance.
The other three domains reward technical knowledge, and candidates carry that habit into scenario questions where the deciding factor is a constraint written into the stem, not a specification comparison.
What to do instead
Before selecting an answer, underline the business constraint in the stem, whether budget, timeline, regulatory obligation, or user experience, and choose the option that satisfies it even if a technically superior option exists. Justify the choice by naming the constraint it serves, then note the technical trade-off it accepts.