Study guide
13.4 Table Analysis: Evaluating Binary Statements (True/False, Yes/No)
GMAT Exam Focus Edition
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: GMAT Exam Architecture & Strategic Foundations
1.1 GMAT Structure, Section Order, and the 205–805 Score Scale 1.2 Question Bookmarking and the Review & Edit Feature Mechanics 1.3 Test-Day Logistics, Pacing Architecture, and Score Reporting Policies
2 Chapter 2: Quantitative Reasoning — Arithmetic & Number Properties
2.1 Integers, Divisibility Rules, Prime Factorization, and LCM/GCD 2.2 Remainders, Even/Odd Parity, and Positive/Negative Sign Analysis 2.3 Exponents, Radicals, Roots, and Scientific Notation 2.4 Absolute Value, Number Line Properties, and Estimation Techniques
3 Chapter 3: Quantitative Reasoning — Fractions, Decimals, Ratios & Percentages
3.1 Fractions, Decimals, and Real-Number Operations 3.2 Ratios, Proportions, and Scaling Relationships 3.3 Percent Change, Successive Percent Changes, and Multipliers 3.4 Commercial Math: Profit/Loss, Markups, Discounts, and Simple/Compound Interest
4 Chapter 4: Quantitative Reasoning — Algebra, Equations & Inequalities
4.1 Linear Equations and Systems of Simultaneous Equations 4.2 Quadratic Equations, Factoring Patterns, and Roots 4.3 Linear Inequalities, Compound Inequalities, and Absolute Value Inequalities 4.4 Functions, Defined Operational Symbols, and Sequences
5 Chapter 5: Quantitative Reasoning — Word Problems & Modeling
5.1 Rate, Time, and Distance: Uniform Motion, Relative Speed, and Average Speed 5.2 Work Rates: Combined Rates, Sequential Tasks, and Opposing Rates 5.3 Mixture Problems and Weighted Averages 5.4 Overlapping Sets, Venn Diagrams, and the Double-Set Matrix Method
6 Chapter 6: Quantitative Reasoning — Counting, Probability & Statistics
6.1 Fundamental Counting Principle, Permutations, and Combinations 6.2 Probability Rules: Independent, Dependent, Mutually Exclusive, and Complementary Events 6.3 Descriptive Statistics: Mean, Median, Mode, Range, and Weighted Mean 6.4 Standard Deviation, Variance, and Data Dispersion
7 Chapter 7: Verbal Reasoning — Critical Reasoning: Argument Structure & Assumptions
7.1 Anatomy of an Argument: Conclusions, Premises, Assumptions, and Background Context 7.2 Assumption Questions: Necessary vs. Sufficient Assumptions and the Negation Test 7.3 Strengthen Questions: Supporting Premises, Causality, and New Evidence 7.4 Weaken Questions: Identifying Flaws, Alternate Causes, and Counter-Evidence
8 Chapter 8: Verbal Reasoning — Critical Reasoning: Advanced Arguments
8.1 Evaluate the Argument: The Variance Test and Decisive Information 8.2 Resolve the Paradox: Reconciling Conflicting Facts and Surprising Outcomes 8.3 Boldface and Method of Reasoning: Identifying the Role of Statements 8.4 Flaw in the Reasoning: Spotting Formal and Informal Logical Fallacies
9 Chapter 9: Verbal Reasoning — Reading Comprehension: Core Analysis
9.1 Passage Structures, Main Idea, and Author's Primary Purpose 9.2 Supporting Ideas, Explicit Details, and Targeted Information Retrieval 9.3 Inference Questions: Deriving Unstated Claims and Valid Deductions
10 Chapter 10: Verbal Reasoning — Reading Comprehension: Advanced Strategies
10.1 Author's Tone, Attitude, and Epistemic Stance 10.2 Logical Structure, Paragraph Function, and Rhetorical Organization 10.3 Application, Contextual Analogy, and Cross-Disciplinary Synthesis
11 Chapter 11: Data Insights — Data Sufficiency Foundations & Algebra
11.1 Data Sufficiency Architecture: The 5 Answer Choices (AD/BCE) and Yes/No vs. Value Logic 11.2 Golden Rules of DS: Preventing Statement 2 Contamination and Sufficiency Verification 11.3 DS Applied to Arithmetic, Number Properties, and Signs 11.4 DS Applied to Algebraic Equations, Systems, and Inequalities
12 Chapter 12: Data Insights — Data Sufficiency Applied Modeling
12.1 DS Applied to Rates, Ratios, and Work Problems 12.2 DS Applied to Statistics, Averages, and Data Sets 12.3 DS Applied to Overlapping Sets, Venn Diagrams, and Probability
13 Chapter 13: Data Insights — Multi-Source Reasoning & Table Analysis
13.1 Multi-Source Reasoning: Tab Navigation, Synthesizing Text, Data, and Emails 13.2 MSR Question Formats: Multiple Choice and Three-Part Dichotomous Questions 13.3 Table Analysis: Interactive Sorting, Filtering, and Trend Identification 13.4 Table Analysis: Evaluating Binary Statements (True/False, Yes/No)
14 Chapter 14: Data Insights — Graphics Interpretation & Two-Part Analysis
14.1 Graphics Interpretation: Bar Charts, Line Graphs, and Scatterplots 14.2 Graphics Interpretation: Bubble Charts, Dual-Axis Graphs, and Pie Charts 14.3 Two-Part Analysis: Quantitative and Mathematical Word Problems 14.4 Two-Part Analysis: Verbal, Logic-Based, and Strategic Decision Problems
13.4 Table Analysis: Evaluating Binary Statements (True/False, Yes/No)
Key Takeaways Explain This Topic AI
In Table Analysis dichotomous evaluations, each statement functions as a formal mathematical or logical hypothesis that must be rigorously verified against the table data.
Conditional statements ('If X > 50, then Y...') require filtering your sample strictly to rows that satisfy the antecedent condition; rows failing the 'if' condition are completely irrelevant and cannot disprove the claim.
Maintain strict distinction between absolute change (value difference) and percentage change (relative change scaled by the initial base value); large absolute gains often correspond to modest percentage increases on high baselines.
To compare column ratios across rows without performing tedious long division, use the cross-multiplication principle: a/b > c/d is mathematically equivalent to a d > b c for positive quantities.
Watch for the 'Weighted Average Fallacy': the average of subgroup averages does not equal the grand average of the population unless each subgroup contains the exact same number of observations.
Last updated: September 2026
13.4 Table Analysis: Evaluating Binary Statements (True/False, Yes/No)
Quick Summary: The final challenge of Table Analysis on the GMAT Focus Edition is executing three consecutive binary evaluations ( Yes/No or True/False ) under strict all-or-nothing scoring. Rather than testing basic arithmetic, these statements test your command of formal logic and quantitative reasoning: evaluating conditional claims with precise subset filtering, distinguishing absolute changes from percentage growth rates , executing rapid ratio comparisons without manual division, and avoiding aggregation errors such as the weighted average fallacy . Mastering these four core statement archetypes ensures complete accuracy across all three parts.
The Logic of Conditional Statements in Table Analysis
One of the most frequent statement formats in Table Analysis is the conditional claim : "If P , then Q " ( P ⟹ Q ) \text{"If } P, \text{ then } Q\text{" } \quad (P \implies Q) "If P , then Q " ( P ⟹ Q )
Examples include:
- "If a hospital has more than 300 beds, its patient readmission rate is below 8.0%."
- "Any tech startup founded after 2020 that secured Series B funding achieved profitability by 2024."
- The Scope Filter Protocol
When evaluating P ⟹ Q P \implies Q P ⟹ Q , you must apply the Scope Filter :
Filter Strictly for P (The Antecedent): Sort the table to isolate only the rows where condition P is True . In the hospital example, you isolate only hospitals with > 300 beds.
Test for Q (The Consequent) Exclusively within that Subgroup: Inspect condition Q (readmission rate < 8.0%) among those filtered rows.
If every single row in the filtered subset satisfies Q, the statement is Yes (True) .
If even one row in the filtered subset fails Q (e.g., a 350-bed hospital has an 8.2% readmission rate), the statement is No (False) .
Ignore Non-P Rows Completely: Rows where P is False (hospitals with <= 300 beds) are wholly irrelevant . A 150-bed hospital with a 12% readmission rate does NOT invalidate the statement!
The Trap of Affirming the Consequent
A classic trap occurs when test-takers look at rows where Q is true and assume the statement requires P to be true.
Example: Finding an 80-bed hospital with a 6.5% readmission rate does not violate "If beds > 300, then readmission < 8.0%" . The statement never claimed that only large hospitals have low readmission rates (Q implies P). Do not confuse a conditional statement with its converse.
Absolute Change vs. Percentage Change
Table Analysis statements frequently exploit the mathematical distinction between absolute differences and relative percentage changes . Absolute Change = Y final − Y initial \text{Absolute Change} = Y_{\text{final}} - Y_{\text{initial}} Absolute Change = Y final − Y initial Percentage Change = ( Y final − Y initial Y initial ) × 100 % \text{Percentage Change} = \left( \frac{Y_{\text{final}} - Y_{\text{initial}}}{Y_{\text{initial}}} \right) \times 100\% Percentage Change = ( Y initial Y final − Y initial ) × 100%
The Base-Value Distortion
Consider two companies in a table over a three-year period:
- Company 2022 Revenue 2025 Revenue Absolute Increase Percentage Increase
- Titan Corp $500 Million $650 Million +$150 Million (150 / 500) = +30.0%
- Venture Inc $10 Million $25 Million +$15 Million (15 / 10) = +150.0%
Notice the opposing outcomes:
Titan Corp achieved by far the greatest absolute revenue gain (+$150M vs +$15M).
Venture Inc achieved by far the greatest percentage revenue growth (+150% vs +30%).
When a Table Analysis statement uses words like "grew by the largest amount" , "greatest increase" , or "largest difference" , it specifies absolute change . When it uses words like "highest growth rate" , "greatest percentage increase" , or "expanded most rapidly" , it specifies percentage change . Never substitute one for the other.
Ratio Comparisons: The Cross-Multiplication Principle
When a statement asks you to compare ratios across different rows (e.g., "The ratio of R&D expenditure to operating profit was higher for Firm A than for Firm B" ), test-takers often open the on-screen calculator and perform two separate long divisions, rounding decimals and wasting time.
Instead, use the fundamental algebraic property of fractions for positive numbers: a b > c d ⟺ a × d > b × c \frac{a}{b} > \frac{c}{d} \iff a \times d > b \times c b a > d c ⟺ a × d > b × c
Application
Suppose Firm A has R&D of $42M and Profit of $130M. Firm B has R&D of $31M and Profit of $98M. Is (42 / 130) > (31 / 98)?
Rather than dividing 42 / 130 ≈ 0.3230 and 31 / 98 ≈ 0.3163, cross-multiply: 42 × 98 = 4 , 116 42 \times 98 = 4,116 42 × 98 = 4 , 116 130 × 31 = 4 , 030 130 \times 31 = 4,030 130 × 31 = 4 , 030
Because 4,116 > 4,030, the inequality (42 / 130) > (31 / 98) is proven immediately with two simple multiplications on the on-screen calculator.
Aggregation Traps and the Weighted Average Fallacy
A pervasive trap in Table Analysis involves statements that claim to deduce an overall aggregate mean from individual subgroup averages. True Population Mean = ∑ ( w i × x ˉ i ) ∑ w i ≠ ∑ x ˉ i k \text{True Population Mean} = \frac{\sum (w_i \times \bar{x}_i)}{\sum w_i} \neq \frac{\sum \bar{x}_i}{k} True Population Mean = ∑ w i ∑ ( w i × x ˉ i ) = k ∑ x ˉ i
If a table lists the average employee salary for 5 regional divisions, you cannot compute the company-wide average salary by simply summing the 5 regional averages and dividing by 5, unless each division has the exact same number of employees .
If the statement claims "The average salary of all employees across the 5 divisions is $72,000" , but the table provides only the divisional averages without the employee headcount per division, the statement cannot be inferred . You must select No because the weights are unknown.
Comprehensive Worked Example: Renewable Energy Infrastructure
Let us analyze a comprehensive Table Analysis dataset containing 12 renewable power generation assets.
Contextual Narrative
The table displays operational and financial metrics for 12 utility-scale renewable energy facilities commissioned between 2021 and 2024. Capital Expenditure (CapEx) represents total upfront installation costs in millions of dollars. Annual Generation is reported in gigawatt-hours (GWh) for the year 2025. Capacity Factor is the ratio of actual energy produced to the maximum possible electrical output if operated continuously at full nameplate capacity throughout the entire year. Levelized Cost of Energy (LCOE) is the estimated net present cost of electricity generation over the facility lifetime, expressed in dollars per megawatt-hour ($/MWh).
Table: Utility-Scale Renewable Energy Projects
- Project Code Technology CapEx ($M) Annual Generation (GWh) Capacity Factor (%) LCOE ($/MWh)
- PRJ-101 Offshore Wind 450 1,200 48.5 68.0
- PRJ-102 Solar PV 180 380 24.0 41.5
- PRJ-103 Onshore Wind 220 620 36.5 44.0
- PRJ-104 Geothermal 310 710 88.0 52.0
- PRJ-105 Solar PV 140 310 25.5 39.0
- PRJ-106 Offshore Wind 520 1,450 51.0 72.5
- PRJ-107 Biomass 160 420 76.0 78.0
- PRJ-108 Onshore Wind 190 540 34.0 46.5
- PRJ-109 Solar PV 210 490 26.0 37.5
- PRJ-110 Hydroelectric 680 1,850 58.0 49.0
- PRJ-111 Geothermal 280 640 85.0 55.0
- PRJ-112 Onshore Wind 250 690 38.0 42.0
- Step-by-Step Problem Walkthrough
Task: For each of the following statements, select Yes if the statement can be reasonably inferred from the table. Otherwise, select No .
If a project has an LCOE of less than $45.0/MWh, its Capacity Factor is less than 40.0%.
The project with the highest ratio of Annual Generation to CapEx is a Solar PV facility.
The mean CapEx of the three facilities with the highest Capacity Factors exceeds $300 million.
- Analytical Deconstruction
- Statement 1: Conditional Claim with Scope Filter
Identify the Condition (P implies Q):
P: Project has LCOE < $45.0/MWh.
Q: Capacity Factor is < 40.0%.
Apply the Scope Filter: Isolate all projects where LCOE < 45.0:
- PRJ-102 (Solar PV): LCOE = 41.5, Capacity Factor = 24.0%
- PRJ-103 (Onshore Wind): LCOE = 44.0, Capacity Factor = 36.5%
- PRJ-105 (Solar PV): LCOE = 39.0, Capacity Factor = 25.5%
- PRJ-109 (Solar PV): LCOE = 37.5, Capacity Factor = 26.0%
- PRJ-112 (Onshore Wind): LCOE = 42.0, Capacity Factor = 38.0%
Test Condition Q across all filtered projects:
Capacity Factors: 24.0%, 36.5%, 25.5%, 26.0%, 38.0%.
The maximum Capacity Factor in this subset is 38.0%, which is strictly less than 40.0%.
Check Irrelevant Rows: Note that other projects have Capacity Factors > 40% (e.g., Geothermal, Hydroelectric, Offshore Wind), but their LCOE values are all >= $49.0/MWh, meaning they fall outside the conditional antecedent. Every single project meeting the 'if' condition satisfies the 'then' condition.
Verdict for Statement 1: Yes .
Statement 2: Ratio Comparison across Technologies
Identify Target Ratio: Generation / CapEx = Annual Generation (GWh) / CapEx ($M).
Scan Promising Candidates:
Solar PV projects:
- PRJ-102: 380 / 180 ≈ 2.111 GWh/$M
- PRJ-105: 310 / 140 ≈ 2.214 GWh/$M
- PRJ-109: 490 / 210 = 7 / 3 ≈ 2.333 GWh/$M
Onshore Wind projects:
- PRJ-103: 620 / 220 ≈ 2.818 GWh/$M
- PRJ-108: 540 / 190 ≈ 2.842 GWh/$M
- PRJ-112: 690 / 250 = 2.760 GWh/$M
Offshore Wind and Hydro:
- PRJ-101: 1,200 / 450 ≈ 2.667
- PRJ-106: 1,450 / 520 ≈ 2.788
- PRJ-110: 1,850 / 680 ≈ 2.721
Compare Maxima:
The highest Solar PV ratio is PRJ-109 at 490 / 210 ≈ 2.333.
But Onshore Wind facility PRJ-108 achieves 540 / 190 ≈ 2.842.
Cross-multiplication verification between PRJ-108 (Wind) and PRJ-109 (Solar): 540 × 210 = 113 , 400 vs 190 × 490 = 93 , 100 540 \times 210 = 113,400 \quad \text{vs} \quad 190 \times 490 = 93,100 540 × 210 = 113 , 400 vs 190 × 490 = 93 , 100
Because 113,400 > 93,100, PRJ-108 has a strictly higher generation-to-CapEx ratio than PRJ-109.
Verdict: The project with the highest ratio is PRJ-108 (an Onshore Wind facility), NOT a Solar PV facility.
Verdict for Statement 2: No .
Statement 3: Mean of Top 3 Capacity Factors
Operation: Sort by Capacity Factor (%) descending.
Isolate Top 3 Rows:
- Rank 1: PRJ-104 (Geothermal) — Capacity Factor = 88.0%, CapEx = $310M
- Rank 2: PRJ-111 (Geothermal) — Capacity Factor = 85.0%, CapEx = $280M
- Rank 3: PRJ-107 (Biomass) — Capacity Factor = 76.0%, CapEx = $160M
Compute Mean CapEx of these three projects: Sum of CapEx = 310 + 280 + 160 = 750 \text{Sum of CapEx} = 310 + 280 + 160 = 750 Sum of CapEx = 310 + 280 + 160 = 750 Mean CapEx = 750 3 = $ 250 million \text{Mean CapEx} = \frac{750}{3} = \$250 \text{ million} Mean CapEx = 3 750 = $250 million
Evaluate Value: The statement claims the mean CapEx exceeds $300 million. Because $250M is not greater than $300M, the statement is false.
Verdict for Statement 3: No .
Final Correct Dichotomous Triplet: Statement 1 = Yes ; Statement 2 = No ; Statement 3 = No .
Trap Catalog for Dichotomous Table Analysis
The Causation Fallacy: Inferring that a low LCOE was caused by a specific technology or region when the table merely documents numerical correlation.
Converse Statement Inversion: Assuming that because all projects with LCOE < 45 have Capacity Factor < 40%, all projects with Capacity Factor < 40% must have LCOE < 45.
The Unweighted Grand Mean Trap: Averaging the Capacity Factors of technologies with unequal project counts and treating it as the system-wide capacity factor.
Neglecting Column Units: Misinterpreting CapEx in millions ($M) versus generation in gigawatt-hours (GWh), resulting in decimal placement errors during manual calculation.