Intuition What this page is for
The parent note told you the three moving-furniture rules . This page does the drills . We will build a small table of every kind of situation these laws can throw at you — then knock down each cell with a fully worked example. When you finish, no exam variant should surprise you.
Reminder of the only two facts everything rests on:
A ⋅ B = min ( A , B ) A + B = max ( A , B )
and values are ==only 0 and 1 ==.
Think of every problem this topic can hand you as landing in one cell of the table below. Each row is a class of situation; the worked examples afterward are each tagged with the cell they cover.
#
Case class
What makes it tricky
Covered by
C1
Pure commutative re-order
spotting a hidden common factor
Example 1
C2
Pure associative re-group
2-input gates building a 3-input function
Example 2
C3
Distributive forward (AND over OR expand)
expanding to reveal cancellation
Example 3
C4
Distributive reverse (factoring)
fewest-gate goal
Example 4
C5
OR-over-AND weird form (A + B C )
the duplicated term
Example 5
C6
Degenerate input (a variable forced to 0 or 1 )
law still holds, but collapses
Example 6
C7
All same (A + A , A ⋅ A ) — limiting/repeat case
idempotent edge, easy to mis-simplify
Example 7
C8
Chained laws (comm → assoc → dist together)
order of moves
Example 8
C9
Real-world word problem
translate English → algebra
Example 9
C10
Exam twist (a trap that looks like a law but isn't)
knowing when a law does NOT apply
Example 10
We verify every numeric/logical claim below in the checker. Let's go.
Rewrite C ⋅ A + B ⋅ A so the common factor is obvious. Do not simplify yet — just re-order.
Forecast: guess which variable is common, and which side each swap happens on, before reading.
Look at term 1: C ⋅ A . Swap to A ⋅ C .
Why this step? Commutative for AND: C ⋅ A = A ⋅ C (because min ( C , A ) = min ( A , C ) ). This lines the A up on the left.
Look at term 2: B ⋅ A → A ⋅ B .
Why this step? Same law, so both terms now start with A .
Result: A ⋅ C + A ⋅ B .
Why this step? Now A is visibly the common factor — the exact set-up the distributive law needs.
Verify: truth-table both against the original. For A = 1 , B = 0 , C = 1 : original = 1 ⋅ 0 (no) … let's do it fully. C ⋅ A + B ⋅ A = 1 ⋅ 1 + 0 ⋅ 1 = 1 . Rewritten A ⋅ C + A ⋅ B = 1 ⋅ 1 + 1 ⋅ 0 = 1 . ✓ Same output — re-ordering changed nothing.
You only own 2-input OR gates but need a 3-input OR of A , B , C . Show the two legal wirings and prove they agree.
Forecast: will OR(OR(A,B),C) and OR(A,OR(B,C)) ever disagree? Guess yes/no.
Write build-1: ( A + B ) + C .
Why this step? This is "combine A , B first, then bring in C " — one physical wiring.
Write build-2: A + ( B + C ) .
Why this step? "Combine B , C first" — the other wiring.
Associative law says ( A + B ) + C = A + ( B + C ) = max ( A , B , C ) .
Why this step? max of three numbers is the same no matter which pair you compare first.
Verify: hardest row is A = 0 , B = 1 , C = 0 . Build-1: ( 0 + 1 ) + 0 = 1 + 0 = 1 . Build-2: 0 + ( 1 + 0 ) = 0 + 1 = 1 . ✓ Both 1 . And the all-zero row: ( 0 + 0 ) + 0 = 0 = 0 + ( 0 + 0 ) . ✓
Simplify A ⋅ ( A + B ) by expanding.
Forecast: guess the final single-letter answer before working.
Expand with AND-over-OR: A ⋅ ( A + B ) = A ⋅ A + A ⋅ B .
Why this step? Distributive spreads the outer A across both terms inside the bracket.
Use A ⋅ A = A (idempotent, from Boolean Algebra Identity & Null Laws ): = A + A ⋅ B .
Why this step? min ( A , A ) = A — ANDing something with itself changes nothing.
Factor A : A + A ⋅ B = A ⋅ ( 1 + B ) , and 1 + B = 1 , so = A ⋅ 1 = A .
Why this step? 1 + anything = 1 (Null/Identity law) collapses the whole tail. This is the Absorption result.
Verify: row A = 1 , B = 0 : LHS = 1 ⋅ ( 1 + 0 ) = 1 ⋅ 1 = 1 ; answer A = 1 . ✓ Row A = 0 , B = 1 : LHS = 0 ⋅ ( 0 + 1 ) = 0 ⋅ 1 = 0 ; answer 0 . ✓
Simplify A ⋅ C + A ⋅ D + A ⋅ E and count the gates before and after.
Forecast: how many gates does the raw form need? Guess, then count.
Spot the common A in all three terms.
Why this step? Reverse distributive (factoring) only works when a variable appears in every product term.
Factor it out: A ⋅ C + A ⋅ D + A ⋅ E = A ⋅ ( C + D + E ) .
Why this step? Distributive run backwards pulls the shared A outside a single OR.
Gate count. Before: 3 AND gates + 1 three-input OR = 4 gates. After: 1 three-input OR + 1 AND = 2 gates.
Why this step? Fewer gates = cheaper, faster chip — the whole payoff (see Combinational Circuit Simplification ).
Verify: row A = 1 , C = 0 , D = 1 , E = 0 : before = 0 + 1 + 0 = 1 ; after = 1 ⋅ ( 0 + 1 + 0 ) = 1 ⋅ 1 = 1 . ✓ Row A = 0 (any C , D , E ): before = 0 + 0 + 0 = 0 ; after = 0 ⋅ ( … ) = 0 . ✓ Gates saved = 4 − 2 = 2 .
Expand X + ( Y ⋅ Z ) into product-of-sums form.
Forecast: how many times must X appear in the answer? Guess 1 or 2.
Apply OR-over-AND distributive: X + Y ⋅ Z = ( X + Y ) ⋅ ( X + Z ) .
Why this step? This is the weird Boolean-only form. The lone X duplicates into both brackets — the single most-missed detail.
Sanity: does X really belong in both? Yes — if X = 1 , the whole OR is 1 , and each bracket ( 1 + Y ) = ( 1 + Z ) = 1 , product = 1 . Consistent.
Why this step? Confirms the duplication is not a typo — it is forced by the logic.
Verify: the trap row X = 1 , Y = 0 , Z = 0 . LHS = 1 + ( 0 ⋅ 0 ) = 1 + 0 = 1 . RHS = ( 1 + 0 ) ( 1 + 0 ) = 1 ⋅ 1 = 1 . ✓ The wrong single-copy form ( X + Y ) ⋅ Z = ( 1 + 0 ) ⋅ 0 = 0 — mismatch, proving why X must appear twice.
In the expression A + ( B ⋅ C ) = ( A + B ) ( A + C ) , a designer hard-wires C = 0 . Show both sides still agree.
Forecast: guess what the whole thing collapses to once C = 0 .
Substitute C = 0 into the LHS: A + ( B ⋅ 0 ) = A + 0 = A .
Why this step? B ⋅ 0 = min ( B , 0 ) = 0 (Null law), then A + 0 = A (Identity law).
Substitute C = 0 into the RHS: ( A + B ) ⋅ ( A + 0 ) = ( A + B ) ⋅ A .
Why this step? A + 0 = A collapses the second bracket.
Simplify ( A + B ) ⋅ A : this is Example 3 in disguise ⇒ A .
Why this step? Absorption — ANDing A with ( A + B ) gives back A .
Both sides = A . The law survives the degenerate input — a good design safety check.
Verify: A = 0 , B = 1 , C = 0 : LHS 0 + ( 1 ⋅ 0 ) = 0 ; RHS ( 0 + 1 ) ( 0 + 0 ) = 1 ⋅ 0 = 0 . ✓ A = 1 , B = 1 , C = 0 : LHS 1 + 0 = 1 ; RHS ( 1 + 1 ) ( 1 + 0 ) = 1 ⋅ 1 = 1 . ✓
A student writes A + A = 2 A and A ⋅ A = A 2 . Fix both, and simplify A ⋅ A + A .
Forecast: does 2 A or A 2 even exist in Boolean algebra? Guess before reading.
There is no 2 and no exponent — values are only 0 and 1 . So A + A = max ( A , A ) = A and A ⋅ A = min ( A , A ) = A .
Why this step? max and min of a number with itself return that same number (idempotent law).
Now simplify A ⋅ A + A = A + A (using step 1) = A .
Why this step? Both idempotent collapses fire, leaving a single A .
Verify: A = 1 : 1 ⋅ 1 + 1 = 1 + 1 = 1 = A . ✓ A = 0 : 0 ⋅ 0 + 0 = 0 = A . ✓ (2 A would give 2 — illegal; A 2 would give 1 here but is nonsense notation.)
Simplify B ⋅ A + C + A ⋅ C to the fewest gates. Show which law fires at each move.
Forecast: guess whether the final form contains B at all.
Commute term 1: B ⋅ A = A ⋅ B . Expression → A ⋅ B + C + A ⋅ C .
Why this step? Line up the A terms so factoring becomes visible.
Re-order (commutative on the OR chain) to group A -terms: A ⋅ B + A ⋅ C + C .
Why this step? OR is commutative, so we may sit the two A -products side by side.
Factor A from the first two (reverse distributive): A ⋅ ( B + C ) + C .
Why this step? Shared A pulls out into one AND over an OR.
Expand back the other way — actually use OR-over-AND / absorption: note A ( B + C ) + C . Test whether C absorbs. Rewrite A ( B + C ) + C = A B + A C + C ; and A C + C = C ( A + 1 ) = C .
Why this step? A + 1 = 1 (Null law) makes A C + C collapse to C — absorption.
So expression = A B + C .
Why this step? Only the A B product and the lone C survive; B does remain (inside A B ).
Final: A ⋅ B + C (1 AND + 1 OR = 2 gates).
Verify: row A = 1 , B = 1 , C = 0 : original 1 ⋅ 1 + 0 + 1 ⋅ 0 = 1 + 0 + 0 = 1 ; final 1 ⋅ 1 + 0 = 1 . ✓ Row A = 0 , B = 1 , C = 1 : original 0 + 1 + 0 = 1 ; final 0 + 1 = 1 . ✓ Row A = 1 , B = 0 , C = 0 : original 0 + 0 + 0 = 0 ; final 0 + 0 = 0 . ✓
A door unlocks if: (the master key is inserted) OR (a valid card is present AND the PIN is correct) . Let M =master, V =valid card, P =PIN correct. Write the unlock condition, then rewrite it as an all-OR-of-brackets (product-of-sums) form for a different circuit family.
Forecast: guess how many brackets the product-of-sums form has.
Translate: unlock U = M + ( V ⋅ P ) .
Why this step? "OR" = + , "AND" = ⋅ ; the card+PIN clause is one AND term.
Apply OR-over-AND distributive: M + V ⋅ P = ( M + V ) ⋅ ( M + P ) .
Why this step? Some gate libraries are cheaper with OR-then-AND; this is the equivalent build. M duplicates into both brackets.
Read it back in English: unlock if (master OR valid card) AND (master OR PIN correct) .
Why this step? Confirms the meaning is preserved — master alone still opens everything.
Verify: master alone M = 1 , V = 0 , P = 0 : form-1 = 1 + 0 = 1 ; form-2 = ( 1 + 0 ) ( 1 + 0 ) = 1 . ✓ Card but wrong PIN M = 0 , V = 1 , P = 0 : form-1 = 0 + ( 1 ⋅ 0 ) = 0 (stays locked); form-2 = ( 0 + 1 ) ( 0 + 0 ) = 1 ⋅ 0 = 0 . ✓
True or false: ( A + B ) ⋅ C = A + ( B ⋅ C ) "by associativity". If false, give the counterexample and the correct relationship.
Forecast: guess true/false before touching a truth table.
False. Associativity only re-groups one operator at a time; here we have + and ⋅ mixed, so associativity does not apply.
Why this step? Crossing operators is the distributive law's job, not associativity's.
Counterexample A = 1 , B = 0 , C = 0 : LHS ( 1 + 0 ) ⋅ 0 = 1 ⋅ 0 = 0 ; RHS 1 + ( 0 ⋅ 0 ) = 1 + 0 = 1 . 0 = 1 — not equal .
Why this step? One mismatched row is enough to kill a claimed identity.
The correct expansion of ( A + B ) ⋅ C uses distributive: ( A + B ) ⋅ C = A ⋅ C + B ⋅ C .
Why this step? AND-over-OR spreads C across the bracket — that is a valid law.
Verify: at A = 1 , B = 0 , C = 0 the correct form A ⋅ C + B ⋅ C = 0 + 0 = 0 , matching LHS 0 . ✓ At A = 0 , B = 1 , C = 1 : LHS ( 0 + 1 ) ⋅ 1 = 1 ; correct 0 ⋅ 1 + 1 ⋅ 1 = 1 . ✓ (and the false RHS A + B C = 0 + 1 = 1 happens to match here — one lucky row does NOT save it; step 2's row already broke it.)
Recall Cover the answers and speak them aloud
Factor A ⋅ P + A ⋅ Q + A ⋅ R and count gates saved vs raw.
Expand M + V ⋅ P into product-of-sums.
Why is ( A + B ) ⋅ C = A + ( B ⋅ C ) false — which law was misused?
Simplify A ⋅ ( A + B ) to a single letter and name the shortcut.
Answer to 1 A ( P + Q + R ) ; raw needs 3 AND + 1 OR = 4 gates, factored needs 1 OR + 1 AND = 2 gates, saving 2.
Answer to 2 ( M + V ) ( M + P ) — the M duplicates into both brackets.
Answer to 3 False; it mixes + and ⋅ , so associativity (same-operator only) cannot apply — you need distributive: ( A + B ) C = A C + B C .
Answer to 4 A (Absorption); A ( A + B ) = A ⋅ A + A ⋅ B = A + A B = A ( 1 + B ) = A .
Mnemonic The one-line survival kit
"Factor when a letter is in every term; duplicate the lone letter across both OR-brackets; never associate across a mixed operator — that's distributive's job."
Parent: the three laws
Boolean Algebra Identity & Null Laws (the A ⋅ A = A , A + 0 = A , 1 + X = 1 collapses used all over this page)
De Morgan's Theorems (the next simplification tool once these run out)
Logic Gates AND OR NOT (what the ⋅ , + gates physically are)
Karnaugh Maps (automates the factoring you did by hand here)
Combinational Circuit Simplification (where the gate-savings pay off)