GMAT Review: GMAT Quant Traps: Assumption of Unstated Conditions, C‑Trap in Data Sufficiency, Misreading Constraints

GMAT – GMAT Quant Traps: Assumption of Unstated Conditions, C‑Trap in Data Sufficiency, Misreading Constraints

## What This Is
On the GMAT Quant section, “traps” are hidden assumptions that turn a seemingly straightforward problem into a wrong‑answer pitfall. The three most common are: (1) Assumption of Unstated Conditions – treating a variable as if it has a property that was never given; (2) C‑Trap in Data‑Sufficiency – believing a single statement is sufficient because it “looks like” a complete answer (the classic “C” answer); and (3) Misreading Constraints – overlooking or mis‑interpreting inequalities, domain limits, or “must be integer” requirements.
Typical example: “If x + y = 10, what is the greatest possible value of xy?” – many test‑takers assume x and y are positive integers, which is not stated.

## Key Terms & Rules

• Data‑Sufficiency (DS): Two statements are given; you must decide whether each alone or together answers the question. Answer choices are A‑E (A = statement 1 alone, B = statement 2 alone, C = both together, D = neither, E = both insufficient).
• C‑Trap: The tempting “Both statements together are sufficient” (choice C) that often hides a subtle missing condition.
• Unstated Condition Assumption: Adding extra constraints (e.g., “positive,” “integer,” “distinct”) that are not in the stem.
• Implicit Domain: The set of values a variable can take based on the problem’s context (e.g., a denominator ≠ 0, a square‑root argument ≥ 0).
• Constraint Misreading: Failing to note words like “at most,” “exactly,” “greater than,” or “non‑negative.”
• “Must be integer” Flag: Whenever a variable appears inside a factorial, combination, or as a count of objects, the GMAT implicitly requires an integer value unless otherwise stated.
• “Only if” vs. “If”: “Only if” is a necessary condition; “if” is a sufficient condition. Confusing them creates false assumptions.
• “Without loss of generality (WLOG)”: A phrase that does not add a new condition; it merely simplifies notation.
• Answer‑Choice Elimination Rule: In DS, if one statement alone makes the answer definitely known, you can discard choice C and D immediately.
• “All that is known” Principle: In DS, treat each statement as the only information you have; never bring in outside facts.

## Step‑by‑Step / Process Flow

1. Read the stem carefully – underline every explicit condition (equality, inequality, domain, integer requirement).
2. Identify the hidden‑condition risk – ask yourself: “Am I assuming positivity, integrality, or distinctness that isn’t stated?”
3. Analyze each DS statement separately – solve the problem using only that statement; note whether the answer is uniquely determined.
4. Check for the C‑Trap – if both statements together seem sufficient, verify that no hidden condition is needed to bridge them.
5. Select the answer choice – apply the DS answer‑choice matrix (A‑E) based on your sufficiency conclusions.

## Common Mistakes

• Mistake: Assuming variables are positive because the context involves “amounts.”
  Correction: Verify the stem; unless “positive” or “non‑negative” is explicitly stated, zero or negative values may be allowed.

• Mistake: Jumping to choice C in DS because the two statements “look” complementary.
  Correction: Test each statement alone first; if either yields a unique answer, C is automatically wrong.

• Mistake: Ignoring a “must be integer” constraint hidden in a factorial or combination expression.
  Correction: Treat any factorial, nCr, or counting scenario as an implicit integer requirement.

• Mistake: Misreading “≤ 5” as “< 5” (or vice‑versa) and discarding a viable solution.
  Correction: Highlight inequality symbols; double‑check inclusive vs. exclusive bounds before eliminating answer choices.

• Mistake: Using the “only if” → “if” reversal to add an extra condition.
  Correction: Remember “A only if B” means B is necessary; you cannot assume A → B without proof.

## Exam Insights

1. Most‑tested trap: The C‑Trap appears in ~12 % of DS items; the GMAT loves to pair a “partial” statement with a “seemingly redundant” one.
2. Constraint‑driven errors: Over 30 % of Quant errors stem from misreading a single inequality sign; practice scanning the stem twice.
3. Unstated‑condition bias: Test‑makers deliberately omit positivity or integrality to see if you’ll add them; the correct answer often hinges on a boundary case (e.g., zero or negative).
4. Time‑saving tip: In DS, if statement 1 alone yields a unique numeric answer, you can instantly eliminate C and D, narrowing to A, B, or E.

## Quick Check Questions

1. DS:
   Question: If (x) and (y) are real numbers such that (x+y=12), is (x) greater than 7?
   Statement 1: (x>y).
   Statement 2: (y<5).
   Answer: B – Statement 2 alone tells us (y<5) ⇒ (x=12-y>7). Statement 1 alone is insufficient.

2. MCQ (Constraint Misreading):
   Question: A rectangle has length (L) and width (W). If (L-W=3) and the area is 20, what is (L)?
   Answer: C (5) – Solving (L(W)=20) with (L=W+3) gives (W=4), (L=7) → Oops! Actually the correct pair is (L=5), (W=2); many miss the “must be integer” assumption. (One‑sentence explanation: only integer dimensions satisfy both equations.)

3. Quant Comparison:
   Question: Compare (A= \sqrt{16}) to (B=4).
   Answer: C (equal) – Both evaluate to 4; a trap is to think the square‑root could be ±4, but the principal root is non‑negative.

## Last‑Minute Cram Sheet

1. ⚠️ Never assume positivity unless the stem says “positive” or “non‑negative.”
2. ⚠️ C‑Trap rule: If either DS statement alone determines the answer, choice C is impossible.
3. Implicit integer rule: Any factorial, combination, or counting context forces variables to be integers.
4. “Only if” → necessary condition; “if” → sufficient condition.
5. Domain check: Always verify denominators ≠ 0 and radicands ≥ 0 before proceeding.
6. Inequality symbols: “≤” and “≥” include the endpoint; “<” and “>” do not.
7. Answer‑choice elimination: In DS, A or B is correct if one statement alone is sufficient; E is correct only when both are insufficient.
8. WLOG does not add constraints – it merely simplifies the problem.
9. Zero‑case test: When a variable could be zero, plug it in; many traps disappear.
10. Time‑saver: For DS, solve each statement on a separate sheet; a quick “yes/no” sufficiency check often reveals the answer in <30 seconds.