How to Pass the Applied Information Technology Engineer Exam (Afternoon Section) in Japan: Subject Selection, Past Exam Questions, and 150-Minute Strategy

The afternoon section of Japan's Applied Information Technology Engineer Exam (応用情報技術者試験) demands far more than textbook knowledge. You pick 5 out of 11 questions, work through dense case-study passages, and convert your understanding into written answers — all within 150 minutes. When your subject selection, your approach to past exam questions, and your time management on exam day aren't working together, the 60-point passing line stays out of reach.

This article is for anyone who freezes up during the afternoon section, or who passes the morning section easily but plateaus on the written portion. It lays out a single, connected strategy: subject selection anchored by the mandatory Information Security question (Question 1), a weekly past exam questions cycle you can actually sustain, and a 150-minute game plan built around 30 minutes per question. Japan's IPA (Information-technology Promotion Agency) has confirmed that the 2026 CBT transition won't change the question format, number of questions, or exam duration — so the core preparation stays the same. You just need to add practice reading and typing on a PC screen.

What Is the Afternoon Section? Exam Format and Passing Criteria You Need to Know First

Exam Format

The afternoon section of the Applied Information Technology Engineer Exam isn't a multiple-choice knowledge test. It's a long-form case-study exam where you read scenarios and write answers that address each question's specific requirements. Under the current paper-based format, you have 150 minutes to answer 5 out of 11 questions. The breakdown matters: Question 1 (Information Security) is mandatory, and you choose the remaining 4 from the elective pool.

What catches people off guard is that 5 questions doesn't mean light. Each question carries substantial density. With 150 minutes for 5 questions, the simple math gives you about 30 minutes per question. But in practice, those 30 minutes have to cover reading the passage, checking diagrams and tables, parsing what the question actually wants, drafting your written answer, and reviewing it. Most people who struggle with the afternoon section aren't just lacking knowledge — they walk into the exam without a clear plan for how to slice up their time against the volume of text.

Despite the long-form format, this isn't a pure reading comprehension exercise. System architecture diagrams, business workflows, design constraints, incident scenarios, and operational assumptions are woven into each passage. You have to extract evidence for your answers from within that material. Questions come in forms like "state the reason," "describe an appropriate response," or "fill in the blank" — requiring you to apply knowledge and reading comprehension simultaneously. The afternoon section is, in essence, designed to mirror the real-world skill of reading specifications and design documents, then making decisions under constraints.

IPA has stated that with the planned CBT transition from 2026, the scope of knowledge and skills tested, the question format, the number of questions, and the exam duration will remain the same. The fundamental challenge of the afternoon section isn't changing. Whether you're working on paper or a screen, what's being tested is still your ability to read through lengthy passages, extract relevant information, and convert it into answers that earn points.

{{OGP_PRESERVED_0}}

Passing Criteria and How Results Are Determined

The passing standard is straightforward: score 60 or above out of 100 on both the morning and afternoon sections. However, how results are determined in practice requires some care. Many unofficial study guides explain that if your morning score falls below the threshold, your afternoon score effectively doesn't count toward the final determination. For the precise details, refer to IPA's official exam information page. From a test-taker's perspective, clearing the morning threshold is a prerequisite, so aim to consistently get at least 48 morning questions correct to be safe.

For the afternoon section, thinking of each of the 5 questions as worth roughly 20 points helps you plan your scoring. Actual grading is done at the sub-question level, but this mental model highlights how "fully nailing one question counts for a lot" and "collapsing on one question hits hard." Since a single poor subject choice or time crunch can become a large block of lost points, a practical mindset is to aim for 3 strong questions and use the remaining 2 for additional points — even though the passing line is 60.

Morning/Afternoon and Subject Group A/B Terminology

If you've been following the exam reform news, you've probably noticed two naming conventions floating around: "morning" and "afternoon" versus "Subject Group A" and "Subject Group B." This article uses morning/afternoon, since that's still the terminology most test-takers recognize. After the 2026 CBT transition, IPA's official materials will use Subject Group A/Subject Group B.

The mapping is simple: what's currently called the morning section corresponds to Subject Group A, and the afternoon section corresponds to Subject Group B. The names are changing, but as mentioned, the question format, number of questions, and exam duration are staying the same — so your study preparation carries over directly. Particularly for afternoon-focused articles, practice materials, and conversations among test-takers, "afternoon section" will remain the more natural term for a while.

Think of this terminology gap as a transitional artifact. When you encounter "Subject Group B" in IPA's official documentation, the actual content you're preparing for is the same long-form, case-study, 5-question "afternoon section" it's always been. There's no reason to let the naming difference cause confusion — just remember that afternoon section = Subject Group B equivalent and move on.

For the overall picture of the Applied Information Technology Engineer Exam and where the reform fits in, IPA's official exam page is the clearest source. Note that while the Fundamental Information Technology Engineer Exam (基本情報技術者試験) has already undergone major changes to its Subject B structure, the Applied exam is expected to retain its long-form, written-answer character after the CBT transition — keeping that distinction in mind prevents mix-ups.

{{OGP_PRESERVED_1}}

Why the Afternoon Section Is Difficult — And It's Not Just About Knowledge Gaps

What trips people up on the afternoon section isn't simply missing knowledge — it's the inability to extract the specific conditions each question requires from within a lengthy passage. The text blends specifications, business workflows, architecture diagrams, and operational constraints into a case-study format. Reading it can give you a sense of understanding, but points only come when you accurately identify what each question is actually asking. In text-heavy questions, even a careful read becomes wasted effort the moment you miss the subject or conditions specified in the question — that reading time essentially converts into lost points.

The real sticking point isn't reading ability per se, but matching questions to the right parts of the passage. Whether a question asks for "the reason" versus "the countermeasure" changes which evidence you need. Overlooking qualifying phrases like "the most appropriate," "after the change," or "from the user's perspective" means your answer might be technically correct knowledge but still not score well. On the afternoon section, writing something true but unasked-for won't earn you points.

Behind this misalignment is often insufficient practice with past exam questions. Test-takers who haven't worked through enough past papers lack the instinct for reconstructing "which part of the passage supports which answer." Among the candidates I've observed, plenty can handle knowledge-based question banks but freeze on the afternoon section. When you trace the cause, it's rarely that they don't know the terminology — it's that they haven't built a reliable process for returning to the passage and locating evidence after reading a question.

The afternoon section's problem booklet contains a substantial volume of text, and processing multiple large questions in 150 minutes requires intentional reading order. Scan the questions first to identify the focal points, then read the passage while searching for relevant sections. Without this back-and-forth habit, you end up reading the entire passage before attempting the questions — and losing time. When you approach the passage without a clear grasp of what the questions want, the result is better described as a search failure than a comprehension failure.

The Traps of Time Allocation and Question Selection

The afternoon section gives you 150 minutes for 5 questions — 30 minutes each on paper. The tricky part is that equal distribution doesn't actually work. In reality, those 30 minutes need to cover grasping the question requirements, reading the passage, building your answer, and reviewing it. Some people rush through questions and skip conditions; others over-invest in a single question and watch the back half crumble. Both speed-running and over-commitment cause lost points — that's what makes the afternoon section so demanding.

The classic pattern is spending more time than planned on your first question. The more promising a question feels, the more you want to push through it. But with each question worth roughly 20 points, fixating on one doesn't optimize the whole. Spending 35 or 40 minutes chasing one answer can leave you without enough time to even read a later question — resulting in blanks or incomplete attempts. This isn't a knowledge failure; it's a self-inflicted time management collapse.

Equally significant is poor subject selection. In a format where you choose 5 from 11, which subjects you pick directly determines your scoring strategy. A common mistake is choosing based on vague reasoning: "I work with networking a bit, so I'll pick that" or "I studied databases before, so that should be fine." Work experience can be an advantage, but it doesn't guarantee compatibility with the exam. Networking might focus on subnetting and routing one year, then shift to architecture design and incident isolation the next. Database questions vary between SQL-heavy years and design-heavy years. Subject selection errors happen not from ignorance, but from misjudging compatibility.

To reduce this risk, you need to test candidate subjects across multiple years of past exam questions and verify whether your performance stays stable despite year-to-year variation. A subject where "I scored well once" is less reliable than one where "I scored consistently across 2-3 different years." The afternoon section throws unseen year-to-year variation at you on exam day, so single data points aren't enough for committing to a subject. Insufficient subject preparation surfaces as time loss the moment you open the problem booklet.

For time allocation priorities, the first step is establishing criteria for when to move on. You can't find evidence in the passage, you can't determine the direction for your written answer, you're stuck on a calculation. Persisting in any of these states doesn't just cost you that question — it drags down the remaining ones. Test-takers who consistently score well on the afternoon section aren't perfectly answering hard questions; they're quickly separating questions they can finish from questions they should abandon.

Written Answer Templates and Scoring Points

The afternoon section doesn't reward writing whatever you know. What gets scored is whether you've included the required elements in the format the question specifies, without excess or omission. This is where writing approach makes the difference. Even when the content isn't far off, sloppy word choices, disconnected subjects and predicates, or poorly scoped answers lead to lost partial credit.

For instance: writing a countermeasure when the question asked for a cause, describing an administrator's benefit when the question asked about the user's perspective, or paraphrasing instead of using the specific terminology from the passage. These mismatches aren't knowledge problems — they're template deficiencies. Afternoon scoring heavily weighs whether your answer format matches the question's required verb: reason, purpose, improvement measure. If it doesn't read as the type of answer requested, points don't attach.

Looking at IPA's model answers and scoring commentary, what's valued isn't elegant prose — it's having the required evaluation criteria covered. That's why building written answers as short sentences anchored by keywords is so effective. My approach is to structure afternoon answers in a conclusion-then-reason order. Place the conclusion that addresses the question first, then support it with reasoning drawn from the passage. This template keeps subjects and predicates clean and reduces punctuation and phrasing errors.

Calibrating length matters too. Too short and you drop essential elements; too long and you introduce irrelevant content. Answer scripts from people who plateau on the afternoon section tend to fall into one of two patterns: "stuffing in everything they know" or "writing too little out of caution." The approach most likely to pick up partial credit is one that hits the question-relevant terms, stays within what the passage can verify, and connects them concisely.

If writing is your weakness, you might be tempted to just read model answers. But what actually works is comparing them against your own answer and identifying the gaps. What did you leave out? Which term was missing? Why did your subject shift? Without breaking it down to that level, you'll repeat the same mistakes on the next past paper. The priority order for afternoon preparation is: rather than adding more memorization, use past exam questions to reconstruct question-passage mappings and solidify your writing template. Knowledge is the foundation, but what determines whether you reach the passing score is your ability to convert that knowledge into a form that earns points.

Subject Selection Decides Your Afternoon Score: How to Choose

Your Selection Framework

For afternoon subject selection, start by fixing the non-negotiable. Question 1 (Information Security) is mandatory, so it's not a subject you decide whether to attempt — it's your top-priority topic to master. From there, how you compose your elective lineup becomes the heart of your scoring strategy.

A common mistake is choosing based on reputation alone: "I read online that this subject is easier to score on" or "everyone recommends Database." The afternoon section requires reading long passages, finding evidence, and writing answers tailored to each question — so general "easy subject" rankings and your personal "easy subject" are different things. Among the test-takers I've advised, this mismatch comes up constantly. Those who have the knowledge but can't raise their scores are almost always treating subject compatibility too casually.

When narrowing candidates, evaluating along three axes — work experience, scoring potential, and interest — makes decisions clearer. Subjects where you have work experience are easier to visualize: you can picture the scenarios and follow terminology relationships more naturally. If you have infrastructure experience, Networking becomes a natural candidate; if you've worked with SQL and design, Database is worth considering. Even a business-oriented subject like System Strategy can feel approachable if you're used to requirements discussions and process improvement conversations.

But work experience alone isn't sufficient. Networking might have straightforward subnetting and routing one year, then shift toward architecture design and incident isolation the next. Database questions feel different depending on whether SQL or design-perspective reasoning dominates. That's why you need a separate axis for scoring potential: Can you grasp the question's intent from the passage? Can you locate evidence easily? Does your answer reliably pick up partial credit? Missing this dimension means even experienced professionals can collapse on exam day.

Interest shouldn't be dismissed either. Afternoon prep involves repeatedly reading past exam questions, and subjects that don't interest you tend to get shallower study attention. Conversely, topics that engage you — even if challenging — leave terminology connections in your memory more naturally, and you'll actually complete review cycles. Even without deep work experience, if a subject interests you and you're getting traction with past papers, that's enough to compete.

Compatibility Check: A 2-3 Year Evaluation Process

You can't assess compatibility by thinking about it — you need to actually solve 2-3 years of past exam questions. IPA's official past exam archive provides problem booklets, model answers, and scoring commentary for each year, giving you plenty of material to test candidate subjects across different years.

What to look for goes beyond simple correct-answer rates. The factors I prioritize are readability, ease of evidence extraction, and score stability. Readability means whether the actors, system architecture, and problem flow naturally enter your mind as you read. Ease of evidence extraction means whether you can quickly sense "the answer is probably in this paragraph" when you see the question. Score stability means whether your performance holds up when the year changes, not just whether you scored high once.

The evaluation process is simple. Pick a candidate subject, solve 2-3 different years. Each time, look beyond just whether you got it right — note where you spent time, what made you hesitate, and what type of passage content tripped you up. For Networking: was it the calculations or the architecture diagram reading? For Database: was it the SQL itself or explaining design intent? For System Strategy: was it terminology knowledge or rephrasing business perspectives? Decomposing your sticking points this way reveals whether you're dealing with a fixable weakness or a fundamental compatibility issue.

After this process, narrowing to 3 or more subjects is practical for exam day. Locking in just 1 or 2 too early exposes you to year-to-year variation. Spreading too wide scatters your study effort. The afternoon section's selection flexibility means going too narrow or too broad both cause problems. If after 2-3 years of testing you find a subject consistently hard to read, with elusive evidence, or with scores that swing wildly between years — drop it from your lineup regardless of its reputation.

{{OGP_PRESERVED_2}}

The 3-Fixed-Plus-1-Backup Design and When to Update

The strongest exam-day configuration is 3 fixed subjects plus 1 backup. With Information Security as your anchor, you prepare 3 primary elective subjects and keep 1 additional subject ready as insurance. Preparing 4 subjects total lets you survey the problem booklet on exam day and avoid whichever question has unfavorable year-to-year variation.

This works because the afternoon section isn't just about "what you know" — it's about "whether this year's questions align with your preparation." With only 3 fixed subjects, hitting a year where one of them is unusually difficult leaves you with no escape route. With a backup, you can assess the full lineup and think, "This year, my backup looks more manageable than Primary B" — and switch. The key principle isn't spreading thin, but keeping your primaries deep while maintaining the backup at a viable level.

Establish update rules so you don't waffle. The criterion for a fixed subject: stable readability and scoring across 2-3 years. The criterion for backup: not as strong as your primaries, but capable of holding its own in favorable years. If, during your practice cycle, one fixed subject becomes consistently shaky, don't cling to it — swap it with the backup. Subject selection shouldn't be a one-time decision; it should be a design you update based on past exam question results.

What you want to avoid: relying on a single subject with high year-to-year variance as your ace. A subject that happened to go well once can cause outsized damage when it doesn't on exam day. Also avoid charging in without a backup because "someone said this combination is easy to score on." The afternoon section rewards the ability to make smart choices after opening the problem booklet, so preserving optionality on exam day directly translates to stability.

How You Use Past Exam Questions Determines Pass or Fail: A Concrete Afternoon Prep Sequence

First Pass: Untimed Evidence Reconstruction

For afternoon past exam questions, jumping straight into timed practice isn't the best opening move. On your first pass, focus on deconstructing "how reading translates into points." Rushing through under time pressure makes it hard to distinguish whether a wrong answer came from a knowledge gap or sloppy evidence extraction. My recommendation for the initial run is to skip the timer entirely. Start by briefly scanning the questions to understand what type of answer each one requires, then read the passage. Just knowing upfront whether you need a cause, an effect, or a countermeasure dramatically changes which parts of the passage deserve your attention.

Once you start reading the passage, don't just skim through it. Consciously identify, paragraph by paragraph, where evidence relevant to the questions might be. Business workflow descriptions, incident trigger conditions, table value changes, architecture connection points — mark anything that looks like raw material for an answer. The important thing here isn't "getting the right answer" but "being clear about which evidence you used." Afternoon questions are less about writing knowledge directly and more about reassembling facts from the passage and diagrams to match what each question demands.

After you finish, use the problem booklet, model answers, and scoring commentary available on IPA's official past exam page to verify whether your answers and evidence aligned. Don't just check right or wrong. Even a correct answer based on the wrong evidence won't be reproducible when the year changes. Conversely, if you found the right evidence but your phrasing was weak, that's a fixable loss.

Then comes the essential step: reconstructing the mapping between questions and passage. For example: "Question 2's cause is in the incident conditions in paragraph 3," "Question 4's countermeasure involves the architecture change in Figure 2 and the operational constraint in paragraph 5." Map question numbers to paragraph numbers, figure names, and keywords. People who are strong on the afternoon section do this automatically in their heads. During your first pass, the goal is to externalize that thinking onto paper or notes.

Second Pass: Time-Boxed Drills

Once you can reconstruct evidence mappings, the next step is building processing speed. The afternoon section requires roughly 30 minutes per question, so your second pass introduces time constraints to compress the read-search-write cycle. Jumping straight to perfecting each answer under pressure will frustrate you, so time-boxing — measuring how far you get within a fixed window — is more practical.

A manageable format is solving 2 questions in 60-75 minutes. Single-question practice doesn't replicate the sustained processing of exam day, while a full 5-question session is too heavy. Two-question sets reveal patterns: did you overspend on the first question? Did your reading speed drop on the second? What matters here isn't knowledge volume but where the flow breaks down — from question preview through passage reading, evidence extraction, to answer drafting.

Time-boxed drills are where the evidence maps from your first pass pay off. Once you can quickly recognize what type of passage information a question verb points to, wasteful re-reading decreases. For Networking, faster diagram-to-passage matching; for Database, quicker table-to-SQL-condition linking; for System Strategy, rapid identification of current-problem-to-improvement-effect pairings — each speeds up your processing time.

Your review approach changes too. On the second pass, record not just "why you got it wrong" but "why it took so long." Did you misread the question and have to backtrack? Couldn't locate the evidence? Struggled to articulate your answer? Without this breakdown, trying to go faster just means repeating the same bottleneck. People whose afternoon scores improve track their processing log, not just their correct-answer rate.

Organizing Recurring Patterns

After working through several years of past exam questions, you start noticing that the same question types recur across different subjects. From this point, you need to stop treating each question's review in isolation and start bundling them as recurring patterns. This is less about adding knowledge and more about creating answer-building templates.

Three categories are worth organizing. First is terminology. Expressions like "availability improvement," "load distribution," "exclusive control," and "internal controls" appear repeatedly in model answers. Trying to rephrase these in your own words usually weakens them — keeping them ready-to-deploy as-is is stronger. Second is how to read diagrams and tables. Architecture diagrams have connection relationships, tables have comparison axes, business flows have current-versus-improved state differences — the reading focus becomes predictable per diagram type. Third is question-requirement types: the writing distinctions between "state the cause," "describe the effect," "explain the reason," and "propose an improvement" mapped to their required verb forms.

The point of this organization isn't creating beautiful notes. It's consolidating into a personal reference sheet you can reuse on the next question. For example: "Cause-type answers need both the phenomenon and the condition," "Effect-type answers need what was done and what improved," "Countermeasure-type answers need the target and the method as a pair." Converting these into checklist items reduces drift from scoring criteria. IPA's model answers and scoring commentary are practical tools for finding these templates. Don't just read the model answer — trace what the scoring commentary identified as insufficient. That's what sharpens the outline of point-earning expressions.

Alongside this, fixing a format for your error log improves review efficiency. Keep it simple enough to sustain, but question requirement, evidence location, your answer, gap versus model answer, and prevention checklist are hard to omit. This format lets you see whether a mistake was "I didn't know the material," "I missed the passage evidence," or "my phrasing didn't meet the scoring criteria." Making these distinctions visible is what drives afternoon section improvement.

Weekly Cycle

What separates effective past exam question practice isn't just the quality of each session — it's whether your weekly routine is structured. The afternoon section benefits more from distributing practice across the week than from single marathon sessions. A pattern I find effective: question-level drills and review on weekdays, full-length integrated practice on weekends.

Weekdays work best for slicing individual questions: "What is being asked?" "Where is the evidence?" "How should I write to earn points?" Even if you can't find large blocks of time in the evening, question-level work lets you complete the reconstruction process. During this phase, weight review heavier than practice. Read IPA's model answers and scoring commentary across multiple years, identifying which evaluation criteria recur within the same subject. Looking only at the problem booklet and stopping there means you never see what the exam creators are actually evaluating.

Weekends are for full 150-minute practice runs that simulate exam-day processing order. Here, track not just correct answers but which order you chose, where you lost time, and whether your concentration held in the second half. Breakdowns during full runs become the targets for weekday question-level reinforcement the following week. The cycle is: practice, review, re-practice — not just practice and stop. Afternoon questions don't stick until you complete that re-practice loop.

When running a weekly cycle, making progress visible is essential. Track how often the same error type appears in your log, which subjects have the most question-requirement misreads, which years trigger time overruns. This lets you chase weaknesses with data rather than feelings. Afternoon prep doesn't improve just from the sense that you've put in volume — the real indicator is whether you're reducing the same mistakes. Past exam questions aren't disposable drill material; they're training tools for internalizing question-passage mappings, scoring criteria, and expression templates. That's what connects most directly to your pass/fail outcome.

How to Avoid Disaster in 150 Minutes on Exam Day: Reading Order and Time Allocation

Opening Minutes: Preview and Full Survey

The first thing to do on exam day isn't diving into the passage. Start by briefly scanning each question to understand what type of answer it requires. The rule here is don't go deep. Identify the required format and output type — "Is it asking for a term?" "A number?" "A written explanation of a reason?" — and stop there. If you start hunting for evidence at this stage, you'll bleed time right from the opening minutes.

Since the afternoon section has you choosing 5 from 11, this initial decision directly determines your scoring stability. I think of this time not as preparation for answering, but as design time for the entire 150 minutes. What you're evaluating during the question preview isn't a vague sense of difficulty, but whether each question's requirements match your processing strengths. For Networking: can you work through the diagram-to-condition mappings? For Database: can you handle the SQL and table reasoning? For System Strategy: can you articulate current problems and improvement effects?

From there, spend the first 10-15 minutes surveying the full set and lock in your 5 questions including Question 1. At this stage, the selection criterion isn't "I can probably solve this" but "I can produce a completed answer within the time limit." Picking 5 manageable questions beats gambling on 1 hard one every time on the afternoon section.

To prevent oversight, leave marks or short notes on the problem booklet. Circle the questions you'll attempt, triangle the maybes, and mark the skip candidates. Adding brief notes like "has numerical calculations," "writing-heavy," or "diagram-focused" makes it faster to revisit if you need to reconsider your choices mid-exam. The afternoon section rewards not just reading ability but any technique that lowers your cognitive load — and that directly becomes scoring power.

Solving Order and When to Cut Your Losses

Once you've picked your 5, fix your solving order. The recommended sequence is: stable subject first, then questions with the most scorable sub-questions, then backup subject last. Starting with a question you can reliably finish establishes your answer-writing rhythm. Starting with an uncertain question risks depleting your energy on question one and dragging down everything after it.

In practice, anchor on Question 1 (Information Security) and front-load the subjects where your past exam question results have been most reproducible. For example, if Networking or Database — where diagram-to-passage matching is relatively straightforward — is your stable subject, put it early. If System Strategy — where you organize and articulate arguments — is your strength, slot it into the middle. The key is ordering by processing stability, not preference.

Where exam-day performance diverges most is the response to unexpectedly difficult questions. You can't find the focal point from the questions, the evidence structure in the passage isn't visible, it's taking too long just to start writing. When any of these three signals appear, the 3-minute rule applies: move on and come back later. Pushing through at this point feels like you're almost there — but what's actually happening is you're cannibalizing time from questions you could have scored on.

For questions you've set aside, don't abandon them entirely. Leave a one-word note on the problem booklet — "return," "re-read" — so you can pick up quickly if time allows. Even this small marker speeds up your restart when you come back. In real-world incident response, marking where you got stuck and moving on with the triage usually produces better outcomes than tunneling into one issue — the afternoon section works the same way. Solving order isn't something you change on a whim; it's a procedure you fix in advance for repeatability.

Time Allocation Model and Review Checklist

Splitting 150 minutes evenly at 30 per question seems logical, but in practice, carving out separate time for the initial survey and final review stabilizes your performance. What I've found effective is allocating the overall survey first, then assigning processing time to each question.

A workable standard model is: 10-minute survey + 25 minutes x 5 questions + 15-minute review. If your strengths and weaknesses are well-defined, an asymmetric model also works: 15-minute survey + 28/22/25/25/20 minutes + 15-minute review, adjusting based on your processing speed per subject rather than theoretical point values. What both models share is reserving the 15-minute review upfront. "Review if there's time left" doesn't work — building it into the plan from the start prevents collapse on exam day.

Within each question, further subdividing time helps you stay on track. Roughly: the first portion for grasping the question and mapping it to the passage, the middle for writing your answer, the end for formatting and checking. The critical point is: don't immediately jump to the next question after writing. Even 30 seconds of condition verification makes a difference. Afternoon section point losses frequently come not from ignorance but from missed conditions.

During review, using a fixed checklist beats scanning by feel. Two main areas to check: question conditions, and answer formatting.

Negative phrasing is particularly treacherous. Questions like "which is NOT appropriate" or "which is unnecessary" can trip you into answering the opposite of what's asked even when you understand the material. For numerical questions, verify units; for written answers, confirm whether the question asked for a "reason," "effect," or "countermeasure" and match your sentence ending accordingly. Answer formatting might seem minor, but ambiguous terminology or tangled sentence structure can prevent correct knowledge from converting into points.

The afternoon section is a contest that runs from knowledge through to the written answer sheet. That's why running a consistent sequence on exam day — "briefly preview questions," "survey the full set and pick 5," "apply the 3-minute rule," "preserve review time" — in the same order every time builds resilience. People with a repeatable procedure experience smaller collapses even in difficult years.

How to Stop Losing Points on Written Answers: Writing Techniques from IPA Model Answers

Reading Questions Without Missing Conditions

Afternoon section point losses often stem not from missing knowledge, but from dropping a single question condition. "Conditions" here means instructions like "state the reason," "propose a countermeasure," "explain from the user's perspective," or "answer using terms from the passage." Content that's correct but doesn't match the question format won't score well.

Something worth noting: the afternoon section isn't all written answers. In practice, questions also include single-word entries, symbol selections, number entries, and numerical calculations. That's why you need to confirm "what format to answer in" before deciding "what to answer." Writing an explanation in a field meant for a single term, or copying passage text for a question asking for a number, creates avoidable losses. The simpler the expected answer, the more discipline you need to not add extra.

When reading questions, parse the requirements before deep-reading the passage. The checklist is short: Who is the question about? What is it asking for? Cause, effect, or countermeasure? Is there a scope restriction? Any negative conditions? Running through this sequence alone reduces misreads. During my own afternoon practice, just marking the verb in each question noticeably reduced answer drift. "List" and "explain" look similar but require different levels of detail.

Negative and exception conditions also bite if overlooked. Questions phrased as "which is NOT appropriate" or "which is unnecessary" can cause reversal errors even when you understand the content. IPA's model answers consistently feature answers that precisely match the question's requirements rather than flashy writing. Put differently, afternoon written answers aren't essays — they're closer to conditional information extraction.

People who consistently nail question conditions aren't those who read the most — they're those who fix the question's template before searching for evidence. In software development, misreading requirements derails the implementation; the afternoon section works the same way — question comprehension determines answer quality.

Short-Answer Templates and Term Selection

To score consistently on written answers, keeping required terms intact while writing short beats writing long. The afternoon section isn't a prose competition. What matters is that the scorer can immediately see "this answer satisfies the question's requirements."

A practical template is building the skeleton from "who / what / why / does what." For a countermeasure question: "The administrator modifies the firewall rules to restrict communication to the externally published scope." Subject, action, purpose — lined up simply, and the answer tightens itself. For cause questions, substitute "what caused" + "what resulted." For effect questions, "what was done" + "what improved." These substitutions cover most question types.

The important thing isn't copying passage text wholesale — it's preserving the core terms while restructuring. Verbose connectors and subjective phrasing almost never help on the afternoon section. Strip out hedging expressions like "it seems that," "it is thought that," or "better" — instead, build short sentences around passage keywords. That produces an answer the scorer can evaluate efficiently.

Formatting details also create gaps. Sentences with too many commas become hard to parse; sentences with no breaks obscure meaning; sentences where subject and predicate are separated and tangled fail to communicate even correct understanding. Also, using "login credentials" in your answer when the passage says "authentication information" introduces inconsistency that looks sloppy. IPA model answers tend to be concise, terminologically consistent, and low on unnecessary modifiers. That's worth emulating.

During study, place the model answer beside your own and don't let the differences slide past you. Focus specifically on: are the essential terms present, are there extraneous terms, and does the answer match the required perspective? Highlighting the gaps in your own answer and keeping records of them reveals why "my content was close but my score didn't rise." People who consistently run this gap analysis are the ones whose afternoon writing suddenly stabilizes.

Pitfalls with Single-Word, Number, and Symbol Questions

Afternoon prep tends to focus on written explanations, but single-word entries, symbol selections, number entries, and numerical calculations also create point gaps. Here, faithfulness to the question format directly becomes your score rather than writing skill. Ironically, people strong at written answers often handle these sub-questions carelessly and drop points.

For single-word entries, determine whether the question wants a technical term or an expression from the passage. If the question says "using terms from the passage," don't substitute with similar words from your own knowledge. Conversely, if it asks for a general term, writing a long passage excerpt is a format violation. The shorter the expected answer, the more important it is not to add extra words.

Number and symbol questions also cause accidents when you rush through them with elimination alone. Even when you know the options, "the most appropriate" versus "which is NOT appropriate" flips the answer. After reading lengthy passages, conditions can swap in your head. For questions like these, re-reading the question condition right before writing your answer is an effective habit.

For numerical questions, the calculation itself is usually less problematic than units, digits, rounding methods, and required notation format. In Networking or Database questions, for instance, having the right reasoning but dropping the unit, or writing an intermediate value when the question asks for an integer, becomes a deduction point. Numerically strong people tend to stop once they reach the answer mentally and move on — pausing to confirm "what to write, in what format, to what precision" stabilizes results.

These question types look lighter than written answers, but they're actually reliable point sources. While the afternoon section demands reading comprehension for each large question, the answer sheet also rewards the accumulation of strict format compliance on these smaller items. Control excess and omission on written questions; don't miss the output format on single-word, number, and symbol questions. When both are in place, your afternoon answer quality steps up a level.

What Changes with the 2026 CBT Transition? What Stays the Same in Afternoon Prep

What Stays the Same

Hearing "CBT transition" might make you feel like the afternoon section is becoming a completely different exam. This is where you want to pause and organize. IPA has indicated that after the 2026 CBT transition, the knowledge scope, question format, number of questions, and exam duration will remain the same. That means the foundations of afternoon prep — subject selection, long-passage reading, writing answers matched to question requirements — remain fully valid.

This is significant. Even as the delivery shifts from paper to computer, the essence of what the afternoon section tests doesn't change. Anchor on Information Security, solidify your elective subjects where you score well, use past exam questions to learn question patterns, extract evidence, and write concisely. This flow continues as before. As discussed, the afternoon section rewards precise answering under conditions more than writing ability. That doesn't shift with the testing medium.

Think of it in practical terms: whether you read a specification document on paper or on screen, misunderstanding the requirements means your design goes wrong. The afternoon section is similar — what determines point differences is whether you can match questions to evidence, not whether the medium is paper or digital. If the uncertainty feels strong, start by grounding yourself in the fact that "the center of your study doesn't need to change."

What Does Change

On the other hand, the test-taking experience definitely changes. The biggest shift is reservation-based scheduling. Through the 2025 exam year, the paper-based test runs twice annually (April spring session, October autumn session) on fixed dates. From 2026 onward, multiple testing dates within a designated period are planned, with test-takers selecting their venue from locations across Japan. Study planning shifts from "one fixed exam date" to "count backward from my reserved date."

An easy-to-overlook change is on-screen reading during the afternoon section. Paper booklets let you annotate margins, move your eyes freely across pages, and flip between diagrams and text. With CBT, you navigate information on a PC screen. Even with the same text volume, reading fatigue manifests differently on screen versus paper. Since the afternoon section specifically requires processing long passages with evidence-based reasoning, building comfort with "tracking where information is located on screen" is worthwhile.

The other change is keyboard input. Since the written-answer format is being maintained, you'll need to get comfortable entering answers on screen. Paper allows micro-adjustments to your thinking as you write by hand, but keyboard input demands the ability to "type short, clean sentences quickly." Specifically, accurately typing technical terms, keeping subjects and predicates aligned, and trimming unnecessary words — these are distinct skills from handwriting that benefit from separate practice.

Note that detailed scheduling and operational specifics for the 2026 exam year are still being finalized and will be published as they're determined.

PBT vs. CBT Comparison Table

Tracking reform changes through text alone can amplify anxiety, so a side-by-side table helps clarify what's actually different.

The table makes clear that the changes center on how you take the exam and how you output answers, not on the exam's content. That's precisely why a wholesale overhaul of your afternoon strategy isn't necessary. The value of past exam question practice remains intact — you just add CBT-specific input training during the final preparation phase. That's the practical approach.

One-Month CBT Practice Menu Before Exam Day

In the final stretch, adapting your body to the exam's input/output matters more than adding knowledge. My approach would be to divide the month into 4 weeks, progressively transferring what you could do on paper to PC performance.

Week 1: Switch to reading afternoon past exam questions and PDF materials on a PC screen. The goal isn't passive reading — it's making the back-and-forth between passage and questions smooth on screen. People who used to underline on paper especially need to practice mentally anchoring which paragraph holds which evidence. On-screen reading can feel like you're tracking fine, yet relocating evidence takes noticeably longer. Closing this gap early prevents stalling on the afternoon section.

Week 2: Repeated short-answer typing on keyboard. You don't need to type long passages. Practicing one-sentence answers to questions is more practical. Pick a question asking for a "cause," "effect," or "countermeasure," type a short sentence with the required terms, then review whether any extra words crept in or whether your subject and predicate drifted. This repetition alone builds familiarity with a rhythm that's different from handwritten answers. Since the afternoon section runs at roughly 30 minutes per question, input delays directly compress your overall time allocation.

Week 3: Full-length practice on screen. Here, partial drills aren't enough — you need to run reading, thinking, and typing as an integrated flow. Even people with high paper-based scoring precision find that concentration fragments on PC, leading to missed diagram details or skipped question conditions. A full run reveals exactly where you lose visual tracking and which subjects consume extra typing time.

Week 4: Building 150 minutes of screen-sustained concentration. The afternoon section requires not just understanding but maintaining judgment and attention across a long duration. Screen-based fatigue tends to surface earlier than paper-based fatigue for many people. Short sessions might feel fine, but in the later questions, concentration drops lead to question-requirement misreads and simple input omissions. This week, prioritize sustaining attention over perfecting review volume — that's what connects most directly to exam-day performance.

In a nutshell, the practice menu is: keep past exam questions at the center, and shift only the medium to match exam day. It's natural to feel anxious about the CBT transition, but the core of what determines afternoon section outcomes hasn't changed. What's changing is where you read (paper to screen) and how you write (pen to keyboard). Target just that gap during the final stretch — that's the most efficient use of your remaining time.

Recommended Study Materials and Official Links for Afternoon Section Prep

IPA Official Resources: The Non-Negotiable Primary Sources

The first materials to gather for afternoon prep — before any commercial textbook — are IPA's primary sources. Specifically, the year-by-year PDF sets on IPA's official past exam page (problem booklets, model answers, and scoring commentary) form your foundation. The afternoon section tests not just "what you know" but "how to answer so that your response earns points," so there's no reason to skip material published by the exam creators themselves.

The core approach is to go beyond solving the most recent 2-3 years chronologically. Read the problem booklets, model answers, and scoring commentary across years as a set. For Networking, one year might focus on subnets and routing while another centers on redundancy and architecture decisions. Database questions shift between SQL-dominant years and design-focused years. Seeing this variation, then identifying "what type of evidence extraction does this subject consistently require" and "which scoring criteria are easy to miss" — that's what breaks you out of answer-memorization mode.

The scoring commentary is particularly valuable. Reading only model answers tempts you into memorizing "the correct text," but the commentary reveals which evaluation criteria were commonly missed and where question-requirement misreads frequently occurred. Afternoon writing prioritizes hitting the required evaluation criteria over producing beautiful prose. In that sense, the commentary is uniquely powerful as a resource for exposing "the thinking habits that cost you points."

Few exams offer this caliber of free resources. My setup would be: save the PDFs by year and prepare a single error log sheet. The format can be minimal — question number, what was asked, the passage line/diagram used as evidence, your answer, the gap versus the model answer, and a prevention note covers what you need. IPA doesn't distribute a template, but this structure is what works for articulating your own weaknesses.

Getting Value from Afternoon-Specific Strategy Books

The role of afternoon-specific strategy books isn't to add knowledge — it's to internalize question-reading patterns and answer-writing templates. People who stall on the afternoon section typically aren't stumped by unfamiliar material; they can't fully extract evidence from the passage and don't have a stable answer format. Strategy books fill that gap.

What to look for in these books: not ones that encourage memorizing model answers, but ones that explain why specific terms are needed. Good explanations break down the "question verb," "conditional clause," "constraints," and "passage evidence" separately, then show which part of the model answer corresponds to each. Since the afternoon section rewards concise answers that don't miss keywords, a book that reveals the answer assembly process is more valuable than a simple answer key.

Also, afternoon-specific books aren't substitutes for question banks. They serve different roles. Strategy books excel at question-reading approach, passage-to-diagram matching, and pattern-based writing. Question banks excel at subject-specific volume and repetition. In professional terms, strategy books are like understanding design philosophy; question banks are like implementation practice. Trying to cover both with a single book leads to either feeling like you understand without practicing, or practicing without internalizing the template.

A selection criterion that matters: specificity of example answers. If the book includes short model answers but doesn't explain "what was cut and what was kept," it won't build afternoon reproducibility. The word order changes depending on whether you're addressing a cause, an effect, or a countermeasure. Books that handle these distinctions carefully translate well to exam performance.

One afternoon-specific book used repeatedly beats several used in parallel. Sticking with "I'll decompose question requirements using this book's method" and "I'll write concisely using this book's template" and committing to that creates smoother connections to your past exam question practice. Since each afternoon question demands heavy processing time, having a no-hesitation template directly stabilizes exam-day performance.

How to Choose Comprehensive Textbooks and Question Banks

Comprehensive textbooks and question banks might seem like a detour when you're focused on the afternoon section, but they're effective when used with clear role boundaries. Position them as: comprehensive textbook for full-scope overview including the morning section, question bank for subject-specific repetition. If you haven't yet decided which afternoon subjects to pick, a comprehensive textbook lets you survey each subject's key topics and assess your strengths and weaknesses faster.

Beyond that, what you want from a question bank is explanation quality over volume. For afternoon use, books that go beyond explaining correct answers to show "where in the passage you should have found your evidence" and "why the wrong answer missed the mark" are the strong choice. Thin explanations mean that even with high solve counts, you can't reproduce your approach when a similar question appears with different phrasing. The Applied Information afternoon section especially requires this, since question framing shifts year to year even within the same subject name.

Organizing the selection criteria, here are 4 things to evaluate:

Current-year coverage is also a meaningful differentiator. It's not simply "newer is better," but materials that reflect recent exam trends reduce study drift. Particularly given that question format and exam duration are expected to remain the same after the CBT transition, books that address screen reading and short-answer typing in addition to paper-based writing are more practice-relevant.

Subject-index usability also matters for self-study. Being able to quickly look up Networking VLAN and routing topics, Database normalization and SQL, or System Strategy investment evaluation and process improvement — a structure that lets you revisit weak points quickly accelerates review. For afternoon prep, "whether you can repeatedly return to weak spots" matters more than "whether you read the whole book."

Combining with free resources is practical. Get primary sources from official PDFs, survey scope from a comprehensive textbook, fix your strategy from an afternoon-specific book, and build repetition from a question bank. Layer in your own error log and checklist, and each material's role stays distinct. You don't need to assemble everything perfectly before starting — think of it as centering on primary sources and filling only the missing roles with commercial materials, and material selection becomes much simpler.

Frequently Asked Questions

How to Approach Locking In Your Subject Areas

A common dilemma in afternoon prep is whether to pick questions on the spot based on what looks doable, or to commit to fixed subjects in advance. My recommendation is to go with 3 fixed subjects plus 1 backup. The afternoon section is less about raw knowledge and more about how deeply you've internalized each subject's reading patterns and answering conventions.

For instance, Networking questions tend to revolve around configuration diagrams, routing, VLANs, and filter conditions. Database questions have recurring patterns around table relationships, SQL, normalization, and performance design. System Strategy requires organizing business effects, costs, and risks in written form. Even though they're all "afternoon questions," the required perspectives differ significantly. Rather than spreading yourself thin, fixing your main subjects and repeatedly drilling how to extract evidence for each question type produces more consistent results.

That said, going with only fixed subjects risks collapse when you hit a year where one of them is unusually difficult. Having 1 backup subject means you still have options if one of your main three looks rough on exam day. Think of it as having three primary resources plus one contingency plan. It makes a real difference to your confidence.

When choosing subjects, "I like it" isn't enough. Look at several years of past exam questions and evaluate: can you follow the logic as you read, do your scores recover after review, and can you reproduce the answer templates? A subject where you struggle initially but understand the structure after reading the explanations has growth potential. Conversely, if the reasoning behind the correct answers remains unclear even after reviewing explanations, that subject probably isn't a good fit.

Setting Score Targets

Rather than chasing high marks evenly across every question, separating your targets into safe points and competitive points is more realistic. Since each afternoon question is roughly worth 20 points, trying to score high on every subject — including your weaker ones — drains both time and focus. A better approach is to classify each question as "secure 12-14 points" or "aim for 16 points."

The advantage of this split is reduced hesitation while solving. For safe-point questions, focus on not dropping essential keywords and reliably picking up the sub-questions you can handle. For competitive questions, carefully trace the full passage and push for precision in your written answers. Simply splitting your approach this way prevents the kind of collapse that happens when you try to treat every question with the same intensity.

People with stable scores have already decided where not to overcommit. The afternoon section is reading-intensive, so trying to perfect every question tends to cause fatigue-driven errors in the second half. At the sub-question level too, spending too much time on low-point blanks is less effective than reliably nailing questions where the evidence is clear.

Tips for Overcoming Information Security

Information Security is mandatory, so if you feel weak in this area, systematically breaking down recent years' question patterns is the fastest approach. Thinking "I'm bad at security in general" is too broad. In practice, most lost points come not from the topics themselves — access control, authentication, logging, malware countermeasures, vulnerability response — but from misreading what the question is actually asking.

An effective countermeasure is practicing concise definitions. Drilling short answers to "why is this dangerous," "what does this prevent," and "how would you fix this" makes it easier to construct answers from the situational descriptions in the passage. Afternoon Security questions reward the ability to produce the right terms concisely rather than writing lengthy explanations. IPA's model answers and scoring commentary confirm that whether the appropriate terms for each evaluation criterion are present tends to be the scoring axis.

Another important point is not to overextend into too many unfamiliar topics. Security constantly surfaces new themes, but what you need to solidify first for the afternoon section are fundamentals: authentication/authorization, encryption, log monitoring, privilege separation, and vulnerability response. If these foundations are shaky, you can understand the passage but can't condense your answer. Once the foundations are solid, you can build safe points even when the specific theme changes.

Preventing Time Overruns

People who spend too much time on long passages usually aren't lacking reading ability — their reading order and criteria for moving on are vague. In the afternoon section, rather than reading the passage carefully from the beginning, it's faster to first grasp what each question is trying to extract. Look at the questions first — is it asking for a cause, an effect, or a countermeasure? Which diagrams or tables will likely be relevant? Then go back to the passage. This order alone significantly reduces wasted reading.

On top of that, evidence marking is highly effective. Whether on paper or screen, consciously tracking conditions, constraints, numerical values, and shifts in subject as you read reduces the number of times you need to search through the passage again when writing. The afternoon section is a time-heavy exam per question, so not re-reading the same paragraph multiple times directly translates to time savings.

As a rule of thumb: if you can't find an angle after 3 minutes on a sub-question, step away temporarily. Pushing through at that point compresses time for subsequent questions you could actually solve. I've seen this type of stall many times, and it's usually an operational mistake rather than a skill gap. In the afternoon section, people who know when to distance themselves from dangerous questions tend to score more consistently than those who try to answer everything.

Note-Taking Strategies in the CBT Era

With CBT, the experience of flipping through a paper booklet and scanning back and forth changes, so adjusting your note-taking approach is worthwhile. While detailed operational procedures should follow IPA's published guidelines, what you want to build from the study phase onward is reading comprehension that assumes on-screen navigation. Since you can't survey the entire problem at a glance like you can with paper, you need to internally organize where the questions, passage, and diagrams are located.

The practical approach is to keep fewer notes with more focused information. Jot down only the "question verb," "paragraph likely containing evidence," and "keywords that must appear in the answer." Keeping just the skeleton that directly connects to your written answer is more effective than drafting long notes, and it transitions more smoothly to typed input. People who relied on writing extensively in margins on paper tend to feel disoriented at first with CBT, so practicing extracting only key points while scrolling helps ease the transition.

Getting comfortable with scrolling also takes practice. If you lose your place every time you scroll back from the passage to the questions, establish a fixed workflow during practice: check the question, find the relevant passage section, make a brief note, then write your answer. Even with CBT, the core skills being tested haven't changed. What changes is converting your evidence-finding approach from a paper-based spatial sense to a screen-based one. Practicing this transition early means you won't burn extra cognitive energy on exam day.

Summary and Next Steps

Afternoon section prep improves not by broadening your knowledge, but by understanding the format and locking in your approach. Narrow your subjects, extract evidence from past exam questions, fix your time allocation and writing template, and your scores will stabilize. Layer in screen-reading and typing familiarity for CBT, and you'll have preparation that holds up under exam-day pressure.

If you're ready to take action, here are your top 3 priorities:

1. Check IPA's official information for exam scheduling and CBT implementation details (confirming primary sources is non-negotiable; reference: IPA's exam information page).
2. Solve afternoon past exam questions and narrow down your compatible subjects (for study sequencing guidance, the article on self-study methods for the Fundamental Information Technology Engineer Exam (新制度対応) is also useful).
3. Run a weekly "practice, review, re-practice" cycle, and build up to full-length timed practice runs (for time management and weeknight study planning, refer to the article on managing study time while working for a structured approach).

Before exam day, make sure your final preparation covers: securing review time, checking question conditions, recording evidence, using short-answer templates, and confirming your on-screen answer workflow.