🇺🇸 GMAT (Graduate Management Admission Test) · flashcards

GMAT (Graduate Management Admission Test) Data Insights: Data Sufficiency & Quantitative Integration Flashcards

51 question-and-answer cards covering Data Insights: Data Sufficiency & Quantitative Integration as it is examined in GMAT (Graduate Management Admission Test). 24 of them are printed below, taken from across the deck — no signup, no paywall on the preview.

51Cards in deck
24Free preview
12Syllabus topics
~210Chars per answer
FreePrice

24 sample cards from the Data Insights: Data Sufficiency & Quantitative Integration deck

Sampled from the end of the deck, so these are different cards from the ones shown on the syllabus page.

  1. In ratio sufficiency, why does knowing only a ratio (e.g., boys:girls = 3:2) fail to give actual quantities?

    A ratio gives relative proportions, not absolute counts — there could be 3 and 2, or 30 and 20. You need one additional concrete quantity (a total or one actual amount) to convert the ratio into specific values.

  2. In a DS ratio problem, what single extra piece of information typically makes a ratio sufficient for actual values?

    Any one actual quantity tied to the ratio — the total, the value of one part, or the difference between parts — lets you solve the multiplier and find all real values.

  3. For DS, when is a percentage change question sufficient without knowing the original amount?

    When the question asks only for the PERCENT change or a ratio of new to old, the original amount cancels out and isn't needed. It becomes insufficient when an ACTUAL dollar/quantity change is required, which needs the base value.

  4. In geometry-flavored DS, why is 'the figure is not drawn to scale' a critical warning?

    Because you cannot infer angle sizes, lengths, right angles, or relative positions from appearance. Sufficiency must come only from stated facts and theorems, never from how the figure looks.

  5. In DS geometry, what is sufficient to determine the area of a triangle?

    A base and the corresponding height, OR two sides and the included angle, OR all three sides (Heron's). Knowing only the perimeter or only two sides (without the included angle) is generally insufficient.

  6. In DS, is knowing all three angles of a triangle sufficient to find its area?

    No. Angles alone fix the SHAPE (similarity) but not the SIZE — infinitely many similar triangles of different areas share the same angles. You need at least one length.

  7. For DS, what determines whether a triangle is uniquely defined (congruence-based sufficiency)?

    The classic congruence criteria: SSS, SAS, ASA, AAS, and (for right triangles) HL. AAA fixes shape but not size, and SSA is ambiguous — recognizing these tells you when side/angle data is sufficient.

  8. In DS, what is sufficient to determine the circumference or area of a circle?

    Any one of: the radius, the diameter, the circumference, or the area — each determines all the others (C = 2πr, A = πr²). So a single such measurement is sufficient for any other circle quantity.

  9. For a DS yes/no question 'Is x > y?', why is knowing x² > y² insufficient?

    Because squaring loses sign information. x² > y² only tells you |x| > |y|; with negatives (e.g., x = -3, y = 1) you can get x² > y² while x < y. So it cannot determine the order definitively.

  10. In DS, why is a statement like 'x² = 16' often insufficient for the value of x?

    Because it yields two solutions, x = 4 or x = -4. A value question needs a unique answer, so unless another constraint (e.g., x > 0) eliminates one root, this statement alone is insufficient.

  11. What is the smart-numbers approach for DS yes/no questions specifically?

    Try to make the answer 'yes' with one allowed case and 'no' with another. If you succeed, the statement is insufficient. If after trying edge cases you can only ever get one answer, it is likely sufficient.

  12. In DS, what does it mean that you should answer the question that is ASKED, not the question you can solve?

    A statement may let you solve for a variable you weren't asked about, or partially solve. Sufficiency is judged solely against the actual question. Solving something is irrelevant unless it answers the specific quantity or yes/no posed.

  13. Why should you rephrase or simplify the DS question stem before evaluating statements?

    Simplifying (e.g., turning 'Is 2x + 4 > 10?' into 'Is x > 3?') reveals exactly what you need, exposes redundant statements, and prevents wasted work — making it obvious whether each statement actually addresses the rephrased target.

  14. In DS, when two statements give a system that is contradictory together, what does that imply about the answer?

    On the real GMAT the two statements never contradict each other (both are always true). If your work produces a contradiction when combining, you've made an error — re-check, because a genuine contradiction cannot occur.

  15. For DS, can Statement (1) and Statement (2) ever contradict one another on the actual exam?

    No. Both statements are always true simultaneously. This is a structural rule: any apparent contradiction signals a computational mistake, not a real possibility.

  16. In DS sufficiency with inequalities, why must you avoid multiplying/dividing an inequality by a variable of unknown sign?

    Because multiplying or dividing an inequality by a negative flips its direction. If the variable's sign is unknown, the operation creates two cases — often the very ambiguity that makes a statement insufficient.

  17. For a DS question about whether n is prime, what kinds of statements tend to be sufficient?

    Statements that pin n to a single value, or constrain it to a set where primality is uniform (e.g., 'n is even and n > 2' → not prime). Statements giving a range with both primes and non-primes are insufficient.

  18. In DS, what is the danger of zero as a hidden case?

    Zero is even, neither positive nor negative, makes any product zero, and is divisible by every nonzero integer. Forgetting to test x = 0 frequently breaks an otherwise 'sufficient'-looking statement, especially in yes/no and divisibility questions.

  19. For DS, when is the ratio of two quantities sufficient to answer a question even without actual values?

    When the question itself only asks for the ratio, a proportion, a percentage, or a quantity where the common scaling factor cancels. Then absolute amounts are unnecessary and the ratio alone suffices.

  20. In DS, how do you decide between answer D and answer C when both statements seem to give the answer together?

    D requires that EACH statement works ALONE. So test each in isolation: if both individually yield the answer, it's D. Only if NEITHER works alone but together they do is it C. Never default to C without the solo test.

  21. What is the recommended order of elimination after testing Statement (1) in DS?

    If (1) is sufficient, eliminate B, C, E (remaining: A or D). If (1) is insufficient, eliminate A and D (remaining: B, C, or E). Then test (2) to narrow further. This 'AD/BCE' split structures the whole process.

  22. In geometry DS, why does knowing only the perimeter of a rectangle fail to determine its area?

    Because many rectangles share a perimeter but have different areas (e.g., perimeter 20 fits 1×9 area 9 and 5×5 area 25). You need both dimensions or perimeter plus another relation (like one side or that it's a square).

  23. In DS, what makes 'x is a factor of 12' versus 'x is a multiple of 12' different for sufficiency?

    'Factor of 12' restricts x to the finite set {1,2,3,4,6,12} (and negatives if allowed) — often narrowing toward sufficiency. 'Multiple of 12' gives infinitely many values (12,24,36,...) — usually keeping a value question insufficient.

  24. What final check should you perform before locking in any Data Sufficiency answer?

    Confirm you (a) judged each statement strictly alone first, (b) answered the exact question asked, (c) tested edge cases (0, negatives, fractions, non-integers), and (d) combined ONLY if both were individually insufficient — guarding against the C-trap and unwarranted assumptions.

What this deck covers

The Data Insights: Data Sufficiency & Quantitative Integration deck follows the GMAT (Graduate Management Admission Test) Data Insights: Data Sufficiency & Quantitative Integration syllabus — 3 chapters and 12 topics — so questions land on material that is genuinely examinable rather than trivia around it. That works out to roughly 17.0 cards per chapter.

Answers are written to be recallable, not just readable — averaging about 210 characters, which is long enough to carry the reasoning and short enough to say out loud.

A deck like this earns its keep on the second and third pass. Read the syllabus first so you know the shape of the subject, then use the cards to find the specific facts that have not stuck.

Data Insights: Data Sufficiency & Quantitative Integration flashcards FAQ

How many Data Insights: Data Sufficiency & Quantitative Integration flashcards are in this GMAT (Graduate Management Admission Test) deck?

51 cards. This page previews 24 of them, sampled evenly across the deck so you can judge the difficulty before installing anything.

Are these GMAT (Graduate Management Admission Test) flashcards free?

Yes. The preview here is free to read with no signup, and the full 51-card deck is free inside the Examius app.

What do the Data Insights: Data Sufficiency & Quantitative Integration cards cover?

They follow the GMAT (Graduate Management Admission Test) Data Insights: Data Sufficiency & Quantitative Integration syllabus — 3 chapters and 12 topics — so the questions track what is actually examinable.

How should I use these flashcards?

Read the syllabus first so you know the shape of the subject, then drill the deck. Examius schedules each card with spaced repetition, so cards you keep missing come back sooner and ones you know drift further apart.