FOA CFOT common mistakes
FOA CFOT · Understand the traps and how to avoid them.
Choosing multimode fiber for a multi-kilometer campus or access link because 'multimode is cheaper to terminate,' then failing questions about distance/bandwidth limits.
Modal dispersion and the higher attenuation of multimode at 850/1300 nm cap its reach; candidates conflate cheap transceivers and easy termination with suitability for long spans.
What to do instead
Memorize the rough design envelopes: multimode for building/campus runs (hundreds of meters, OM3/OM4 to ~300 m at high rates), single-mode for km-scale outside plant and access. When a question gives a distance over ~500 m or a long-haul/FTTH context, default to single-mode and justify with dispersion and attenuation.
Treating 62.5/125 and 50/125 multimode as interchangeable, or assuming a 50 µm core mates cleanly with 62.5 µm fiber without penalty.
Both are 'multimode,' so candidates ignore core/cladding geometry and the loss penalty from core mismatch and differing bandwidth grades (OM1–OM5).
What to do instead
Learn the core/cladding pairs (62.5/125, 50/125, 9/125 single-mode) and the OM1–OM5 grade table. For mixed-core splices/connectors, expect added loss and state that best practice is to match fiber types; use the larger-core-to-smaller-core direction as the lower-loss case.
Confusing the color codes and polarity rules for premises fiber (e.g., swapping the TIA-598 12-fiber color sequence or miswiring a duplex pair as straight-through instead of A-B crossover).
Color sequences and duplex polarity are memorization items that candidates skim, and they map copper patch-cord habits onto fiber.
What to do instead
Drill the 12-fiber sequence (Blue, Orange, Green, Brown, Slate, White, Red, Black, Yellow, Violet, Rose, Aqua) until automatic, and practice polarity: duplex patch cords are A-B (crossed) so transmit on one end reaches receive on the other; MPO trunks use Method A/B/C-know which yields a crossed pair.
Underestimating or misapplying bend radius and pulling tension rules on premises cable (e.g., allowing tight cable-tie cinching or a bend tighter than the manufacturer's minimum).
Candidates treat fiber like copper, where tight dressing and sharp bends are tolerated; they forget that macrobending causes real loss and can crack glass.
What to do instead
State the rule as 'follow manufacturer spec, never tighter than the stated minimum' and expect indoor cable minimum bend radii on the order of several centimeters (tensile load dependent). Remember bend-insensitive fiber reduces but does not eliminate macrobend loss, and cable ties must not deform the jacket.
Sizing outside plant conduit and pull boxes from cable diameter alone, ignoring fill ratio, bend radius at handholes, and future capacity.
Candidates focus on 'does the cable fit' and skip standard fill percentages and the practical need to pull through bends and leave slack.
What to do instead
Apply standard conduit fill practice (keep cable occupancy well under half the conduit ID), verify pull-box and duct-bend radii against cable minimum bend radius under load, and always design spare capacity and slack loops for splicing and future fibers.
Treating aerial, buried, and underground placement as interchangeable and picking a cable type without matching it to the environment (e.g., using indoor distribution cable outdoors or standard loose tube where rodent/water protection is needed).
Cable construction terms (loose tube, tight buffer, armored, toneable, figure-8) blur together, so candidates pick by habit rather than by environment.
What to do instead
Build a placement-to-cable matrix: aerial (figure-8/messenger, UV-rated), buried (armored, rodent-resistant), underground duct (loose tube, water-blocked). Match jacket/strength-member/water-blocking features to the hazard and cite the hazard when answering.
Designing a link without a loss budget, or computing the budget but forgetting connector, splice, and margin allowances-then declaring a link 'passes' on a single end-to-end reading.
Candidates jump to 'the light gets through' and skip the arithmetic of component losses, wavelength-dependent attenuation, and design margin.
What to do instead
Always compute: budget = (transmitter output − receiver sensitivity); losses = fiber attenuation × length + connector pairs + splices + splitters; subtract a design margin (commonly a few dB). Compare per-wavelength and per-direction, and remember splitters in PON add large fixed loss.
Mixing up test-set roles and reference methods-e.g., using one-jumper vs. three-jumper references without adjusting expectations, or measuring with the wrong source/wavelength for the fiber under test.
Insertion loss depends on the reference method and on launch conditions; candidates memorize 'test the link' without learning that the reference setup changes the measured value and that multimode needs the right launch (mandrel/EF-style conditioning).
What to do instead
Learn that one-jumper reference includes one connector pair and three-jumper includes none, and that results must be compared to the correct limit for that method. Match source wavelength to the application (850/1300 nm multimode, 1310/1550 nm single-mode), set the reference before testing, and keep the same method for acceptance.
Reading an OTDR trace as a simple loss number-misidentifying events, ignoring dead zones, or treating a reflective spike and a splice loss as the same thing.
OTDR interpretation is graphical and candidates skim it; they don't connect blind/dead zones to pulse width and don't account for bidirectional averaging of splice loss.
What to do instead
Practice trace anatomy: launch/end reflections, non-reflective splice events, reflective connectors, and the fact that short pulse widths shrink dead zones but reduce range. Know that splice loss is best taken as the average of both directions, and that a ghost reflection is not a real event.
Designing FTTH/PON as a simple point-to-point link-ignoring split ratios, power budget for the splitter cascade, and the upstream/downstream wavelength plan (e.g., 1490/1310 nm with 1550 for video overlay).
Candidates carry over point-to-point habits and forget that a single OLT port is shared by many ONTs through splitters, so loss and wavelength allocation drive feasibility.
What to do instead
Memorize the PON basics: a passive splitter (e.g., 1:32) imposes roughly 15–17 dB loss, budget must cover feeder + distribution + drop + splitters + connectors + margin, and wavelengths are ~1490 nm downstream / ~1310 nm upstream with 1550 nm reserved for RF video. Check the split ratio against the class power budget before declaring the design viable.