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
- (b) 80 — To find the number of attempts needed, divide the target number of successes by the probability of success: 60 ÷ 0.75 = 80. Writing 45 is wrong because 60 × 0.75 = 45 multiplies instead of dividing — that is the number of successes expected from 60 attempts, not the number of attempts needed for 60 successes. Writing 240 is wrong because 60 ÷ 0.25 = 240 uses 0.25, the probability of MISSING, instead of 0.75, the probability of scoring. Writing 90 is wrong because it comes from misremembering 0.75 as 2/3 and dividing by that instead: 60 ÷ (2/3) = 90. She needs to attempt 80 free throws.
- (c) 30 — The numbers less than 4 are 1, 2 and 3, so the probability of that event is 3/6, and the expected count in 90 rolls is 90 × 3/6 = 45. The probability of rolling a 6 is 1/6, and the expected count is 90 × 1/6 = 15. The difference between the two expected counts is 45 − 15 = 30. A candidate who answers 45 has given the expected count for 'less than 4' only, forgetting to subtract the other expected count. A candidate who answers 15 has given the expected count for '6' only. A candidate who answers 36 has used a dice with 5 possible numbers instead of 6, giving 90 × 3/5 = 54 and 90 × 1/5 = 18, a difference of 36.
- (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.
- (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.
- (b) likely — On the probability scale, 'certain' is reserved for a probability of exactly 1, and 'evens' describes a probability of exactly 0.5. A probability of 0.9 is high but not equal to 1, so the correct word is 'likely'. Choosing 'certain' treats a probability close to 1 as if it were exactly 1, which it is not. Choosing 'evens' misjudges 0.9 as being close to the midpoint of the scale, when it is close to the 'certain' end instead. Choosing 'unlikely' reads the scale the wrong way round, as if a high probability meant a low chance of happening.
- (c) 0.37 — Method: pool the two runs into one combined set of results, then find the relative frequency of red across all of the spins together. Working: total reds = 16 + 21 = 37. Total spins = 40 + 60 = 100. Relative frequency = 37 ÷ 100 = 0.37. Answer: 0.37. Watch out: writing down 0.40 uses only the first run, 16 ÷ 40, and throws away the extra evidence from the second 60 spins. Writing down 0.35 uses only the second run, 21 ÷ 60, and throws away the first run instead. And writing down 0.375 averages the two runs' separate rates, (0.40 + 0.35) ÷ 2, which treats a run of 40 spins and a run of 60 spins as equally weighted, when pooling the actual counts gives the larger run its fair share of influence.
- (b) 0.225 — The relative frequency of rain is the number of rainy days out of all days recorded: 9 ÷ 40 = 0.225, which is noticeably less than the forecaster's claimed 0.3. Using the number of dry days, 40 − 9 = 31, as the denominator instead of the total of 40 gives 9 ÷ 31 = 0.29 (2 d.p.). Simply reporting the forecaster's claimed value, 0.3, without calculating anything from the data at all, ignores the recorded results completely. Misplacing the decimal point, treating 9 out of 40 as 9%, gives 0.09 instead of 0.225.
- (c) 325 — Method: first find the relative frequency of NOT landing on red from the 200 spins, then scale that up to 500 spins. Working: non-red results = 50 + 80 = 130, out of 200 spins, so P(not red) = 130 ÷ 200 = 0.65. Expected non-red results in 500 spins = 500 × 0.65 = 325. Answer: 325. Watch out: writing down 175 finds the expected number of RED results instead, 70 ÷ 200 × 500 = 175, answering the opposite of what was asked. Writing down 250 assumes landing red or not landing red must be a fair 50-50 split, but the spinner is biased and the actual results do not split evenly. And writing down 130 stops after finding how many of the 200 spins were non-red and forgets to scale that figure up to the 500 spins asked for.
- (d) 3/16 — Method: work out each draw's own probability first, then multiply them together since the two draws are independent. Working: there are 8 tickets in all, 3 of them blue, so P(blue) = 3/8. P(spinner number greater than 2) = 2/4 = 1/2, since 3 and 4 qualify. Multiplying gives 3/8 × 1/2, which comes to 3/16. Answer: 3/16. Watch out: writing down 3/8 stops after the first draw and never brings in the spinner at all. Writing down 1/2 does the opposite, using only the spinner and ignoring the ticket draw. And writing down 5/16 uses 5/8, the probability of a RED ticket, instead of 3/8 for blue — reading the wrong colour off the raffle.
- (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.
- (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.
- (b) 70 — Saloon, estate and hatchback are exhaustive, so their probabilities sum to 1: the probability of a hatchback is 1 − 0.28 − 0.37 = 0.35. The number of hatchbacks is 0.35 × 200 = 70. Treating the SUM of the other two probabilities, 0.28 + 0.37 = 0.65, as the probability of a hatchback instead of its complement gives 0.65 × 200 = 130. Multiplying the correct probability, 0.35, by 100 instead of the 200 cars actually surveyed gives 35. Averaging the two given probabilities, (0.28 + 0.37) ÷ 2 = 0.325, instead of subtracting them from 1, and then multiplying by 200 gives 65.
- (b) 22.8% — Relative frequency as a percentage is the faulty count divided by the total, then multiplied by 100: 33 ÷ 145 × 100 = 22.76, which rounds to 22.8%. Giving 33.0% as the answer uses the frequency, 33, directly as a percentage without dividing by the total 145 at all. Rounding 22.76 down to 22.7% instead of up applies the wrong rounding direction at the first decimal place. Finding the relative frequency of the bulbs that were NOT faulty first: 145 − 33 = 112, and 112 ÷ 145 × 100 = 77.24, answers the opposite question and rounds to 77.2%.
- (c) 170 — 68% of the 250 packets germinated: 250 × 0.68 = 170. Using the complement, the 32% that did NOT germinate, gives 250 × 0.32 = 80. Shifting the decimal point, using 0.068 instead of 0.68, gives 250 × 0.068 = 17. Rounding 68% up to 70% before multiplying gives 250 × 0.70 = 175.
- (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.
Build your own mix at the worksheet builder.