Data Sufficiency is one of the most misunderstood question types in competitive reasoning. The task sounds simple — read a question, read two statements, decide if you can answer — but most candidates make the same mistake: they try to actually solve the problem.
Do not do that.
Here is the key insight: you are not asked "what is the answer?" — you are asked "can you find the answer?" That is a completely different job.
Think of it like this. A friend calls you and says, "I need to know the age of the person in this photo." You have two clues:
From Statement I alone, you cannot find the age (you need the current year or the photo year). From Statement II alone, you cannot find the age (you need the birth year). But together, both statements give you: age = 2020 − 1990 = 30. You do not need to actually "experience" the photo — you just needed to confirm the path to the answer exists.
That is exactly how Data Sufficiency works. Your job is to check whether a path to a unique answer exists, not to walk down that path.
Why "unique" matters: If a statement gives you two possible answers (say, a number that could be either 4 or −4), it is not sufficient — ambiguity means insufficiency.
The four standard verdict options you will almost always see:
Every Data Sufficiency question in UP Police Constable maps to one of these four outcomes. Your entire strategy is building the reflex to reach the right verdict quickly.
Approach every Data Sufficiency question in exactly this sequence. Do not skip steps, do not rush.
Step 1 — Understand what the question is actually asking for.
Before reading either statement, ask yourself: "What would I need in order to answer this?" Write it mentally as a requirement list. For "Find the area of a triangle," your requirement list is: {shape type + all relevant dimensions}. For "What is the cost of one item?", your list is: {total cost + number of items} or {unit cost directly}.
This step takes 5–10 seconds and saves you from being misled by irrelevant statements.
Step 2 — Test Statement I alone (ignore Statement II completely).
Cover Statement II with your hand mentally. Read Statement I. Does it alone satisfy your requirement list? Can you get a unique, definite answer?
Step 3 — Test Statement II alone (ignore Statement I completely).
Now cover Statement I. Read Statement II alone. Same question: does it alone give a unique, definite answer?
When you combine: Only combine if both individual tests failed. Ask: together, do they complete the requirement list?
This is where UP Police Constable setters love to trap you. One statement will contain information that sounds useful but has nothing to do with the question.
Look at the colour-of-items example from the PYQs below. Statement II says "the items are blue in colour." Your instinct might be to think "colour affects price in some markets." That instinct will cost you marks. In reasoning, colour is irrelevant to price unless the question specifically links them. Dismiss irrelevant statements immediately — they are designed to eat your time.
The irrelevance test: Ask, "If I remove this statement, does my ability to answer the question change at all?" If no, the statement is irrelevant — mark it as insufficient and move on.
Geometry questions in Data Sufficiency are particularly tricky because you need enough constraints to uniquely fix the shape.
For a triangle:
For perimeter of a triangle:
base = 2 × area ÷ height), but the other two sides are still unknown unless the triangle type is given (right-angled, isosceles, etc.).Key principle: In geometry, ask "how many unknowns do I have, and how many independent equations do the statements give me?" If unknowns > equations, it is not sufficient.
A statement is sufficient only if it leads to exactly one answer. If a statement allows two or more possible answers, it fails.
Example: "x² = 16" gives x = 4 or x = −4. If the question asks "find x," this statement alone is not sufficient unless additional context rules out the negative value.
This catches candidates who say "I can partially solve it, that's enough." It is not. Partial solving that leaves ambiguity = insufficient.
| Question type | What you usually need | |---|---| | Cost / price | Unit cost OR total + count | | Age | Birth year + reference year OR age at event + time gap | | Area of known shape | Shape type + key dimension(s) | | Perimeter | All sides OR shape + key dimension | | Number puzzles | Enough equations for all unknowns | | Relationship (who is elder?) | Direct comparison OR chain of comparisons |
Build this table in your head — when you see the question type, your requirement list should appear automatically.
Before reading either statement, mentally write down what you need to answer the question. Call this your "shopping list." When you read each statement, ask: "Does this statement give me at least one item from my shopping list?" If it completes the list alone, it is sufficient. This turns a reasoning task into a matching task — matching statements to requirements. Standard method (read-and-think): 60–90 seconds. Requirement list method: 20–35 seconds, because you know what you are looking for before you start looking.
When testing Statement I, physically (or mentally) block Statement II. Many candidates unconsciously blend both statements when evaluating one. By forcing yourself to read only one at a time, you eliminate cross-contamination errors. In mock tests, candidates who blend statements wrong the verdict 30–40% of the time on "only one sufficient" questions. The cover-hand test costs 0 extra seconds and prevents a common wrong answer.
If a statement gives you information about a dimension/attribute that the question does not mention (colour when asking about price, weight when asking about age, material when asking about perimeter), flag it immediately as "almost certainly irrelevant." Test the other statement first. This alarm alone eliminates one wrong option in under 5 seconds, turning a 4-option question into a 3-option question. Standard approach: evaluate all four options equally (80s). Irrelevance alarm: eliminate one in 5s, solve remaining in 40s. Net saving: ~35 seconds.
For any geometry question, count unknowns vs. equations. A triangle has up to 6 parameters (3 sides, 3 angles) but is uniquely determined by 3 independent ones. If the statements together give you fewer independent constraints than unknowns, the answer is "neither is sufficient." For equilateral triangle: knowing it is equilateral collapses 6 parameters to 1 (the side). Add the side → 0 unknowns → sufficient. For a general triangle with area + height: you get the base but still have 2 unknown sides → perimeter not determinable. This counting method takes 10 seconds and gives the verdict without any calculation. Without it, candidates often attempt partial calculations for 2–3 minutes and still get it wrong.
After you decide a statement is sufficient, run a 5-second sanity check: "Does this give me exactly one answer, or could there be two?" If the statement involves a squared variable, an absolute value, or a range ("between 10 and 20"), there may be multiple answers — which means insufficient. This check adds 5 seconds but prevents the most common advanced-level error in Data Sufficiency. Most candidates skip this check and lose marks on questions designed specifically around this ambiguity trap.
In the exam hall, follow this decision tree without deviation:
Step 0 (5s): Read the question. Write your requirement list mentally.
Step 1 (10s): Read Statement I only. Does it alone complete the requirement list and give a unique answer?
Step 2 (10s): Read Statement II only. Same test.
Step 3 (10s): Combine both statements. Together, do they complete the requirement list uniquely?
Red flags that slow you down — avoid:
Total target time per question: 35–45 seconds.
Why this question: This is the simplest Data Sufficiency structure — one statement is directly sufficient, one is completely irrelevant. The exam setter banks on you spending time evaluating the colour statement. Train yourself to dismiss irrelevance in under 5 seconds.
Solving path: Requirement list: {unit cost} or {total cost + count of identical items}.
Statement I: 5 identical items cost 100. Count = 5, total = 100. Unit cost = 100 ÷ 5 = 20. Unique answer. Statement I alone is sufficient.
Statement II: Items are blue. Colour has no mathematical link to price in this problem. Irrelevance alarm fires immediately. Statement II alone is not sufficient.
Verdict: Only Statement I is sufficient.
Why this question: This tests the "two statements combining" scenario. Neither statement alone is sufficient, but together they fully determine the answer. Knowing when to combine — and when combining still fails — is the hardest skill in Data Sufficiency.
Solving path: Requirement list: {shape type + key dimension(s) sufficient to compute area}.
Statement I alone: One side is 6 units. A triangle with one side = 6 could be any shape — right-angled, scalene, obtuse. No unique area possible. Not sufficient.
Statement II alone: It is an equilateral triangle. Shape is fixed, but no size given. Infinitely many equilateral triangles of different sizes. Not sufficient.
Combined: Equilateral triangle (Statement II) with side = 6 (Statement I). Area = (√3/4) × 6² = (√3/4) × 36 = 9√3. Unique answer.
Verdict: Both statements together are required (sufficient).
Why this question: This is the "neither sufficient" verdict — the most counter-intuitive outcome. The trap is that area + height gives you the base, and candidates think "I have the base, one more step and I'm there." But perimeter needs all three sides, and you are still two unknowns short.
Solving path: Requirement list: {all three sides of the triangle} — because perimeter = sum of all three sides.
Statement I alone: Area = 24 sq. units. Countless triangles have area 24. Not sufficient.
Statement II alone: Height = 4 units. On its own, height gives nothing about sides. Not sufficient.
Combined: Area = 24, Height = 4. Using Area = (1/2) × base × height → 24 = (1/2) × base × 4 → base = 12. You now know one side. But the other two sides are completely unknown — the triangle could be right-angled (sides 5, 12, 13 — verify: area = 30, not 24), isosceles, or scalene. You need the triangle type or more measurements to find the remaining two sides. No unique perimeter is possible.
Verdict: Both statements together are also not sufficient.
Solving instead of checking sufficiency. You do not need the numerical answer. The moment you know a unique answer exists, stop. Completing the calculation wastes 30–60 seconds per question.
Blending both statements when testing one. "Statement I says one side is 6, and since we know it is equilateral..." — that is using Statement II while evaluating Statement I. Test each statement in isolation first. This error causes wrong verdicts on the most common question type.
Treating irrelevant information as potentially helpful. Colour, material, texture, and similar qualitative data almost never affect quantitative answers. The moment you see "Statement II: the items are made of wood," dismiss it as irrelevant and direct your attention to Statement I.
Accepting a statement as sufficient when it gives two possible answers. If a statement leads to "x = 4 or x = −4," it is not sufficient. Always run the unique-answer check before finalising your verdict.
Assuming "both together" always works. The "neither sufficient" option exists and appears regularly. Do not assume that combining two pieces of information always bridges the gap — check whether the combined information actually completes the requirement list.
Forgetting to verify that the question's requirement list is fully met. For perimeter, you need all sides. For area of a general triangle, you need more than just one side. Define the requirement list precisely at the start, or you will declare a statement sufficient when it only partially helps.