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
- (d) 136 — 15% of 160 = 0.15 × 160 = 24 patients reported side effects, so 160 − 24 = 136 did not. Stopping after finding the number who reported side effects, 24, answers the wrong question — it is not the number who did NOT report them. Misreading '15%' as a raw count of 15 patients, rather than a percentage, gives 160 − 15 = 145. Subtracting 15% of 160 twice, 160 − 24 − 24 = 112, double-counts the side-effect group.
- (b) 3/10 — The number who use at least one app is 90 − 20 = 70. Since 55 + 42 double-counts the overlap, n(X ∩ Y) = 55 + 42 − 70 = 27, so P(both) = 27/90 = 3/10. Forgetting to subtract the 20 who use neither, and using the full 90 as the union, gives 55 + 42 − 90 = 7, so 7/90. Reporting the probability of using X or Y (or both), 70/90 = 7/9, answers a different question about the union, not the overlap. Reporting the probability of using neither app, 20/90 = 2/9, is the complement of the union, not the intersection.
- (c) 102 — Method: turn the past record into a relative frequency, then use it as an estimate of the probability of rain and multiply by the number of days being predicted for. Working: relative frequency of rain = 70 ÷ 250 = 0.28. Expected rainy days in 365 days = 365 × 0.28 = 102.2, which rounds to about 102 days. Answer: about 102 days. Watch out: writing down 48 swaps which number is the sample and which is the target, working out 70 ÷ 365 × 250 instead of 70 ÷ 250 × 365. Writing down 70 just repeats the original count of rainy days without scaling it up to the new, longer period at all. And writing down 110 comes from rounding the relative frequency to 0.3 before multiplying, 365 × 0.3 = 109.5, when 70 ÷ 250 is exactly 0.28 and needs no rounding at all.
- (b) £100 — Method: find the expected number of wins, turn that into the expected pay out, then compare it with what the games cost. Working: the expected number of wins is 200 × 0.15 = 30. Each win pays £10, so the expected pay out is 30 × 10 = 300 pounds. Playing 200 times at £2 a go costs 200 × 2 = 400 pounds. The expected loss is 400 − 300 = 100 pounds. Answer: Amir should expect to be about £100 down. The distractors: £300 is the expected winnings on their own, with the cost of playing never taken off; £400 is the total cost of playing, with the winnings never taken off; £700 comes from adding the two totals, 400 + 300 = 700, instead of subtracting one from the other.
- (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.
- (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.
- (a) 60 — Method: because the counter goes back each time, every draw is the same experiment, so the expected number of reds is the number of draws multiplied by P(red). Working: there are 8 red counters out of 20, so P(red) = 8 ÷ 20 = 0.4. Over 150 draws the expected number of reds is 150 × 0.4 = 60. Answer: about 60 red counters would be expected. The distractors: 90 uses P(blue) by mistake, 150 × 12 ÷ 20 = 90; 100 comes from writing the probability from the red to blue ratio of 8 to 12, giving 150 × 8 ÷ 12 = 100; 75 comes from treating red and blue as equally likely because there are two colours, which gives 150 ÷ 2 = 75.
- (d) 12/25 — The group holds 40 of the 250 tickets, so for any one prize the probability the group wins it is 40/250 = 4/25. There are 3 prizes and the group has the same chance at each one, so the expected number won is 3 × 4/25 = 12/25. Writing 4/25 is wrong because it is the chance of winning just ONE prize, without multiplying by the 3 prizes available. Writing 4/75 is wrong because it divides by the 3 prizes instead of multiplying (4/25 ÷ 3 = 4/75), which would mean the group did worse the more prizes were on offer. Writing 64/15625 is wrong because it multiplies the single-prize probability by itself three times, (4/25)³, as though all three prizes had to be won together, instead of adding up the expected number across the three separate prizes. The expected number of prizes won by the group is 12/25.
- (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.
- (a) 1276 — Method: an unbiased relative frequency tends towards the theoretical probability as the number of trials increases, so use the record resting on the most trials, then multiply by the number of new trials. Working: the three records rest on 50, 200 and 1000 drops, so the most reliable is the one after 1000 drops, namely 0.638, and the run is indeed settling as the trials increase. The expected number of point up landings in 2000 further drops is 2000 × 0.638 = 1276. Answer: about 1276 times. The distractors: 1440 uses the earliest record, which rests on only 50 drops, giving 2000 × 0.720 = 1440; 1330 uses the middle record, treating 200 drops as a safe compromise when 1000 drops is better still, giving 2000 × 0.665 = 1330; 1348 comes from averaging the three records, since 0.720 + 0.665 + 0.638 = 2.023 and 2.023 ÷ 3 = 0.674, then 2000 × 0.674 = 1348, which gives the 50 drop record the same weight as the 1000 drop record.
- (d) 24 — There are 4 choices for the first digit. Once that digit is used, 3 digits remain for the second position, and then 2 digits remain for the third position: 4 × 3 × 2 = 24 codes. Choosing 64 comes from allowing a digit to be reused at every position, 4 × 4 × 4 = 64, which is not allowed here since no digit repeats. Choosing 12 comes from multiplying only the first two positions, 4 × 3 = 12, and forgetting that a third digit is also chosen from the digits that remain. Choosing 6 comes from counting only the arrangements of one single set of three digits, 3 × 2 × 1 = 6, and forgetting that there are 4 different sets of three digits that can be chosen from 2, 3, 4 and 5.
- (a) 160 — Expected number = probability × number of trials = 0.08 × 2,000 = 160. Moving the decimal point one place too far, using 0.008 instead of 0.08, gives 2,000 × 0.008 = 16. Working out the expected number of customers who do NOT buy a bag, using the complement 1 − 0.08 = 0.92, gives 2,000 × 0.92 = 1,840. Rounding 0.08 up to 0.1 before multiplying gives 2,000 × 0.1 = 200.
- (b) 100 — The sample shows a proportion of 8/60 = 2/15 faulty. Apply that proportion to the new batch of 750: 750 × 2/15 = 100. Flipping the ratio, calculating 8/750 × 60 instead of 8/60 × 750, gives 0.64, which rounds to about 1. Assuming the same number of faulty items applies to the new batch, without scaling for its larger size, just repeats the sample's count of 8. Rounding the proportion 8/60 = 0.1333... down to 0.1 before multiplying gives 750 × 0.1 = 75.
- (c) 9/16 — There are 180 students in total and 84 are in Year 11, so Year 10 has 180 − 84 = 96 students. Of those 96, 42 travel by bus, so 96 − 42 = 54 walk. P(Year 10 student walks) = 54/96 = 9/16. Using the whole school of 180 as the denominator instead of just the 96 Year 10 students gives 54/180 = 3/10. Using the bus count, 42, as if it were the number who walk gives 42/96 = 7/16, the wrong branch of the Year 10 row. Working out the probability for Year 11 instead of Year 10 — 46 walkers out of 84 — gives 46/84 = 23/42.
- (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.
Build your own mix at the worksheet builder.