What is the goal in Data Sufficiency?
NOT to solve the problem fully. The goal is to determine whether the information provided is enough to answer the question uniquely. You are judging sufficiency, not computing answers.
What are the five answer choices in Data Sufficiency?
(A) Statement 1 alone is sufficient (B) Statement 2 alone is sufficient (C) Both together are sufficient (D) Each alone is sufficient (E) Even together are not sufficient. Memorize this pattern. It never changes.
What is the correct order to test statements?
1️⃣ Test Statement 1 alone. 2️⃣ Test Statement 2 alone. 3️⃣ Only then test both together if needed. Never combine too early.
What does “sufficient” mean?
You can determine exactly one answer. If multiple answers are possible → insufficient.
If the question asks “What is the value of x?” what qualifies as sufficient?
You must get one exact value of x. Not a range. Not two possibilities. Exactly one.
If the question asks a Yes/No question, what qualifies as sufficient?
You must get a definitive Yes OR No. If answer could be Yes in one case and No in another → insufficient.
What is the biggest DS mistake?
Solving fully instead of testing variability. The key question is always: “Could it be different?”
What mental question should you ask after testing a statement?
Can I create another valid scenario that gives a different answer? If yes → insufficient.
Why should you avoid over-calculating?
Because DS is about logical sufficiency, not numeric precision. Often logic eliminates answers faster than algebra.
What is the fastest elimination shortcut in DS?
If Statement 1 is sufficient alone → eliminate B, C, E immediately.
If Statement 2 alone is sufficient, what can you eliminate?
Eliminate A, C, E immediately.
When should you plug in numbers in DS?
When variables are abstract and conditions allow multiple possibilities. Testing values exposes hidden insufficiency.
What kinds of numbers should you test in DS?
Positive numbers Negative numbers Zero Fractions. Many DS traps hide in neglected cases.
Why must you test zero explicitly?
Zero often changes multiplication/division logic. Many statements fail at zero.
Why test negative numbers?
Inequalities and absolute values often reverse behavior with negatives.
If multiplying or dividing by a negative in inequality, what happens?
The inequality sign flips. This is a common DS sufficiency trap.
If statement gives x² = 9, is x uniquely determined?
No. x = 3 or −3. Multiple values → insufficient.
If statement gives x > 0 and x² = 9, is it sufficient?
Yes. Now x = 3 only.
If statement says x > 5, can you determine x?
No. Infinite possible values → insufficient.
If you can narrow x to a range (e.g., 2 < x < 4), is that sufficient?
No. Unless the question only asks a Yes/No that range resolves.
When can a range be sufficient?
If the question asks something like “Is x > 0?” And the entire range satisfies the condition.
When should you combine statements?
Only after testing each independently. Never assume they must work together.
If each statement alone gives multiple values but together give one value, answer is?
(C)
If each statement alone gives one unique answer, answer is?
(D)