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
- (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.
- (b) 0.55 — Method: it is easier to find the probability that Ffion wins NEITHER stage, then subtract that from 1. Working: P(lose stage 1) = 1 − 0.4 = 0.6, and P(lose stage 2) = 1 − 0.25 = 0.75. P(neither) = 0.6 × 0.75 = 0.45. P(at least one) = 1 − 0.45 = 0.55. Answer: 0.55. Watch out: adding the two win probabilities, 0.4 + 0.25 = 0.65, treats winning both as impossible and overcounts — that is not how independent probabilities combine. Multiplying the two win probabilities, 0.4 × 0.25 = 0.1, gives the probability of winning BOTH stages, not at least one. And stopping at 0.45, the probability of winning neither stage, forgets the final step of subtracting from 1.
- (c) Red — Theoretical probability is 1/3 ≈ 0.333 for each colour. Red's relative frequency is 38/90 ≈ 0.422, above 1/3, so red is over-represented. Blue's relative frequency is 26/90 ≈ 0.289, below 1/3, so blue is under-represented, not over. Green's relative frequency is also 26/90 ≈ 0.289, below 1/3 for the same reason. Since red's relative frequency clearly exceeds 1/3, it is not true that none of the colours are over-represented.
- (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) 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.
- (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.
- (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) 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.
- (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.
- (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.
- (c) 120 — 27 of the 45 sweets are orange (45 − 18 = 27), so the probability of taking an orange sweet is 27/45 = 3/5, and 200 × 3/5 = 120. Writing 80 is wrong because 200 × 18/45 = 80 uses the LEMON sweets' fraction instead of orange. Writing 182 is wrong because it takes the 18 lemon sweets away from the 200 repeats (200 − 18 = 182), applying the ‘the rest are orange’ subtraction to the number of goes instead of to the 45 sweets in the bag. Writing 27 is wrong because it is simply the number of orange sweets in the bag — it has not been scaled up to account for the 200 repeats. The expected number of times an orange sweet is taken is 120.
- (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.
- (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) 3,860 — The probability a bulb works correctly is the complement of being defective: 1 − 0.035 = 0.965. Expected number working correctly = 0.965 × 4,000 = 3,860. Using the probability of being defective instead of its complement gives 4,000 × 0.035 = 140, the expected number of DEFECTIVE bulbs, not working ones. Shifting the decimal point in the complement, using 0.0965 instead of 0.965, gives 4,000 × 0.0965 = 386. Assuming every bulb works, ignoring the 0.035 probability altogether, gives the full batch of 4,000.
- (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.
Build your own mix at the worksheet builder.