PhilNITS IT Passport common mistakes
PhilNITS IT Passport · Understand the traps and how to avoid them.
Treating the IT Passport as a vocabulary quiz and memorizing Japanese term-to-English glosses (e.g., matching '仮想化' to 'virtualization') without being able to say what problem the technology solves or when it is chosen.
The exam is delivered in Japanese and many candidates study from bilingual word lists because they feel efficient; this builds recognition memory that collapses when a question asks for a scenario judgment rather than a definition.
What to do instead
For every term, write one sentence in Japanese stating the problem it solves and one contrasting term it is confused with (e.g., 仮想化 vs クラウド, RDB vs NoSQL). Rehearse explaining the pair in your own words, and only then move to the next term.
Answering calculation questions (稼働率, 伝送時間, 売上高営業利益率, 損益分岐点) by estimating or pattern-matching the answer choices instead of setting up the formula on paper.
These questions look short and the choices are often close, so candidates rush; time pressure in a 100-question, 120-minute paper rewards the fastest-feeling answer rather than the computed one.
What to do instead
Drill a fixed set of about ten formulas until you can write each from memory, then do timed mini-sets where you must show the unit conversion line (秒 vs 分, bit vs バイト, 千円 vs 円) before selecting. Never select an option that required no written step.
Misreading the direction of a question stem, for example answering what is NOT correct when asked for the correct statement, or choosing the 'most appropriate' when the stem asks for the 'least appropriate'.
Japanese stems place the negation late (「…として適切でないものはどれか」), and under time pressure the eye locks onto the topic word and skips the qualifier.
What to do instead
Circle or underline the decisive phrase (適切でない, 最も, 除く) on every question before reading the choices. If a question has no such phrase, consciously confirm it is a positive stem. Build this into a fixed per-question routine.
Studying only Technology and skipping Strategy and Management because they feel like 'business common sense' that needs no preparation.
Candidates with an engineering background assume the non-technical half is free marks, but the exam uses precise frameworks (SWOT, 3C, PPM, バランススコアカード, 損益分岐点) whose terminology and standard interpretations must be learned exactly.
What to do instead
Allocate study time explicitly across the three domains and take at least two full mock exams scored by domain. Any domain below roughly 60 percent gets its own review block before the next mock.
Confusing strategy frameworks with each other, such as using SWOT as if it generated options, mixing 3C with 4P, or treating PPM's '問題児' and '負け犬' as interchangeable.
The frameworks share vocabulary (市場, 製品, 成長) and are often learned as lists of letters rather than as tools with distinct purposes and outputs.
What to do instead
For each framework write three lines: what question it answers, what its axes or elements are, and one concrete example. Test yourself by being given a business situation and naming which framework applies and why the others do not.
Answering corporate accounting and finance items by intuition, for example assuming a higher current ratio always means healthier finances or that 減価償却 is a cash outflow.
These topics appear in the Strategy/Management area but draw on accounting conventions that IT candidates rarely use, so plausible-sounding reasoning replaces the actual definitions.
What to do instead
Learn the small closed set the exam uses: 貸借対照表/損益計算書/キャッシュフロー計算書 structure, 流動比率 and 当座比率, 減価償却 and 簿価, 損益分岐点, and 営業利益 vs 経常利益. For each, write one numeric example and one common trap.
Treating legal and compliance items (個人情報保護法, 不正アクセス禁止法, 著作権法, 労働者派遣法) as a single blur and picking whichever law name looks most serious.
The laws overlap in everyday situations, and candidates memorize names without the trigger condition that decides which law applies.
What to do instead
Build a two-column table: 'situation' and 'applicable law plus the deciding condition'. Include borderline cases such as an employee leaking customer data (company obligation vs individual crime) and copying software for personal use.
Leaving project-management and service-management questions to guesswork, for example not being able to distinguish クリティカルパス, フロート, and slack when a small network diagram is given.
These items look like arithmetic puzzles, so candidates skip the underlying concepts and then cannot interpret the diagram under exam conditions.
What to do instead
Practice a handful of small activity networks by hand: compute earliest and latest start times, identify the critical path, and state in words what a delay on a non-critical activity does. Do the same for SLA and サービスデスク terms with one example each.
Spending too long on a few hard questions early, then rushing the final block and losing easy marks on terminology and security basics.
The paper mixes difficulty, and candidates without a time policy treat every question as equally worth solving to completion.
What to do instead
Adopt a rule: if a question is not resolved after about a minute, mark it, pick the best current option, and return later. Practice this in timed mocks so the habit is automatic, and reserve the last ten minutes for marked items.
Reviewing mock exams by reading the correct answers only, without recording why the chosen wrong option was attractive.
Recognition of the right answer feels like learning, but the exam penalizes the specific distractor patterns you fall for repeatedly, and those patterns are invisible unless you name them.
What to do instead
Keep an error log with four columns: question topic, my answer, correct answer, and the reason the distractor was tempting. Group the log by distractor type (unit trap, reversed condition, near-synonym term) and review the log before each new mock.