📝 How to round whole numbers (27 MCQs)

📖 Explanation: Exact total = 4,823 + 6,197 + 3,456 = 14,476. Round each first: 5,000 + 6,000 + 3,000 = 14,000 (error = 476). Add then round: 14,476 → 14,000 (error = 476). Wait calculation: 4,823→5,000; 6,197→6,000; 3,456→3,000; sum=14,000. Add first=14,476→14,000 (to nearest thousand). Errors are equal (476). But option says difference=100? Let's recalc: 5,000+6,000+3,000=14,000. 14,476 rounds to 14,000. Difference = 0. So correct is B. Explanation: Both yield 14,000 so difference zero. This highlights that rounding order doesn't always change the result, but can in other cases.

📖 Explanation: Rounding to nearest hundred thousand: 1,234,567 → 1,200,000; 1,456,789 → 1,500,000. Estimated growth = 300,000. Exact growth = 222,222. Error = 77,778 (~35% error). For growth estimates, relative error matters. Rounding to nearest ten thousand would give 1,230,000 and 1,460,000 → growth 230,000 (error ~3.5%). So the method is poor for growth because both numbers round in opposite directions (down and up), magnifying error. Correct is B.

📖 Explanation: Rounding to nearest thousand: look at hundreds digit (7). Since 7 ≥ 5, round up to 5,000. First student is correct. Second student confused thousand with hundred place. So error is place value misconception. D is correct.

📖 Explanation: Nearest ten thousand: 54,321→50,000; 49,876→50,000; sum=100,000. Nearest thousand: 54,321→54,000; 49,876→50,000; sum=104,000. Difference = 4,000. Exact total = 104,197. Analyst's estimate (104,000) is closer. Manager's rounding lost detail because both rounded to same ten-thousand. So A is correct.

📖 Explanation: Rounded: A→30, B→30, C→40, D→40; sum=140. Exact=28+34+41+37=140. Individual errors: +2, -4, -1, +3 sum to 0. So estimate is exact but errors cancel. This demonstrates that rounding errors can offset. B is correct.

📖 Explanation: One-step: 6,482 → look at hundreds (4) → 6,000. Two-step: 6,482→6,500 (nearest hundred), then 6,500→7,000 (nearest thousand). This yields 7,000, which is farther (error 518 vs 482). So two-step rounding is invalid and less accurate. The error is in sequential rounding. B is correct.

📖 Explanation: Exact total = 12,483+9,765=22,248. Organizer: 12,000+10,000=22,000 (short). Volunteer: total 22,248 rounds to 22,000 (short). Wait both give 22,000. But option C says volunteer says met? Let's recalc: 22,248 rounds to 22,000 (nearest thousand) not 25,000. Actually none says met. But the goal is 25,000; both estimates are 22,000, short. So correct should be A or B. However the question is designed to test that rounding total vs rounding parts can give different results when crossing a threshold. Let's adjust numbers: Suppose Week1=12,600, Week2=12,400, goal=25,000. Round each: 13,000+12,000=25,000 (met). Total=25,000 exactly. Not good. Let's use original: 12,483+9,765=22,248. Both round to 22,000. So same. To make different, need e.g., 12,600+12,500=25,100 exact, round each=13,000+13,000=26,000, total rounds=25,000. Then organizer says met, volunteer says met? Actually both met. The challenge is to find a case where rounding each says short but rounding total says met. Example: 12,600 and 12,400 → exact 25,000, each rounds to 13,000+12,000=25,000 met. Try 12,600+12,300=24,900 → each round 13,000+12,000=25,000 met, total rounds to 25,000 met. To get short by parts but met by total: need each rounds down but total rounds up. E.g., 11,600+13,400=25,000 exact, each rounds to 12,000+13,000=25,000. Not. Let's set: Week1=11,499 (rounds to 11,000), Week2=13,501 (rounds to 14,000) sum=25,000 exact, parts=25,000. Not. To get parts short: 11,400+13,400=24,800, parts=11,000+13,000=24,000 short, total=25,000 (since 24,800 rounds to 25,000). So organizer says short (24,000<25,000), volunteer says met (25,000). So correct C. But with given numbers 12,483+9,765=22,248 → both short. So I'll change the numbers in the question to 11,483 and 13,765? Actually let's keep the question but fix numbers: Week1=11,483, Week2=13,765 → total=25,248. Rounded each: 11,000+14,000=25,000 met. Total rounds to 25,000 met. Both met. To get different: Week1=11,483 (→11,000), Week2=13,765 (→14,000) sum parts=25,000 met. No. Let's do Week1=11,483 (→11,000), Week2=13,765 (→14,000) total=25,248→25,000. Both met. Need parts short: Week1=11,400 (→11,000), Week2=13,400 (→13,000) sum parts=24,000 short, total=24,800→25,000 met. So I'll edit question text to use 11,400 and 13,400. But I must keep the CSV format. I'll rewrite the question with new numbers.

📖 Explanation: Exact total = 11,483+13,765=25,248. Organizer rounds each: 11,000+14,000=25,000 → met. Volunteer rounds total: 25,248 → 25,000 → met. Wait that gives both met. I need numbers that give parts short but total met. Let's use 11,483 and 13,765 gave both met. To get parts short: need each round down and sum <25,000. Example: 11,400→11,000; 13,400→13,000; sum=24,000 short. Exact total=24,800→25,000 met. So I'll use 11,400 and 13,400. Then organizer: 11,000+13,000=24,000 (short), volunteer: 24,800→25,000 (met). So C is correct. This illustrates that rounding individual components can lead to different decisions than rounding the final total, especially near thresholds.

📖 Explanation: Student B's method (add first then round) is mathematically sound for estimating the final total; $22,203 rounds to$22,000. Student A's method is flawed because rounding each number before adding introduces a larger error; here it gives a misleading exact match. Option C is false because rounding is not commutative with addition in terms of exact rounded results. Option D ignores the estimation context. Thus B is the correct reasoning.

📖 Explanation: The student is correct because rounding to the nearest hundred thousand: for 7,893,542, the ten-thousands digit is 9 (>=5), so round up to 7,900,000. For 8,104,299, the ten-thousands digit is 0 (<5), so round down to 8,100,000. Difference = 8,100,000 - 7,900,000 = 200,000. This tests the concept of rounding place value and applying it to difference estimation. Options B, C, D are variations that either restate or misinterpret, but A correctly validates the student.

📖 Explanation: 3,784 rounds to 4,000 (since 784 >= 500), 2,916 rounds to 3,000 (916 >= 500). Estimated total = 7,000. Exact sum = 6,700, which rounds to 7,000 (since 700 >= 500). The error is the absolute difference between the estimated total (7,000) and the exact sum (6,700) = 300. Option A incorrectly says error 0, C incorrectly calculates error, D uses wrong rounding for 3,784. Thus B is correct.

📖 Explanation: Interpreting bar graph data and applying rounding to nearest hundred: 2,345→2,300, 3,210→3,200, 1,876→1,900, 4,502→4,500. Sum = 11,900, which lies in the range 11,500–12,000. This question requires reading graph values, rounding each, then summing and estimating range, testing multi-step reasoning and graph interpretation.

📖 Explanation: 94,725 rounded to nearest ten thousand: look at thousand digit 4 (since 94,725 → ten-thousands place is 9, next digit 4 <5, so round down to 90,000). 90,000 ÷ 15,000 = 6 truckloads (estimate). Actual: 94,725 ÷ 15,000 = 6.315, so they need 7 full truckloads because you can't have a fraction of a truckload (ceil). Option A is correct. B says estimate 7 but 90,000/15,000=6, not 7. C says actual 6 which is insufficient. D says estimate 7 wrong. So A.

📖 Explanation: First student is correct: to round to nearest thousand, look at the hundreds digit (6). Since 6 >= 5, round up the thousands digit from 5 to 6, making 6,000. The second student incorrectly thinks it's closer to 5,000, but 5,678 is 678 away from 6,000 and 678 away from 5,000? Actually distance to 6,000 is 322, to 5,000 is 678, so closer to 6,000. Option C correctly identifies the second student's confusion, but A is the direct correct answer. Option D is nonsense. So correct is A.

📖 Explanation: To round to 350,000, the number must lie in [345,000, 354,999]. Check each: A) 345,678 sum=33, not 20. B) 354,321 sum=18 and odd, fails both. C) 348,320 sum=3+4+8+3+2+0=20, even, and rounds to 350,000 (since 8 in thousands? Actually to nearest ten thousand, look at thousand digit: 8 >=5, so 348,000 rounds to 350,000? Wait 348,320: ten-thousands digit is 4, next digit (thousands) is 8, so round up to 350,000. Correct. D) 352,010 sum=11, not 20. So C is the only one satisfying all conditions. This tests multiple constraints and place-value rounding.

📖 Explanation: The student's reasoning is flawed because they misunderstand the level of precision. Rounding to the nearest tenth of a million means the target is 8.4 million or 8.5 million; since 8,421,937 is 21,937 away from 8.4 million and 78,063 away from 8.5 million, 8.4 million is the correct rounded value. The purpose is to simplify data for communication, not to preserve exact accuracy. Thus option B is correct.

📖 Explanation: The purpose of rounding depends on the context. For a pie chart, simplicity is key, so 65% is acceptable, but for trend analysis, 65.4% retains more precision and is better. Option B correctly distinguishes these purposes, showing rounding is a tool, not a rule. The second researcher’s argument is valid because preserving a decimal aids comparison, while the first researcher’s choice is not 'wrong' but serves a different purpose. Thus B is the most balanced and correct.

📖 Explanation: The student’s error is applying rounding at the wrong stage and expecting an exact match. Rounding’s purpose is estimation or simplification, not precision. Her estimated total of $35 is a reasonable quick estimate for budgeting, differing by only 7 cents. Option B identifies the misuse and correctly states that rounding is for approximation, not exact billing. Options A and D misunderstand rounding as useless, while C is impractical because rounding$4.99 to $4.99 is not rounding.

📖 Explanation: The purpose of rounding to significant figures is to communicate measurement precision, not to maximize closeness to the original. One significant figure means only the most significant digit (the tens place, 1 in 12.345) is kept, and the next digit (2) is less than 5, so it rounds down to 10 (represented as $1 \times 10^1$ cm). The colleague’s 12.3 cm has three significant figures, violating the guideline. Thus B is correct; A and C misinterpret significant figures, and D ignores the guideline.

📖 Explanation: The purpose of rounding is context-dependent. For a population graph, an upper bound (3,000) simplifies scale, while a budget benefits from a more precise estimate (2,500) to avoid underestimation. Option C correctly identifies that both are valid rounding choices (to different place values) and that the context determines the purpose. Option A and D are too rigid, and B incorrectly assigns 'nearest hundred' to budget when it’s actually to the nearest hundred, but the explanation of purpose is less precise than C.

📖 Explanation: In a digital display with limited pixels, the purpose of rounding is to reduce data complexity so that it can be rendered clearly. The step function, while less precise, serves this practical purpose. Option B correctly evaluates that the loss of precision is acceptable for the display’s constraints, making the student’s claim too absolute. A is incorrect because it ignores context; C imposes an unnecessary rule; D is false because rounding changes representation.

📖 Explanation: In multi-step calculations, the standard practice is to round only the final answer to avoid cumulative rounding errors that can compound. Rounding intermediate factors (3.14 and 2.72) introduces error early, which may lead to a less accurate final value, though here coincidentally it matches. The primary purpose is to maintain accuracy until the end. Option B correctly identifies the student’s method as superior and explains the purpose. A is wrong because early rounding increases error; C ignores the principle; D is false.

📖 Explanation: Both students are actually correct. Rounding to the nearest tenth: look at hundredths digit (6) which is >=5, so tenths digit (8) becomes 9, giving 3.9. Rounding to nearest hundredth: look at thousandths digit (5), so hundredths digit (6) becomes 7, giving 3.87. The misconception is thinking one must be wrong, but different place values yield different rounded forms. This tests understanding that rounding is place-value dependent and multiple correct answers exist for the same number at different precision levels.

📖 Explanation: When rounding to nearest hundred, 12,847 becomes 12,800 (since tens digit 4<5) with absolute error |12,847-12,800|=47. Rounding to nearest thousand gives 13,000 (hundreds digit 8>=5) with error 153. The hundred-rounded value is closer to the true number, thus more accurate, but less suitable for a quick headline. This requires comparing precision vs. practicality and calculating error, not just mechanical rounding.

📖 Explanation: 4.9996 rounded to nearest whole: ones digit 4, tenths 9>=5 -> 5. To nearest tenth: tenths digit 9, hundredths 9>=5 -> tenths becomes 10, carry over -> 5.0. To nearest hundredth: hundredths digit 9, thousandths 9>=5 -> hundredths becomes 10, carry -> 5.00. All yield the same numerical value 5, though with different decimal places. The misconception is thinking 5.0 and 5 are different; they are equal. This tests understanding that trailing zeros don't change value but indicate precision, yet numerically all are 5.

📖 Explanation: To round to nearest ten, look at the ones digit (which is 7 in 247.6, since decimal part doesn't affect the ones place for rounding to tens). The tens digit is 4. Since 7 >=5, we round the tens digit up from 4 to 5, making it 250. The decimal .6 is irrelevant for tens rounding because we only consider the digit immediately to the right of the target place (ones). This multi-step reasoning requires identifying the correct place value and not being misled by the decimal.

📖 Explanation: For a number to round to 3.5 to the nearest tenth, the tenths digit after rounding must be 5. The original number must be in the interval [3.45, 3.55) because the lower bound 3.45 has hundredths digit 5, which rounds up to 3.5 (since 5 rounds up). The upper bound 3.55 would round to 3.6 because hundredths digit 5 makes tenths 5 become 6 (since 5 rounds up). So 3.55 is excluded. This tests the interval concept and the boundary behavior of 5, which is a common misconception area.