CBNT common mistakes
CBNT · Understand the traps and how to avoid them.
Treating dBmV and dBm as interchangeable when reading a signal level meter, and reporting a level without stating the reference impedance or the unit.
Both are logarithmic power/voltage units and look similar on a meter display; candidates memorize '0 dBmV equals about 48.75 dBm at 75 ohms' as a fact to recall rather than understanding that dBmV is referenced to 1 mV across 75 ohms while dBm is referenced to 1 mW, so they drop the conversion and mix units across downstream and upstream calculations.
What to do instead
Before any calculation, write the unit and reference next to every number. Practice converting a handful of values both ways at 75 ohms so the ~48.75 dB offset becomes automatic, and always state 'dBmV at 75 ohms' in written answers. On the job, confirm the meter is set to the unit the work order specifies.
Confusing downstream and upstream frequency splits and applying downstream level expectations to upstream carriers.
Candidates study the forward path in detail because it carries most services, then carry those level and tilt expectations into the return path, forgetting that upstream levels at the subscriber are much lower, the band is narrow and noisy, and ingress behaves very differently in the 5-42 MHz region.
What to do instead
Build a one-page split diagram for the plant's architecture (for example 5-42 MHz return, 54-1002 MHz forward) and annotate expected levels and tolerances at each test point for both directions. When a question mentions a frequency, first place it on the split diagram before reasoning about level.
Measuring signal level at the wrong test point or with the wrong meter settings, such as reading a carrier while the meter is in sweep mode or averaging over a channel wider than the carrier.
Candidates learn the correct procedure but rush under time pressure, or they assume any reading from a signal level meter is valid; they do not check resolution bandwidth, detector mode, or whether the port is terminated, so the number looks plausible but is not comparable to the specification.
What to do instead
Adopt a fixed checklist for every measurement: correct test point, correct frequency, correct channel bandwidth, correct detector, cable and connectors in good condition, unused ports terminated. State these conditions explicitly when answering scenario questions, because exam items often hinge on one of them.
Describing leakage detection only as 'use a leakage detector' without specifying the calibration step, the antenna, or how the detected level relates to the field strength at 3 meters.
Leakage questions feel qualitative, so candidates give a generic answer; they never practiced the sequence of calibrating the receiver against a known source, driving or walking the route, and logging GPS-tagged hits with the correct units.
What to do instead
Memorize the operational sequence and the units: calibrate before the run, verify with a known leak if available, record location and level, and compare against the applicable limit expressed in microvolts per meter at 3 meters. Practice explaining why an uncalibrated detector reading cannot be used as compliance evidence.
Assuming a clean-looking connector is a good connector, skipping the visual and mechanical inspection before attaching a meter.
Candidates focus on electrical tests because those produce numbers; they underestimate how often a bad F-connector, a stray braid strand, or a loose center conductor causes the very problems the meter then reports, so they chase the reading instead of the cause.
What to do instead
Make inspection a mandatory first step: check center conductor length, dielectric condition, braid fold-back, connector torque, and weather sealing. In exam scenarios, when a reading is erratic or a single drop fails while neighbors pass, suspect the termination first and say so.
Confusing loss budget concepts: mixing insertion loss, return loss, and through-loss, or adding losses in linear units instead of dB.
The terms sound similar and candidates memorize definitions without practicing a full link budget from tap to outlet, so they add dB values incorrectly or treat return loss as a loss to subtract from signal level rather than a reflection metric.
What to do instead
Work several complete budgets end to end (passive loss from tap through splitter and cable to the outlet, plus outlet and drop losses) and state each term's meaning in one sentence. Remember return loss is a ratio describing reflection; a higher number means a better match, not more attenuation.
Answering safety questions with the general principle but omitting the specific control, such as describing 'use a ladder safely' instead of setting, securing, and maintaining three-point contact at the correct angle.
Safety content is often skimmed as common sense, so candidates never encode the concrete numbers and steps; they also forget that the exam rewards the specific procedure over the sentiment.
What to do instead
Convert each safety topic into a numbered procedure with the key figures and controls: ladder angle and tie-off, approach distances to energized lines, lockout/tagout steps, PPE for fiber work, and laser eye-hazard rules. Rehearse them aloud so the specific step, not the general idea, comes out first.
Treating fiber handling like copper handling: bending patch cords tightly, looking into a fiber end, or cleaning with a dry wipe only.
Candidates with coax backgrounds transfer habits; fiber looks robust, and the invisible nature of the hazard and of contamination makes the consequences easy to dismiss, so bend radius limits, inspection, and wet-then-dry cleaning get skipped.
What to do instead
Memorize the fiber rules as a short list: never look into a fiber or connector, respect minimum bend radius, inspect and clean every mating surface with the wet-then-dry method, and cap or cover unused connectors. Tie each rule to the failure it prevents: macrobend loss, end-face contamination, and eye injury.
Giving a technically correct but customer-hostile answer on service scenarios, such as explaining RF theory instead of acknowledging the problem, setting expectations, and confirming resolution.
Candidates prepare for the technical domains and treat customer service as filler, so they miss that scenario items test the sequence: listen, restate the issue, explain in plain language, act, verify with the customer, and document.
What to do instead
Practice a short service script and apply it to sample scenarios: acknowledge, clarify, explain without jargon, give a time expectation, confirm the fix with the customer, and note the work order. When a question asks what to do next, choose the step that respects both the technical procedure and the customer's understanding.
Reciting standards by name without knowing what they actually constrain, and inventing or misattributing a limit when unsure.
Candidates memorize acronyms and titles under time pressure and then guess at thresholds; the exam rewards knowing which body covers which topic and what kind of requirement it sets, and a confident wrong number costs more than an honest 'verify against the current standard'.
What to do instead
Build a two-column table: standard or body on the left, the specific thing it governs on the right (installation practices, RF leakage limits, safety, testing methods). Learn the categories and where to look up current limits rather than memorizing numbers that change; in answers, cite the governing document and state that the current edition's limit applies.