FOA CFOS/L common mistakes
FOA CFOS/L · Understand the traps and how to avoid them.
Treating the 100 m channel limit as a single cable-length rule and forgetting that it splits into 90 m of horizontal cable plus 10 m of patch cords and equipment cords, then choosing a cable route that needs 95 m of permanent link.
Candidates memorize '100 metres' from introductory material and never internalize the 90 m + 10 m split, or they confuse permanent link with channel. The distinction only appears once you draw the full end-to-end path including cross-connect and work-area cords.
What to do instead
Before answering any length question, sketch the channel from equipment outlet to the active equipment, label each segment, and apply the 90 m horizontal + 10 m cord rule. Practice converting a floor plan into a permanent-link length and then a channel length so the two numbers are never conflated.
Mixing up multimode core/cladding sizes and their bandwidth-distance behaviour, for example assuming 62.5/125 µm and 50/125 µm OM3 fibre are interchangeable at 10 Gb/s over the same distance.
The '125 µm cladding' is common to both, so candidates fixate on the cladding and forget the core. Legacy 62.5 µm OM1 and modern 50 µm OM3/OM4 look similar on a datasheet and the distance tables are easy to skim.
What to do instead
Build a one-page table pairing each fibre type (OM1 62.5/125, OM2 50/125, OM3, OM4, OS2) with its typical source, core size, and supported reach at 1 G and 10 Gb/s. Rehearse the reason OM3 uses a VCSEL-optimized 850 nm profile rather than memorizing numbers alone.
Specifying a connector by polish style alone without matching it to the fibre type and application, e.g. pairing an APC connector with a multimode link or mating APC to UPC.
Candidates learn 'APC = low reflection, better' and apply it universally. The 8-degree angled endface is designed for singlemode return-loss control, and mating it to a flat UPC endface causes an air gap and high loss.
What to do instead
Anchor the rule: APC is singlemode only and must never be mated to UPC; colour code (green = APC, blue = UPC) is a physical interlock cue. When a question names a connector, immediately check fibre type, polish, and whether both ends match before evaluating loss.
Choosing a connector or splice method on cost or habit rather than on loss budget and environment, e.g. using field-installable mechanical splices in a high-vibration riser or selecting epoxy-polish where a pre-terminated assembly was clearly indicated.
The exam frames component selection as a trade-off among insertion loss, return loss, reliability, and installation time. Candidates who default to one familiar method skip the comparison the question is testing.
What to do instead
For each component question, list the four selection axes (loss, return loss, environment/ruggedness, termination time and skill) and score the options against them. Know typical insertion-loss values for fusion splice, mechanical splice, and factory connector so the comparison is quantitative.
Pulling cable past its rated tensile load, exceeding bend radius, or cinching cable ties tight, then answering installation questions as if these were cosmetic issues rather than causes of attenuation and latent failure.
Candidates treat workmanship as a checklist of 'looks neat' and underestimate how microbending and stress-induced cracks degrade loss over time. The damage is invisible at install and appears at test or years later.
What to do instead
Memorize the physical limits as numbers: maximum tensile load per cable type, minimum bend radius as a multiple of cable diameter (typically 10x during pull, less when installed), and the rule that ties should hold without deforming the jacket. Tie every workmanship answer back to the mechanism it prevents.
Ignoring separation from power conductors and the fill/raceway capacity rules, routing fibre in the same conduit or tray as AC wiring or overfilling a pathway without checking fill ratio.
Fibre is dielectric, so candidates assume electromagnetic interference is irrelevant and that proximity to power is harmless. They forget that safety codes, cable damage during faults, and fill limits are separate concerns from EMI.
What to do instead
Separate the two rationales: EMI immunity does not remove code-mandated separation, and pathway fill limits protect against installation damage and heat. Learn the applicable fill percentage and separation distances you were taught, and check both whenever a routing scenario is presented.
Reporting a link as 'pass' from an OLTS (light source and power meter) reading alone, or from an OTDR trace alone, without a reference method or bidirectional measurement.
Candidates equate 'I got a number' with 'I tested it'. They skip the one-jumper or three-jumper reference setup, forget to set the reference to 0 dB, and accept a single-direction OTDR trace that hides a bad connector on the far end.
What to do instead
State the test method explicitly in every answer: reference the meter to the source, record the reference value, measure both directions, and compare against the computed loss budget. For OTDR, insist on bidirectional averaging and ghost/event analysis rather than a single trace.
Building a loss budget by adding only connector and splice losses and forgetting fibre attenuation, or applying the wrong wavelength's attenuation coefficient.
Connector and splice losses are the visible events, so they dominate attention. Fibre attenuation (dB/km) and the difference between 850 nm multimode and 1310/1550 nm singlemode values are easy to omit or misapply.
What to do instead
Use a fixed budget template: (number of connectors x connector loss) + (number of splices x splice loss) + (length in km x attenuation at the specified wavelength) + margin. Compute it for the exact wavelength named in the question and compare to the measured result, not to a generic pass line.
Designing a topology that ignores the actual distance and bandwidth requirement, e.g. proposing a centralized (collapsed) architecture across a campus without checking the channel length, or omitting redundancy for a link the scenario marks as critical.
Candidates answer topology questions from a memorized preference for centralized or hierarchical designs instead of deriving the choice from the stated constraints. They also treat redundancy as a generic 'good thing' rather than a requirement tied to stated availability needs.
What to do instead
Read the scenario for the three drivers: distance, bandwidth growth, and availability. Map each to a design consequence (centralized vs. distributed, fibre count and spare strands, path diversity) and justify the choice against those drivers rather than a default preference.
Producing documentation that records cable IDs and test results but omits as-built routing, strand assignments, splice/patch schedules, and the loss-budget basis, so the record cannot support future moves, adds, or changes.
Candidates treat documentation as a formality completed after the job, so they capture only what the tester exports. The exam tests whether the record is usable by the next technician, which requires the physical and logical map, not just pass/fail data.
What to do instead
Adopt a documentation checklist: as-built drawings, labelling scheme, strand and port assignments, splice and patch schedules, test results with method and reference, and the approved loss budget. When a question describes a handover, verify each item is present and traceable to a specific cable or strand.