Iran Konkur Languages common mistakes
Iran Konkur Languages · Understand the traps and how to avoid them.
Reading a passage once, then answering detail questions from memory without returning to the line that supports the choice, so answers drift toward what the passage 'generally' says rather than what it states.
Konkur reading passages are timed tightly and candidates fear re-reading costs minutes, so they trust first impressions; distractor options are deliberately written to be plausible from a vague memory of the topic.
What to do instead
For every detail or inference item, locate and underline the exact sentence (or two) that decides the answer before marking it. Train with a 3-pass method: skim structure (30 seconds), read questions, then scan-and-verify each option against a specific line. Practice until verification adds under 15 seconds per item.
Choosing an answer option that is true in real life or true somewhere in the passage but does not answer the question asked (especially 'main idea', 'tone', and 'author's purpose' items).
Candidates evaluate options for factual truth instead of relevance to the stem; main-idea items punish options that are too narrow (one paragraph) or too broad (beyond the text), and candidates lack a habit of checking scope.
What to do instead
Before looking at options, write a 5-word prediction of the answer. Then eliminate any option that is only a supporting detail or that goes beyond the passage's scope. For main-idea items, verify the chosen option covers the whole passage, not one paragraph.
Treating grammar items as 'which sounds right' and picking the option that matches a memorized pattern, ignoring the surrounding clause (e.g., choosing a past tense after 'since' or a gerund after a preposition because it 'sounds natural').
Konkur grammar tests specific contrasts (tense sequence, conditionals, reported speech, inversion, articles) and the wrong options are common learner errors that feel familiar; without an explicit rule check, familiarity beats correctness.
What to do instead
For each grammar item, name the rule being tested in one word (tense, article, inversion, preposition, concord) and apply it to the full sentence, not the gap alone. Keep a one-page error log of rules you missed and re-test only those rules weekly.
Answering vocabulary items by translating the stem word into Persian and picking the option with the closest Persian meaning, missing collocation and register (e.g., 'make a decision' vs 'do a decision', 'strong rain' vs 'heavy rain').
Bilingual study habits encourage one-to-one word mapping, but Konkur vocabulary items frequently test collocations, prepositions, and near-synonyms distinguished only by usage.
What to do instead
Learn new words as chunks: record the word with its usual collocates and preposition (depend on, responsible for, a heavy smoker). For synonym items, insert each option into the original sentence and reject any that changes the grammatical pattern or register.
Filling cloze blanks one by one in order, committing to an early choice that later context contradicts, and never re-reading the completed text.
Cloze passages are designed so that a later sentence disambiguates an earlier blank; sequential filling without a final coherence check locks in errors, and cohesive devices (however, therefore, in contrast) are ignored.
What to do instead
Read the whole cloze passage first without filling anything. Fill the blanks you are sure of, then use the remaining context and linking words to resolve the rest. Always do a final read-through of the completed passage to check logic and grammar flow.
Producing the wrong word form because the candidate supplies a synonym or a different part of speech that fits the meaning but not the required slot (e.g., writing 'success' where 'successful' is needed, or forgetting the negative prefix).
Word-form items require both meaning and morphology; under time pressure candidates stop at meaning and skip checking what the sentence structure demands (adjective before noun, adverb modifying verb, noun after article).
What to do instead
Before writing, identify the slot: what part of speech does the syntax require? Then apply derivational morphology deliberately (prefix, suffix, spelling changes such as happy→happiness, begin→beginning). Build a personal table of common families and test yourself by filling slots, not by translating.
In the second foreign language, reading the passage word by word and stalling on unknown words, or answering from the cognate that looks like an English/Persian word rather than from the target-language sentence.
Limited vocabulary in the second language makes every unknown word feel fatal, and false friends (e.g., German 'bekommen', French 'actuellement') mislead candidates who rely on surface similarity.
What to do instead
Practice gist-first reading: skim for topic and structure, answer global questions, then scan for the specific sentence behind each detail item. Maintain a false-friends list for your language and review it before each mock. Never choose an option based only on a word that resembles another language.
In verbal reasoning, accepting an argument's conclusion because it matches personal belief or because the passage sounds authoritative, instead of testing whether the stated premises actually support it.
These items are designed with conclusions that are plausible but logically unsupported (or supported only by an unstated assumption); everyday reasoning rewards plausibility, not validity.
What to do instead
For each argument, label premises and conclusion explicitly, then ask: 'If the premises are true, must the conclusion be true?' Identify the hidden assumption and check whether an answer option attacks, strengthens, or merely restates it. Practice on assumption, weaken, and strengthen item types separately.
Solving quantitative items by setting up full algebra for every problem, running out of time, and leaving later easy items blank; or misreading units and percentages (e.g., percent increase vs percent of, cm vs m).
School training rewards formal solutions, but Konkur quantitative sections are speed tests where approximation, plugging in answer choices, and unit checks win; unit and percentage wording traps are common.
What to do instead
Adopt a triage rule: attempt items in two passes, doing arithmetic-friendly ones first. Use back-solving from options and estimation where exact computation is slow. Before computing, circle the unit and the exact question wording (increase vs total, per person vs total). Time yourself in 90-second blocks.
Reading data-interpretation tables and charts by grabbing the first number that looks relevant, ignoring axis scales, legends, and the 'total vs segment' distinction, then computing on the wrong base.
Charts compress information and use non-unit scales or multiple series; candidates skim the visual and assume the tallest bar or the labeled number is the required value, and percentage-of-total items are computed on a segment instead of the total.
What to do instead
For every chart item, first read the title, axis labels, units, and legend aloud in your head, and note whether the question asks for a segment, a ratio, or a change over time. Write the required formula before touching numbers, then extract values. Do a sanity check: does the answer's size make sense relative to the chart?