EXIN EPI Certified TIA-942 Internal Auditor common mistakes
EXIN EPI Certified TIA-942 Internal Auditor · Understand the traps and how to avoid them.
Treating the four Rated-4 topology levels as a single ladder where Rated-4 means 'fully redundant everything', and answering architecture questions by counting redundant components rather than by checking the fault-tolerance and concurrent-maintainability criteria that define each level.
Candidates memorise the level numbers and the word 'redundant' but never internalise that Rated-1 is single-path with no redundancy, Rated-2 adds redundant components (no concurrent maintainability), Rated-3 adds concurrently maintainable paths, and Rated-4 adds fault tolerance against a single failure. Because all four levels can contain redundant hardware, component-counting heuristics collapse.
What to do instead
Build a comparison table with one row per level and columns for: number of distribution paths, redundant components present, concurrent maintainability, fault tolerance, and typical example. For each scenario question, first ask 'can maintenance happen without shutdown?' then 'does one unplanned failure keep the load running?'; only then assign the level.
Confusing TIA-942's infrastructure Rated levels with the availability class tiers of other schemes, and answering 'what level is this design?' by importing tier definitions from a different framework.
Many candidates arrive with prior exposure to other tiered availability models and assume the numbering and criteria are interchangeable. The exam tests TIA-942's own definitions, so imported assumptions produce confidently wrong answers.
What to do instead
Before the exam, write out TIA-942's Rated-1 to Rated-4 definitions in your own words and explicitly note where they differ from other schemes (e.g. what fault tolerance and concurrent maintainability mean here). On any question, cite the TIA-942 criterion you are applying, not an external label.
Assuming the TIA-942 standard specifies detailed engineering values - exact cable distances, precise temperature set-points, or prescriptive equipment lists - and selecting answers that quote specific numbers as if the standard mandated them.
The standard is an infrastructure topology and performance document organised by functional areas (site, architectural, electrical, mechanical, telecommunications, security), and much of its content is classification and requirement framing rather than a single mandated numeric design. Candidates over-attribute specifics to the standard.
What to do instead
Learn the standard's structure by functional area and what each area covers at a high level. When a question asks what the standard requires, prefer the answer framed as a requirement or rating criterion over one quoting an arbitrary number, and flag any numeric claim you cannot tie to a named clause area.
Mixing up the functional areas and terminology - for example treating 'telecommunications spaces' and 'telecommunications pathways' as the same topic, or placing cabling topology questions under the electrical domain when answering.
The standard's chapter structure uses closely related terms (spaces, pathways, cabling, redundancy) and candidates skim the headings, so they cannot map a question to the right area or recall which requirements live where.
What to do instead
Create a one-page map of the standard's functional areas with three or four bullet keywords each (spaces = rooms/enclosures; pathways = routes between them; cabling = media and performance; electrical = distribution and grounding; mechanical = cooling). Practise classifying sample questions into these buckets before answering.
Writing audit findings as opinions or general observations ('the room looked cluttered', 'cooling seems inadequate') without stating the criterion, the objective evidence, and the resulting nonconformity.
Candidates new to auditing describe what they saw rather than structuring the finding against a requirement. Without a criterion and evidence, the finding cannot be verified or closed, and the exam tests exactly this structure.
What to do instead
Draft every finding in a fixed template: criterion (which requirement/standard clause area), condition (what was observed), evidence (document, record, measurement, interview, observation), effect/risk, and the requirement it breaches. Practise rewriting vague observations into this five-part form until it is automatic.
Designing an audit programme that is just a list of checklist items with no scope statement, objectives, criteria, sampling rationale, or resource and timing plan, then answering planning questions as if a checklist were an audit plan.
Checklists are familiar and comfortable; programme-level thinking (scope boundaries, interfaces, risk-based sampling, competence of auditors, schedule) is less intuitive and often skipped in study.
What to do instead
Learn the anatomy of an audit programme and an individual audit plan separately: programme = multi-audit cycle, objectives, risk-based prioritisation, resources, schedule; plan = scope, criteria, team, sampling approach, logistics for one audit. Write a one-page mock plan for a data centre electrical area and check it contains every element.
Relying on a single evidence type - usually document review or a quick walkthrough - and treating a vendor specification sheet or a manager's verbal assurance as sufficient proof of conformity.
Documents are easy to collect and interviews are quick, so candidates default to them. They forget that audit evidence must be sufficient and appropriate, and that design intent documents do not prove the as-built or operating state.
What to do instead
For each finding, name the evidence class used (document review, observation, interview, measurement/re-test) and ask whether corroboration is needed. Remember that a specification proves design intent only; confirming installed condition requires observation or measurement. Practise triangulating one claim with two independent evidence types.
Failing to distinguish conformity from effectiveness, and grading every finding as a major nonconformity (or every finding as an observation), with no consistent severity scale.
Candidates either lack a defined severity scheme or apply it emotionally. Without agreed criteria for major, minor, and observation, grading is arbitrary and the corrective-action logic that follows becomes incoherent.
What to do instead
Adopt and memorise a severity definition: major = absence or systemic breakdown of a required control; minor = isolated lapse with limited effect; observation = improvement opportunity with no requirement breached. Apply it to ten practice findings and justify each grade in one sentence.
Closing corrective actions on the basis of a submitted action plan or a promise, or verifying only that a document was produced, rather than verifying that the root cause was addressed and the corrective action is effective.
Follow-up is administrative and easy to treat as paperwork. Candidates confuse 'response received' with 'corrected', and skip root-cause analysis, so recurrence is not prevented.
What to do instead
Structure follow-up as: root-cause confirmed, corrective action implemented (evidence of implementation), effectiveness verified (re-audit or re-test after a defined interval), then closure. Reject action plans that only restate the problem or only correct the symptom; require the cause and the preventive change.
Treating continual improvement as a one-off corrective-action loop and ignoring trend analysis, management review, and the feedback of audit results into the next programme cycle.
Candidates see audit as a linear find-fix-close process and miss the improvement cycle: aggregating findings, spotting repeat or systemic issues, updating risk assessment, and re-prioritising the next audit programme.
What to do instead
Learn the loop explicitly: findings feed trend analysis, trend analysis feeds management review, management review feeds programme risk assessment and the next cycle's scope. Practise taking a set of five findings and writing the trend conclusion and the resulting change to the next audit programme.