The 12 GRE Quant Traps (and How to Beat Each One)

Quantitative Comparison Traps

Quantitative Comparison (QC) questions have a structure unlike any other question type on the test, and that structure creates traps that are entirely specific to QC. In a QC question, you are given Quantity A and Quantity B and asked to determine whether A is greater, B is greater, they are equal, or the relationship cannot be determined from the information given. That fourth option, 'cannot be determined,' is the source of the most important QC trap.

Trap 1: The 'Cannot Be Determined' Trap

When a QC question involves an unconstrained variable, students typically try to evaluate which quantity is larger by substituting a value. If A comes out larger with x = 2, they select 'A is greater.' The trap is that this logic is only valid if the relationship holds for ALL values of x satisfying the problem's conditions. If it holds for x = 2 but not for x = -1, the answer is 'cannot be determined.'

Take the canonical example, where Quantity A is x squared and Quantity B is x. Students substitute x = 3 (A = 9, B = 3, so A is greater) and select A. But for x = 0, both quantities equal 0, so they are equal. For x = 1/2, A = 1/4 and B = 1/2, so B is greater. The relationship depends on x, so the correct answer is 'cannot be determined.'

Trap 2: The 'Special Cases' Trap

Questions that do not specify whether a variable is a positive integer, a fraction, or a negative number are testing whether you remember to try special cases. The most important special cases are negative numbers, fractions between 0 and 1, zero itself, and numbers between -1 and 0. Students who test only positive integers miss all of these.

Consider Quantity A as x cubed and Quantity B as x squared. For x = 2, A = 8 and B = 4 (A greater). For x = 1/2, A = 1/8 and B = 1/4 (B greater). For x = -1, A = -1 and B = 1 (B greater). The answer is D. A student who tests only x = 2 and x = 3 gets the wrong answer. The fix: whenever a QC question involves exponents, squares, or roots and does not specify the nature of the variable, mentally run through your special case checklist before committing to an answer.

Trap 3: The 'Geometric Figure Not to Scale' Trap

QC questions that include a geometric figure often draw that figure in a visually misleading way. A triangle that looks isosceles may not be. An angle that looks like 90 degrees may not be. The GRE sometimes marks figures as 'not drawn to scale,' but not always.

The rule is absolute: in geometry problems, the only information you can use is what is stated in the problem text or clearly marked on the figure (like right angle symbols). Visual impressions are not valid inputs. A question might show a quadrilateral that looks like a rectangle and then ask you to compare two side lengths. If the rectangle-ness is not stated, you cannot assume it, and the answer is probably D. The fix: when a QC problem includes a geometric figure, make a deliberate list of what is stated versus what is merely drawn, and solve only from the stated information.

Number Properties Traps

Number properties are the area of GRE Quant where most trap errors occur. The traps work by exploiting the automatic assumptions that people make about numbers, assumptions that are often true in everyday life but are false in the mathematical universe the GRE operates in.

Trap 4: The Integer Assumption Trap

When a GRE problem says 'n is a number' or 'let x satisfy this equation,' it does not mean n or x is an integer. Students who assume integers when the problem does not specify integers will solve the problem for the wrong set of values.

Example: 'If n times (n minus 1) equals 6, what is n?' Students instantly think of integers and conclude n = 3 (since 3 times 2 = 6) or possibly n = -2 (since -2 times -3 = 6). But the equation also has non-integer solutions. For a multiple choice question asking what n could equal, options including non-integers like 2.5 or -1.5 may be valid solutions depending on the equation.

Trap 5: The Positive Assumption Trap

Similarly, the absence of the phrase 'positive' does not mean a variable is positive. Questions involving absolute values, inequalities, and comparisons are particularly susceptible to this trap, because positive numbers behave differently from negative numbers in almost all these contexts.

Example: if the problem tells you that the absolute value of x is 5, x could be 5 or -5. A question that asks you to evaluate x minus 3 has two completely different answers depending on the sign of x. Students who assume x = 5 and compute 2 get the wrong answer for x = -5, which produces -8. When a question involves absolute values, inequalities, or square roots, always check whether negative values of the relevant variable are possible.

Trap 6: The Zero Trap

Zero is the most common single source of number properties errors on the GRE, and it works in three distinct ways.

1. Zero is an even number. This surprises many test takers who think of even numbers as starting at 2. Questions that ask about properties of even numbers may include zero as a valid case.
2. Zero is neither positive nor negative. A problem that says 'for all positive numbers' or 'for all negative numbers' does not apply to zero.
3. Any number multiplied by zero is zero, which collapses expressions in ways that can change the answer to a comparison dramatically.

Example: if a problem establishes that xy = 0, you cannot conclude that x is zero or that y is zero. You only know that at least one of them is zero. A student who concludes x = 0 and then evaluates subsequent expressions with x = 0 will get the wrong answer in cases where y = 0 and x is not zero.

Trap 7: The Negative Exponent Trap

This trap is extraordinarily common and extraordinarily avoidable once you have seen it once. It involves the difference between two expressions: 'negative x squared' written as -x^2, and 'the square of negative x' written as (-x)^2. These are not the same. The square of negative x is positive: (-x)^2 = x^2. The negative of x squared is always negative or zero: -(x^2) is never positive for real x.

GRE problems exploit this by writing expressions that look like 'negative of something' but are actually 'something negative.' Example: Quantity A is (-3)^2 and Quantity B is -(3^2). Quantity A equals 9. Quantity B equals -9. Quantity A is greater. A student who reads both as 'three squared' picks 'equal' and gets it wrong. The fix: when you see a negative sign near a power, stop and parse the expression explicitly before evaluating.

Word Problem Traps

Word problems are where GRE Quant tests your reading precision as much as your mathematical ability. The traps in this category work by introducing ambiguity about units, reference points, or direction of an inequality, all things that a careful reader catches and a rushing reader misses.

Trap 8: The Units Trap

The GRE regularly mixes units within a problem and expects you to convert them correctly before computing. Common unit trap pairs include miles and feet (1 mile = 5,280 feet), hours and minutes, dollars and cents, kilometers and meters, and percentages and decimal fractions.

The mechanism: a problem states a speed in miles per hour, asks you to compute a distance for a time given in minutes, and does not remind you to convert. Students who compute speed times time without converting end up with a number that is off by a factor of 60. Example: a car travels at 60 miles per hour. How many feet does it travel in 30 seconds? Students who multiply 60 by 30 get 1,800, then may or may not convert to feet. The correct process: 60 mph = 1 mile per minute = 5,280 feet per minute = 88 feet per second. In 30 seconds: 88 times 30 = 2,640 feet.

Trap 9: The 'Percent of What' Trap

Percent problems on the GRE contain three distinct and easily confused computations:

• Percent change: how much something changed relative to the original.
• Percent of the original: what fraction of the original value a new amount represents.
• Percent of the new value: what fraction of a new amount some related quantity represents.

These are not interchangeable, but problems are written to make them look like they might be. Example: a price increases from $80 to $100. What is the percent increase? Students compute (100 - 80) / 100 = 20%, using the new price as the denominator. The correct answer is (100 - 80) / 80 = 25%, using the original price. Percent change is always relative to the starting value.

A subsequent question might then ask: by what percent must the new $100 price decrease to return to $80? The answer is (100 - 80) / 100 = 20%, now correctly using the new price as the denominator. Same numbers, different denominators, different answers. These problems are designed to induce this confusion.

Trap 10: The 'At Least / At Most' Reading Trap

Inequality direction is one of the most consistent sources of reading errors on GRE word problems. The phrases 'at least,' 'no more than,' 'at most,' 'no fewer than,' 'minimum of,' and 'maximum of' each specify an inequality direction, and flipping that direction produces the wrong answer. A problem that asks for the minimum number of items satisfying a condition requires an inequality pointing one way; substituting the wrong direction produces a maximum rather than a minimum.

The trap deepens when problems embed the inequality language in a story context. Example: 'A container holds at most 50 liters. If it currently holds x liters, which expression represents the maximum additional liters it can hold?' Students who answer with x rather than 50 - x, or who set up the inequality as x is greater than or equal to 50 rather than x is less than or equal to 50, answer the wrong question.

Geometry Traps

Geometry traps on the GRE are primarily about the relationship between what is drawn and what is stated. The test deliberately exploits the human tendency to use visual information even when it has been explicitly withdrawn.

Trap 11: Figures Not Drawn to Scale

The GRE explicitly states that figures in Quantitative Reasoning problems are not necessarily drawn to scale unless the figure is a number line or an explicitly labeled coordinate system. Despite this, students consistently rely on visual impression when computing geometric quantities. The trap is most dangerous in Quantitative Comparison problems where a figure looks like it settles the comparison but actually does not.

Example: a QC problem shows a triangle with what appears to be one right angle and asks you to compare the lengths of two sides. The figure looks like the two legs are equal. But the problem does not state that any angles are equal or that the triangle is isosceles. The visual impression cannot substitute for stated information. The correct answer may be D if the relationship between the sides depends on information not provided.

Trap 12: The Similar Triangles Assumption

This trap is more conceptual-looking but is actually a misreading trap. Students who learn that parallel lines cut by a transversal create similar triangles sometimes apply this relationship in contexts where it was not established. In a figure with two triangles, the triangles look similar, and they might even share an angle, but similarity requires one of three specific conditions:

• Two pairs of equal angles (AA).
• Two pairs of proportional sides with an included equal angle (SAS).
• Three pairs of proportional sides (SSS).

A visual resemblance does not establish similarity. Problems that look like they want you to use similar triangle ratios will occasionally provide just enough information to make similarity seem obvious, while actually requiring you to prove it. If the similarity is not stated or derivable from stated angle or side relationships, you cannot use proportional side ratios.

Example: two triangles share a vertex and look like they have parallel corresponding sides, making them appear similar. The problem asks you to find a side length using what looks like a proportion. But the parallel relationship was never stated; it was only implied by the figure. Without a stated parallel relationship or two explicitly equal angles, the proportion is not valid, and the problem may have a different solution method or may be unanswerable from the given information.

Data Interpretation Traps

Data interpretation problems appear in both Quant sections and test a specific skill: extracting accurate numerical information from graphs and tables under time pressure. The traps here are reading traps, not computation traps. The math is almost always straightforward; the challenge is reading the data correctly in the first place.

Misreading Graph Scales

Misreading a scale is the most consistent data interpretation error, particularly on graphs where the y-axis does not start at zero, where both axes use different scales for different segments, or where a logarithmic scale is used. On a graph where the y-axis starts at 50,000, the bar for a company with 60,000 units looks twice as tall as the bar for a company with 55,000 units, but the actual difference is only 10,000 versus 5,000: a 2-to-1 visual ratio for a much smaller numerical ratio.

The GRE exploits truncated axes regularly. Example: a bar chart shows two companies' revenues for a year. Company A's bar extends to the 85 mark on the y-axis. Company B's bar extends to the 80 mark. If the y-axis starts at 75 and each unit represents $5 million, Company A's revenue is 75 + (85-75) x 5M = $125 million. Company B's is $100 million. The ratio is 1.25 to 1, not the roughly 1.06-to-1 that the bar heights alone suggest. The fix: before reading any value from a graph, read the scale labels on both axes, note where zero is, and compute actual values rather than reading proportional heights from the chart.

The Absolute vs. Percentage Change Trap

Data interpretation questions often ask about 'the greatest increase' or 'the year with the largest growth.' These questions are traps because absolute increase and percentage increase can identify different years, and the question specifies one of them while the data invites you to compute the other. Consider a company's revenue across four years:

A question asking 'which period showed the greatest percentage increase in revenue?' requires the percentage calculation; a question asking for 'the greatest increase in revenue' (without 'percentage') requires the absolute calculation. These are answered differently, and the answer choices are carefully constructed to match both possible misreadings.

The Calculator Trap

The GRE Quant section provides an on-screen, four-function calculator with a square root key. Many test takers treat it as a gift, a guarantee that every computation can be handled mechanically. It is not a gift. It is a subtle trap. Test takers who reach for the calculator on every problem lose time, lose the ability to check answers by estimation, and miss the elegant shortcuts that the GRE is designed to reward.

The on-screen calculator is slow. Entering a multi-step computation with the mouse takes significantly longer than mental math for problems designed to be solved without a calculator. Consider these two cases:

Estimation is a critical GRE Quant skill that the calculator undermines if overused. Many GRE problems have answer choices that are far apart enough that an estimate resolves the question immediately. If the answer choices for a problem are 4, 8, 14, 24, and 42, and your estimate of the answer is around 7 or 8, you know the answer is 8 without computing exactly.

A test taker who reaches for the calculator to compute 7.84 and then picks the wrong answer because of an entry error has made both a strategy error and a calculation error. The order of operations should be estimation first, calculation only when the estimate does not resolve the question, and calculator only when the computation is genuinely tedious.

There is also a specific calculator trap on Data Interpretation problems, where students use the calculator to compute values that the graph makes visually obvious. Reading 'approximately 25,000' from a bar chart and then using the calculator to add 25,000 + 8,000 is slower than just computing 33,000 mentally. Save the calculator for cases where multiple data points need to be combined or where the scale requires actual multiplication. For rough reading and comparison problems, your eye is faster.

Building a Trap-Detection Habit

Knowing that traps exist is not the same as catching them in real time. The goal of trap training is to internalize a question-reading process that reliably surfaces potential traps before you commit to a solution path. This process has to be fast enough not to eat your time budget, but systematic enough to catch the signals that matter.

Run this trap-detection process on every GRE Quant question:

1. Read the full question twice before starting any computation.
2. Identify all constraint words: 'integer,' 'positive,' 'non-zero,' 'greater than,' 'at least,' 'at most.'
3. Identify the question type (QC, multiple choice single answer, multiple choice multiple answer, numeric entry).
4. For QC questions: ask 'could the relationship depend on an unstated value?' If yes, try special cases.
5. For word problems: identify units and write down required conversions.
6. For geometry: list stated vs. visual information explicitly.
7. Then solve.

This process sounds slow, but it becomes fast with practice. After 30 to 40 problems reviewed with this checklist, the checklist becomes automatic: you will find yourself scanning for constraint words and special case opportunities as part of reading the question, not as a separate step. The investment is front-loaded into your practice sessions; the payoff is speed and accuracy on test day.

The most important element of the checklist for most test takers is the constraint word scan. Constraint words are the mechanism by which most traps work: the question allows negatives but does not say so; the question allows fractions but the student assumed integers; the question says 'at most' and the student read it as 'at least.' Practicing the explicit scan for constraint words catches more traps than any other single habit.

How to Review Practice Problems to Build Trap Immunity

Practice without review is nearly worthless for improving Quant accuracy. The review process is where learning happens, and for trap-based errors specifically, it requires a different approach than reviewing conceptual errors. The goal is not just to understand why you got the question wrong: it is to identify the specific trap and add it to your internal detection pattern library.

For every GRE Quant question you answer incorrectly, run through this three-question diagnosis and match each error type to its remedy:

Keeping a trap log is the single most effective practice for reducing trap error frequency. A trap log is a simple document where you record each trap error you make:

• The date.
• The question source.
• The trap type (from the list in this post).
• What assumption you made.
• What the correct reading was.

Reviewing this log weekly will reveal which traps are your personal high-frequency errors and which you are already detecting reliably. Most test takers find that 60 to 70 percent of their trap errors come from three or four trap types. Targeted awareness of those specific traps is far more efficient than general vigilance about all twelve.

For quant practice problems specifically, build the trap-detection habit into your approach from the beginning. Do not practice problems at high speed hoping to develop accuracy. Develop accuracy at lower speed first, then gradually increase pace. Speed that outpaces accuracy produces nothing except a larger collection of unexamined mistakes.

Frequently Asked Questions