LSAT Logic Games Must Be False Questions

Must Be False questions are a unique and powerful test of your command of a Logic Games setup. While many questions ask what could or must be true, these require you to identify the single answer choice that cannot be true under any valid interpretation of the rules. Mastering them demands more than rule memorization; it rewards a deep, synthesized understanding of how all the constraints interact to shape the possible worlds of the game.

Understanding the "Must Be False" Task

The prompt for these questions is typically: "Which one of the following must be false?" or "Each of the following could be true EXCEPT." Your task is to find the statement that is impossible. The four incorrect answers are all possible—they could happen in at least one scenario consistent with the rules. The correct answer violates the rules, either directly or through their logical implications. This question type is excellent for forcing you to see the boundaries of what the game allows. Success hinges on moving beyond listing what can happen to clearly defining what cannot.

To attack these questions, you have three primary, hierarchical strategies. Start with the most efficient method and proceed to the next only if needed.

Strategy 1: Check for Direct Rule Violations

Your first and fastest filter is to compare each answer choice directly against the stated rules. Often, the correct answer will blatantly break a rule given in the initial scenario. For example, if a sequencing rule states, "F is interviewed earlier than G," an answer choice that places G before F is immediately and definitively false. Scan for these direct contradictions.

However, the LSAT rarely makes it this simple. More commonly, the violation is subtler, involving a combination of rules. An answer might not break any single rule in isolation but creates a situation where complying with one rule forces you to break another. For instance, if you have the rules "A is in spot 1 or 3" and "If A is in spot 1, then B is in spot 5," an answer placing A in spot 1 and B in spot 3 violates the conditional rule. It's not a direct violation of the first rule, but it makes the conditional statement false. Treat conditional logic with extreme care here.

Strategy 2: Apply Deduced Global Constraints

When a direct violation isn't apparent, you must leverage your global deductions. These are the inferences you draw by combining two or more rules before even looking at the questions. They represent unavoidable truths that govern every valid scenario.

Common global deductions include:

• Blocked Positions: In sequencing, if X must be before Y and Y must be before Z, then X must be before Z (transitivity).
• Limited Options: In grouping, if only two spaces are available for three elements that cannot go together, one of those elements must be out.
• Numerical Distributions: In hybrid games, determining fixed numbers of elements assigned to different categories.

The correct Must Be False answer will often conflict with one of these powerful, non-negotiable inferences. If your deduction proves that "K must be in group 2," then any answer choice placing K in group 1 must be false. This is why robust upfront diagramming and deduction are critical; they provide the bedrock for efficiently eliminating many answer choices.

Strategy 3: Test Against Established Valid Scenarios

When the first two strategies don't yield a clear answer, you must test the choices against what you know is possible. This is where your work on previous questions becomes invaluable. A valid scenario you created for an earlier "Could Be True" question is a perfect template.

The Testing Process:

1. Try to Make It True: Take the statement in the answer choice as a new, temporary rule.
2. Incorporate into a Known Framework: Add this temporary rule to your original diagram and rules.
3. Attempt a Placement: Try to place the remaining elements without breaking any original rule or global deduction.

If you can successfully create a complete, valid scenario that includes the statement, then that statement could be true, and you eliminate it. You only need one valid scenario to eliminate an answer. The correct "must be false" answer is the one for which you cannot create any valid scenario—every attempt leads to a contradiction.

Efficiency Tip: Start testing with the most restrictive or unusual-looking answer choices. Often, the most constrained or specific scenario is the impossible one. Also, if you have two seemingly similar answers, testing one can often prove the other false by implication.

Common Pitfalls

1. Confusing "Must Be False" with "Could Be False": This is the cardinal error. Remember, four answers could be true (they are possible). You are hunting for the one that is impossible. Do not eliminate an answer just because it seems unlikely or restrictive; you must prove it cannot happen.
2. Neglecting Conditional Logic Chains: A statement might not violate a rule's sufficient condition but can violate its necessary condition when combined with another fact. For example, with rules "If P, then Q" and "If R, then not Q," an answer placing P and R together must be false, as it would force Q and not Q to both be true. Map out your conditional chains clearly.
3. Failing to Use Previous Work: You are not meant to solve each question in a vacuum. A scenario you drew for question 2 is a pre-tested valid arrangement. If an answer choice describes that exact scenario, it is clearly possible. Use your prior diagrams to save massive time.
4. Over-testing the Wrong Answer: Once you find an answer that leads to a contradiction, you have likely found the correct choice. Briefly confirm the contradiction is unavoidable, then select it and move on. Do not feel obligated to test all five choices exhaustively every time.

Summary

• Must Be False questions ask for the impossible answer—the one that violates the game's boundaries.
• Employ a three-step strategy: First, look for direct rule violations. Second, apply your global deductions. Third, test stubborn answers against known valid scenarios.
• Your upfront work is crucial: Strong initial diagrams and deduced constraints are your most efficient tools for solving these questions quickly.
• Avoid the "could be false" trap: You are not looking for a statement that is merely not always true; you are looking for the statement that is never true under the given rules.
• Use the test's structure to your advantage: Valid scenarios from earlier questions are powerful evidence for eliminating incorrect "must be false" answer choices.