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) 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.
- (a) 952 — 68% = 0.68. The relative frequency from the survey applies to the new group of 1400 shoppers, so the expected number is 0.68 × 1400 = 952. Working out 1 − 0.68 = 0.32 and applying that instead, 0.32 × 1400 = 448, finds the number who have NOT used a self-checkout, not the number who have. Applying 68% to the original sample size of 250 instead of the new total of 1400 gives 0.68 × 250 = 170. Applying the complement percentage to the original sample size, 0.32 × 250 = 80, compounds both mistakes.
- (b) 60 — The probability of landing on purple in a single spin is 2/6. The expected number of times it lands on purple in 180 spins is 180 × 2/6 = 60. A candidate who answers 90 has used 3/6 instead of 2/6, miscounting the purple sections as 3. A candidate who answers 30 has used 1/6 instead of 2/6, forgetting one of the two purple sections. A candidate who answers 120 has used the probability of NOT landing on purple, 4/6, by mistake.
- (a) 50 — To find the number of shots needed for an expected 12 hits, divide the number of hits wanted by the probability of a hit: 12 ÷ 0.24 = 50. Multiplying the number of hits by the probability instead of dividing gives 12 × 0.24 = 2.88, which rounds to 3 shots. Rounding 0.24 to 0.25 before dividing gives 12 ÷ 0.25 = 48. Using the probability of missing, 1 − 0.24 = 0.76, instead of the probability of hitting, gives 12 ÷ 0.76 = 15.79, which rounds to 16.
- (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.
- (b) 8,100 — First find the total number of alerts sent in the month: 1,500 × 30 = 45,000. Then apply the probability of a 'STOP' reply: 45,000 × 0.18 = 8,100. Stopping after finding only one day's expected replies, 1,500 × 0.18 = 270, forgets to scale up to the whole month. Multiplying the number of days by the probability instead of by the daily total of alerts gives 30 × 0.18 = 5.4, which rounds to 5. Shifting the decimal point in the probability, using 0.018 instead of 0.18, gives 45,000 × 0.018 = 810.
- (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.
- (d) 1/4 — Method: a product is odd only when BOTH factors are odd, so list the ordered pairs where both scores are odd and divide by 36. Working: the odd scores on a dice are 1, 3 and 5, so there are 3 × 3 = 9 ordered pairs where both scores are odd, out of the 36 equally likely pairs, cancelling down to 1/4. Answer: 1/4. Watch out: writing down 3/4 finds the probability that AT LEAST ONE score is odd, 1 minus the probability both are even, which is a different, easier condition to meet than both being odd. Considering only the first dice's score and ignoring the second gives 1/2, since 3 of the first dice's 6 scores are odd — but the product also depends on what the second dice shows. And writing down 1/12 comes from counting only the pairs where the SAME odd number appears twice, (1, 1), (3, 3) and (5, 5), missing pairs like (1, 3) and (5, 1) where the two odd scores differ.
- (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) 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) 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.
- (a) 1200 — Method: take the estimate from the larger sample, because an unbiased relative frequency tends towards the true probability as the sample grows, then multiply by the number of bulbs made in a week. Working: Inspector B tested 500 bulbs, far more than Inspector A's 40, so use B's relative frequency: 30 ÷ 500 = 0.06. A week's production is 4000 × 5 = 20000 bulbs. The expected number of faulty bulbs is 20000 × 0.06 = 1200. Answer: about 1200 faulty bulbs a week. The distractors: 2000 uses Inspector A's estimate, 4 ÷ 40 = 0.1, giving 20000 × 0.1 = 2000, and so rests on a sample of only 40 bulbs; 1600 comes from averaging the two estimates of 0.1 and 0.06 to get 0.08, and 20000 × 0.08 = 1600, which gives the small sample equal weight with the large one; 240 uses the right estimate but stops at a single day, 4000 × 0.06 = 240.
- (a) £124.80 — On the cake branch, 150 − 100 = 50 cakes were bought by children. Adding the 54 biscuits bought by children gives 50 + 54 = 104 items sold to children in total, and at £1.20 each that raises 104 × £1.20 = £124.80. Writing £60.00 is wrong because 50 × £1.20 = £60.00 only counts the cake sales to children and leaves out the 54 biscuits. Writing £163.20 is wrong because it uses the ADULT sales instead of children's: 100 cake adults plus 90 − 54 = 36 biscuit adults gives 136 × £1.20 = £163.20. Writing £136.80 is wrong because it finds the cake children's number by subtracting the wrong branch (150 − 90 = 60 instead of 150 − 100 = 50), giving 60 + 54 = 114 items and 114 × £1.20 = £136.80. The total raised from sales to children is £124.80.
- (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.
- (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.
Build your own mix at the worksheet builder.