Printable · GCSE Foundation · ages 14-16
Probability worksheet — GCSE Foundation
Fifteen questions across the probability statements at Foundation tier. Choose the non-calculator filter to rehearse Paper 1, which counts for a third of the marks.
Calculator
Answer key: Probability worksheet — GCSE Foundation
MathsUKwww.geekhero.co.uk
- (c) 0.15 — Method: for two independent events, multiply along the branches of the tree to find the probability of both outcomes happening together. Working: P(red and heads) = P(red) × P(heads) = 0.3 × 0.5 = 0.15. Answer: 0.15. Watch out: adding the two probabilities, 0.3 + 0.5 = 0.8, does not give the probability of both — probabilities along one path of a tree are multiplied, not added. Writing down 0.5 ignores the spinner altogether and gives only the coin's probability. And writing down 0.65 is the probability of red OR heads, which is 0.3 + 0.5 − 0.15 = 0.65, a different question from the one asked here.
- (b) 24/125 — On the fiction branch, 160 − 112 = 48 books were returned late. None of the non-fiction books were late, so the total number of late books is 48, out of 250 books altogether: 48/250 = 24/125. Writing 3/10 is wrong because it divides the 48 late fiction books by the fiction total (160) instead of the whole library total (250). Writing 56/125 is wrong because 112/250 simplifies to 56/125, and 112 is the number of fiction books returned ON TIME, not late. Writing 9/25 is wrong because 90/250 simplifies to 9/25, and 90 is simply the number of non-fiction books, which has nothing to do with late returns. The probability is 24/125.
- (b) The relative frequency is settling near 0.5 — Method: turn each result into a relative frequency before comparing them, because it is the relative frequency, and not the difference between the two counts, that tends towards the theoretical probability. Working: after 10 flips the relative frequency of a head is 7 ÷ 10 = 0.7, which is a long way from 0.5. After 1000 flips it is 528 ÷ 1000 = 0.528, which is much closer to 0.5. Meanwhile the gap between the two counts has grown rather than shrunk: it was 7 − 3 = 4 after 10 flips and is 528 − 472 = 56 after 1000 flips. Answer: the relative frequency is settling near 0.5, which is what an unbiased experiment does as the sample grows. The distractors: saying the counts are levelling out is the usual form of this idea and the figures contradict it, since the gap went from 4 to 56; saying the coin is biased treats 28 extra heads in 1000 flips as proof, when 0.528 sits close to 0.5 and a fair coin gives results like this often; saying the next flip is more likely to be a tail is the gambler's fallacy, since each flip stays at 1/2 whatever came before.
- (a) 0.48 — There are two ways to score exactly one throw: scoring on the first and missing the second, 0.6 × 0.4 = 0.24, or missing the first and scoring the second, 0.4 × 0.6 = 0.24. Adding these gives 0.24 + 0.24 = 0.48. Choosing 0.24 comes from working out only one of the two paths and forgetting the other one also gives exactly one score. Choosing 0.36 comes from working out the probability of scoring BOTH throws, 0.6 × 0.6 = 0.36, instead of exactly one. Choosing 0.84 comes from working out the probability of scoring AT LEAST one throw, 1 − 0.4 × 0.4 = 0.84, instead of exactly one.
- (a) Game B, by £8 — Game A's expected total is 40 × 0.2 × £5 = £40. Game B's expected total is 40 × 0.1 × £12 = £48. Game B is higher, by £48 − £40 = £8. Writing 'Game A, by £8' is wrong because it has the right difference but the wrong game — Game A's total (£40) is actually LOWER than Game B's, not higher. Writing 'Game B, by £48' is wrong because £48 is Game B's whole expected total, not the DIFFERENCE between the two games. Writing 'Game A, by £40' is wrong in the same way, using Game A's whole total as if it were the margin, and naming the wrong game as the winner. Game B gives the higher expected total, by £8.
- (a) 0.36 — Relative frequency is the number of times the event happened divided by the total number of trials: 18 ÷ 50 = 0.36. Dividing by 100 instead of the actual 50 spins gives 18 ÷ 100 = 0.18. Finding the relative frequency of NOT landing on green, using 50 − 18 = 32 spins, gives 32 ÷ 50 = 0.64. Misplacing the decimal point in the division, so that 18 ÷ 50 is carried out as 18 ÷ 500, gives 0.036 — a tenth of the correct value.
- (a) 0.30 — Red, blue, green and yellow are exhaustive, so all four probabilities sum to 1: 0.24 + 0.16 + x + x = 1, so 2x + 0.40 = 1, giving 2x = 0.60 and x = 0.30. Stopping at 2x = 0.60 without dividing by 2 leaves 0.60, the combined probability of both blue and green together, not the value of x on its own. Sharing the 0.60 across all four colours instead of just the two unknown ones gives 0.60 ÷ 4 = 0.15. Leaving out the 0.16 for yellow gives 2x + 0.24 = 1, so 2x = 0.76 and x = 0.38.
- (a) £150 — Each game, the expected payout is 0.1 × £20 = £2, so the fête's expected profit per game is the £3 charged minus the £2 expected payout, £1. Over 150 games, that is 150 × £1 = £150. Writing £300 is wrong because 150 × £2 = £300 is the total expected PAYOUT, not the profit — it has not been subtracted from the entry fees. Writing £450 is wrong because 150 × £3 = £450 is the total money taken in entry fees, without accounting for what is expected to be paid out in prizes. Writing £1 is wrong because that is only the expected profit for ONE game — it has not been scaled up to all 150 games. The fête's expected profit is £150.
- (b) 3/5 — The question asks about the girls only, so use the girls' total of 70 as the denominator: 42 out of 70 girls walk, giving 42/70 = 3/5. Choosing 21/65 comes from using the whole survey of 130 pupils as the denominator instead of just the 70 girls, 42/130 = 21/65. Choosing 33/70 comes from using the boys' walking count, 33, over the girls' total of 70, mixing up the two rows of the table. Choosing 2/5 comes from using the number of girls who CYCLE, 70 − 42 = 28, instead of the number who walk, giving 28/70 = 2/5.
- (b) 500 — Method: when a dice is known to be fair, the theoretical probability is the best thing to work from, and the more trials there are the closer the results tend to it. Working: for a fair dice the probability of a six is 1/6, so the expected number of sixes in 3000 rolls is 3000 × 1 ÷ 6 = 500. The class experiment gave a relative frequency of 14/60, but 60 trials is far too few to overturn a known theoretical value, and the school's 3000 rolls will tend towards 1/6 in any case. Answer: about 500 sixes. The distractors: 700 comes from using the class relative frequency instead of the theory, 3000 × 14 ÷ 60 = 700; 600 comes from splitting the difference between the two, since 1/6 is about 0.167 and 14/60 is about 0.233, whose mean is 0.2, and 3000 × 0.2 = 600; 2500 uses 5/6 instead of 1/6 and counts the rolls expected not to be a six.
- (b) £100 — Over 250 games, the expected total winnings are 250 × (1/5) × £12 = £600, since a player wins on 1 of the 5 equally likely sections. The total cost of playing is 250 × £2 = £500. The players' expected profit is the winnings minus the cost: £600 − £500 = £100. Writing £500 is wrong because that is only the total cost of playing, without any winnings included. Writing £600 is wrong because that is only the total expected winnings, without subtracting what was paid to play. Writing £2,500 is wrong because it assumes a win on every single game (250 × £12 = £3,000) instead of using the 1-in-5 probability, then subtracts the cost: £3,000 − £500 = £2,500. The players' expected profit over the 250 games is £100.
- (c) 0.5 — Method: count the favourable outcomes, write them over the total number of equally likely outcomes and then divide to turn the fraction into a decimal. Working: the odd scores are 1, 3 and 5, which is 3 of the 6 equally likely scores, so the probability is 3/6, and 3 ÷ 6 = 0.5. Answer: 0.5, the middle of the 0 to 1 probability scale. The distractors: 0.33 comes from listing only 3 and 5 as odd and working out 2 ÷ 6; 0.17 comes from giving the probability of one particular odd score, 1 ÷ 6; 0.3 comes from writing '3 out of 6' as 0.3, reading the 3 straight off as tenths instead of dividing.
- (c) 1/10 — On the adult branch, 210 − 189 = 21 appointments were missed. There are 300 − 210 = 90 child appointments, and 90 − 81 = 9 of those were missed. In total, 21 + 9 = 30 appointments were missed, out of 300: 30/300 = 1/10. Writing 7/100 is wrong because 21/300 simplifies to 7/100, and 21 only counts the adult branch, leaving out the 9 missed child appointments. Writing 3/100 is wrong because 9/300 simplifies to 3/100, and 9 only counts the child branch, leaving out the 21 missed adult appointments. Writing 1/9 is wrong because it divides the 30 missed appointments by the 270 that were attended (300 − 30) instead of by the whole 300 booked. The probability is 1/10.
- (a) 753 — The estimate from 2000 spins is the most reliable, since it comes from the largest sample size, so the best estimate of the probability is 0.251. Over a further 3000 spins, the expected number landing on green is 3000 × 0.251 = 753. Writing 1050 is wrong because 3000 × 0.350 = 1050 uses the estimate from only 20 spins, the LEAST reliable of the three. Writing 870 is wrong because 3000 × 0.290 = 870 uses the estimate from 200 spins rather than the more reliable 2000-spin estimate. Writing 750 is wrong because 3000 × 0.25 = 750 ignores the recorded data completely and simply assumes each of the 4 colours is equally likely. The best estimate is 753 expected green spins.
- (c) 80 — Since 180 calls are 0.75 of all the technical support calls, the technical support total is 180 ÷ 0.75 = 240. The billing calls make up the rest of the 320 calls, so 320 − 240 = 80. Choosing 240 comes from stopping after finding the technical support total and forgetting the question asks for the billing calls, which are the rest. Choosing 185 comes from multiplying 180 × 0.75 = 135 instead of dividing, then working out 320 − 135 = 185. Choosing 140 comes from using 180 directly as the whole technical support total, ignoring the probability altogether, then working out 320 − 180 = 140.
Build your own mix at the worksheet builder.