12 GRE Quant Traps (With Examples) and How to Beat Them

The 12 GRE Quant traps at a glance

Use this as a quick reference: the tell (how you spot the trap in the wild) and the one move that beats it. Each is explained in full below.

Want to see these in timed questions? Drill them in quantitative comparison practice, where most of the traps live, and in a free full-length GRE mock, where every question has a worked solution.

Where the Traps Live in the Current Quant Sections

Since September 2023 the GRE has two Quant sections: 12 questions in 21 minutes, then 15 in 26 minutes, so about 1 minute 45 seconds per question (ETS test structure page, checked October 2026). The second section's difficulty depends on how you did on the first, so a trap that catches you in section 1 costs you twice. ETS publishes the question formats but not how many of each appear; the counts below are Magoosh's estimates for the shorter test.

Three ETS ground rules decide many traps before you start: all numbers used are real numbers, so a variable can be negative, zero or a fraction unless the question says otherwise; geometric figures are not necessarily drawn to scale; and coordinate systems and data graphs are drawn to scale.

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 it in a visually misleading way. A triangle that looks isosceles may not be. An angle that looks like 90 degrees may not be. ETS's rule is that geometric figures are not necessarily drawn to scale, whether or not the figure carries a note saying so.

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 where many trap errors occur. The traps exploit automatic assumptions people make about numbers: assumptions that hold in everyday life, where quantities are usually positive whole numbers, but fail in the GRE's world of all real numbers.

Trap 4: The Integer Assumption Trap

ETS states that all numbers used on the test are real numbers. When a problem says 'x is a number' or gives a range, it does not mean x is an integer. Students who assume integers when the problem does not say so solve the problem for the wrong set of values.

Example: 1 < x < 3. Quantity A is x; Quantity B is 2. A student thinking in whole numbers sees that the only integer between 1 and 3 is 2 and picks 'equal'. But x = 1.5 makes B greater and x = 2.5 makes A greater, so the correct answer is 'cannot be determined'. The same trap appears in problem solving when a question asks how many values satisfy a condition: the count is finite only if the problem restricts you to integers.

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 a frequent source of number properties errors, 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

Negative exponents and negative signs are different things, and the GRE tests both. A negative exponent means a reciprocal, not a negative number: 2^(-3) = 1/(2^3) = 1/8, a small positive number. Students who read 2^(-3) as -8 get the sign and the size wrong. Fractional bases reverse intuition: (1/2)^(-2) = 2^2 = 4, which is larger than the base. A fractional exponent is a root: 8^(1/3) = 2.

The sign version is just as common. In -x^2 the exponent applies first and the negative sign second, so -3^2 = -9; in (-3)^2 the negative is inside the parentheses, so it equals 9. The square of a negative number is positive, while the negative of a square is never positive for real numbers. Example: Quantity A is (-3)^2 and Quantity B is -3^2. A equals 9, B equals -9, so A is greater. A student who reads both as 'three squared' picks 'equal'.

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

ETS's rules on figures are specific, and the trap runs in both directions. Geometric figures are not necessarily drawn to scale, so you cannot read lengths or angle sizes off them. You can assume that lines shown as straight are straight, that points on a line are in the order shown, and that objects are in the relative positions shown. Coordinate systems such as xy-planes and number lines, and data graphs such as bar, circle and line graphs, are drawn to scale, so you can read values from them by sight or measurement.

The first direction is the familiar one: measuring a geometry figure. The second costs points too: refusing to read a scaled graph or number line, and grinding out an exact calculation the picture already settles. Know which kind of figure you are looking at before you decide how much to trust it.

Example: a problem shows a triangle with what looks like a right angle and two equal legs, and asks for the length of the hypotenuse. Nothing in the text marks the angle as 90 degrees or the legs as equal. Treating it as a 45-45-90 triangle because it looks like one is the trap; without a right-angle mark or stated equal sides, you cannot use those relationships.

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 questions come in sets: several questions about the same table or graph (ETS). They test one skill, extracting accurate numbers from a display under time pressure. The traps here are reading traps, not computation traps. The math is usually simple; the challenge is reading the data correctly in the first place.

Misreading Graph Scales

Misreading the scale is one of the most common data interpretation errors, especially on graphs whose vertical axis does not start at zero. ETS says data graphs are drawn to scale, and a truncated axis is still to scale; it just starts somewhere other than zero, which distorts how bar heights compare.

Example: a bar chart's vertical axis is labeled in millions of dollars and starts at 80. Company A's bar reaches 100 and Company B's reaches 90. On the page, A's bar rises 20 units above the axis and B's rises 10, so A looks twice as large. In fact A's revenue is 100 / 90, about 1.11 times B's: roughly 11 percent more, not 100 percent more. The fix: before reading any value, read both axis labels, note where the axis starts and what each gridline is worth, and compute from the values, not from bar heights.

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

Both Quant sections provide an on-screen calculator, which ETS says you can operate with the mouse or the keyboard. ETS's own guidance is that it is most useful for tedious computations such as long division and square roots, and that simpler computations are often faster done mentally. Many test takers treat it as a guarantee that every computation can be handled mechanically. That is the trap: reaching for it on every problem costs time, removes the estimation check, and skips the shortcuts the questions are built to reward.

Even with the keyboard, entering a multi-step computation takes longer than mental math on a problem designed to be solved without a calculator, and every entry is a chance for a typo. Compare 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.

Format Traps: Select-All and Numeric Entry

Two GRE Quant formats have traps of their own, separate from the math.

Select one or more answer choices. ETS's instruction is to consider every choice, decide which are correct, and select all of those and only those. The question may or may not tell you how many to select. The trap is stopping after the first correct choice, or assuming there must be at least two. Treat any partial selection as a miss and test each choice on its own.

Example: which of the following could be a value of x if 2x + 3 > 7 and x < 5? (A) 1 (B) 2 (C) 3 (D) 4.5 (E) 5. The first inequality gives x > 2, so the range is 2 < x < 5. Check each: 1 and 2 fail the first condition, 5 fails the second, and 3 and 4.5 both work. Answer: C and D. A student who finds 3 and moves on, or who rejects 4.5 by assuming integers, loses the point.

Numeric entry. ETS lets you enter an integer or decimal in a single box, or a fraction in two boxes, and if the question asks you to round, you must round to the required degree of accuracy. With no answer choices to check against, the traps are:

• Rounding in the middle of a calculation instead of only at the end.
• Answering in the wrong form: entering 0.25 when the question asks 'what percent', where the answer is 25.
• Answering in the wrong unit: minutes when the question asks for hours.
• Skipping the estimate. Without choices, a quick estimate is your only check that the number you type is the right size.

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 one of the most effective ways to reduce trap errors. 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 shows which traps are your personal repeat offenders and which you already catch reliably. For most people a handful of trap types account for most of their trap misses, and targeted awareness of those few is far more efficient than general vigilance about all twelve.

Build the trap-detection habit into your practice from the start. Do not practice at high speed hoping accuracy follows. Develop accuracy at a slower pace first, then increase speed. For harder material, work through our hardest GRE math questions, and for the trap-dense formats, GRE word problems and GRE probability questions each walk through worked examples.

Spot the Trap: Five Practice Questions

Try each before reading the answer. Name the trap first, then solve.

1. x^2 = 9. Quantity A: x. Quantity B: 3. Answer: the relationship cannot be determined. x can be 3 or -3. Trap 5, the positive assumption.
2. 0 < x < 1. Quantity A: x^3. Quantity B: x^2. Answer: B is greater. For any fraction between 0 and 1, a higher power is smaller (for x = 1/2, x^3 = 1/8 and x^2 = 1/4). Trap 2: testing x = 2 suggests the opposite, but x = 2 is not allowed here.
3. A price rises by 20 percent and then falls by 20 percent. What is the net percent change? Answer: a 4 percent decrease, because 1.2 times 0.8 is 0.96. Trap 9: the second 20 percent is taken of a larger base.
4. xy = 0. Quantity A: x. Quantity B: 0. Answer: the relationship cannot be determined. If y = 0, x can be anything. Trap 6: a zero product means at least one factor is zero, not a particular one.
5. Quantity A: (1/2)^(-2). Quantity B: 2^2. Answer: the two quantities are equal; both are 4. Trap 7: a negative exponent means a reciprocal, not a negative number.

Frequently Asked Questions