C-NNIC common mistakes
C-NNIC · Understand the traps and how to avoid them.
Treating the 100 m channel limit as a single cable-length rule and ignoring that patch cords, equipment cords, and consolidation point cabling all count toward the channel budget.
Candidates memorize '100 m horizontal run' and apply it only to the permanent link, then oversize designs or approve installs where the total channel exceeds limits once cords are added.
What to do instead
Always compute the full channel: permanent link plus work-area cord plus patch cord plus any consolidation point or MUTOA allowance. Practice drawing a channel end to end and labeling each segment's length before judging compliance.
Confusing permanent link and channel test limits when interpreting certification results, accepting a passing permanent link as proof the channel will pass.
Permanent link testing excludes patch cords and the far-end connection, so margins look better; candidates forget the field tester's adapter configuration changes the limit set being applied.
What to do instead
Learn which adapter and limit each test type uses, and read the tester's reported limit name before declaring pass/fail. When qualifying a channel, test with channel adapters and cords installed.
Selecting cable category by habit rather than by the distance, bandwidth, and environment requirements stated in the scenario.
Candidates anchor on the most familiar media type and skip the calculation of supported distance at the required data rate, or ignore alien crosstalk and shielding needs in high-EMI or bundled runs.
What to do instead
For each scenario, write down data rate, distance, bundle size, and EMI exposure first, then match to a media type and confirm the standard's supported distance and frequency. Reject any choice that cannot meet the stated distance.
Mixing up T568A and T568B pin/pair assignments or miswiring one end, producing a crossover or split pair that the candidate then misdiagnoses.
The two assignments differ only in which pairs land on pins 1-2 and 3-6, and candidates memorize color orders visually without understanding the pair-to-pin mapping.
What to do instead
Memorize pair-to-pin mapping for both assignments and practice identifying split pairs from a wiring diagram. On test questions, trace each pair from pin to pin rather than reciting colors.
Ignoring separation-from-power and bend-radius/bundle-fill rules when routing cable, then choosing a pathway that violates them.
Pathway questions look like topology questions, so candidates focus on route efficiency and forget that EMI separation, fill ratios, and minimum bend radius constrain the acceptable route.
What to do instead
Build a checklist for any pathway decision: separation from power, bend radius, fill capacity, support spacing, and fire-rated barrier crossings. Apply the checklist to every routing option before selecting.
Treating codes and safety items as generic common sense instead of citing the specific requirement for firestopping, plenum ratings, grounding/bonding, or marking.
Candidates study the technical cabling content heavily and skim the codes domain, so they cannot distinguish which rule applies to a penetration, a plenum space, or a telecommunications bonding backbone.
What to do instead
Create a one-page matrix mapping each hazard (plenum, riser, penetration, grounding, labeling) to its governing requirement and the acceptable materials. Review it until the mapping is automatic.
Designing topologies without accounting for redundancy, single points of failure, or the distance limits that force a tier or media change.
Candidates draw a logically correct star or hierarchical design but forget that the physical layer imposes distance and media constraints that change which topology is feasible.
What to do instead
After sketching a topology, annotate each link with media, distance, and device, then check for single points of failure and any link exceeding its supported distance. Revise before answering.
Misapplying power and cooling calculations for racks and equipment, such as ignoring derating, airflow direction, or UPS load versus circuit capacity.
Candidates treat power as simple addition and overlook that circuit capacity, continuous-load derating, and hot-aisle/cold-aisle airflow determine whether a rack design is valid.
What to do instead
Practice computing rack load with derating applied, confirm airflow direction compatibility for installed equipment, and verify circuit capacity against continuous-load rules before approving a layout.
Skipping the pre-test verification steps and jumping straight to interpreting a failed certification result, then blaming the cabling instead of the test setup.
Candidates want to diagnose the cable, but many failures come from wrong adapter, wrong limit, bad reference, contaminated connectors, or excessive cord movement during the test.
What to do instead
Adopt a fixed sequence: verify tester reference, correct adapter and limit, clean and inspect connectors, stabilize cords, then test. Only after setup is confirmed should you interpret results as cabling faults.
Answering installation-practice questions from general construction intuition rather than the cabling-specific rules for support spacing, pulling tension, and cable management.
Candidates have real-world building experience that conflicts with telecommunications cabling requirements, so they apply the wrong spacing or tension values.
What to do instead
Study the specific support spacing, maximum pulling tension, and management requirements for each cable type and commit the numeric values to memory with a short reference card for review.