Skip to main content
Sign in Create a free account
Varsity Tutors
Sign in

Choosing Appropriate Levels of Accuracy - Algebra 1

  1. A student measured a room length with a tape measure marked only in whole centimeters and wrote: "The room is 425.37 cm long." Why is this reporting inappropriate?
    Answer: It claims more decimal precision than the tape measure can provide. This question tests your understanding that the precision of your reported answer should match the precision of your measurements—you can't claim accuracy beyond what your measurement tools or methods allow. False precision is reporting too many digits: saying 'we need 3.7142857 people for the job' is silly—you can't have fractional people! Or 'the stick is 12.384729 cm' when you measured with a ruler marked in cm (so really 12 cm or maybe 12.4 cm at most). Excessive decimals don't make you look more accurate; they show you don't understand measurement limitations. Round appropriately! The statement 'The room is 425.37 cm long' shows false precision: the tape measure is marked only in whole centimeters, so measurements are to the nearest cm, not decimals. With tool precision to whole cm, we can only reliably report to nearest cm. The extra digits .37 are unjustified—they suggest accuracy beyond what the measurement method actually provides. Appropriate reporting: 425 cm. Choice B correctly identifies claiming more decimal precision than the tape measure can provide which appropriately reflects measurement capability. Choice C ignores the sig fig rule: with inputs having various sig figs, but here it's about tool precision, not arbitrary rounding to 10 cm. Sig figs rules prevent false precision in calculations—follow them! False precision red flags: (1) More decimals than your measuring tool can detect, (2) Fractional counts of discrete things, (3) More sig figs than any input had, (4) Excessive precision for the context (measuring a room 'exactly 12.0000000 feet'). If you see these in your work or others', recognize it as inappropriate precision. Better to round sensibly than claim unjustified accuracy!
  2. A student uses a ruler marked only in whole centimeters to measure a pencil and records the length as 14 cm (to the nearest 1 cm). Which reporting shows appropriate precision for this measurement?
    Answer: 14 cm This question tests your understanding that the precision of your reported answer should match the precision of your measurements—you can't claim accuracy beyond what your measurement tools or methods allow. The fundamental principle: you cannot report a calculated or measured value more precisely than your least precise measurement. If you measure length to the nearest centimeter (like 24 cm), you can't honestly report area to the nearest millimeter (like 576.00 cm²)—your measurement tool wasn't that precise! Calculations don't magically create precision; they can only preserve (or lose) the precision from your inputs. Reporting excessive decimal places is false precision—claiming accuracy you don't actually have. Given measurement of 14 cm (to nearest 1 cm) with a ruler marked in whole cm, we report as 14 cm, without decimals. The measurement has precision to whole numbers, so we report to wholes. Reporting as 14.0 cm would be false precision—suggesting tenths precision the ruler doesn't provide. This reflects our actual measurement capability, not false precision. Choice C correctly reports to wholes which appropriately reflects measurement capability. Choice A shows false precision: reporting to tenths when measurement only justifies precision to wholes. Example: if you measure with a tool accurate to 0.1 cm, reporting 5.3874 cm claims you can distinguish thousandths of a centimeter—but you can't with that tool! Report 5.4 cm instead, matching your measurement capability. False precision red flags: (1) More decimals than your measuring tool can detect, (2) Fractional counts of discrete things, (3) More sig figs than any input had, (4) Excessive precision for the context (measuring a room 'exactly 12.0000000 feet'). If you see these in your work or others', recognize it as inappropriate precision. Better to round sensibly than claim unjustified accuracy! Trailing zeros matter: 3.5 vs 3.50 vs 3.500 represent different claimed precision (tenths vs hundredths vs thousandths). Only include trailing zeros after the decimal if your measurement actually supports that precision! If measured to hundredths, write 3.50 (showing you measured hundredths). If measured to tenths, write 3.5 (don't add fake zeros). Trailing zeros after decimal are significant—they're precision claims!
  3. Two lengths are measured as 3.2 m and 8.75 m. You multiply them to find an area: 3.2×8.75=28.03.2\times 8.75=28.0 (from the calculator). How should the product be reported given the measurement precision?
    Answer: 28 m2^2 This question tests your understanding that the precision of your reported answer should match the precision of your measurements—you can't claim accuracy beyond what your measurement tools or methods allow. Significant figures tell you how precise a measurement is: 3.2 has 2 sig figs (precise to tenths), while 3.20 has 3 sig figs (precise to hundredths). When you multiply or divide measurements, the result should have the same number of sig figs as your least precise input. Example: 3.2 m × 7.856 m = 25.1392 m² → report as 25 m² (2 sig figs from 3.2). This prevents claiming the product is more accurate than the measurements that went into it! Calculating area with 3.2 m (2 sig figs) and 8.75 m (3 sig figs): 3.2 × 8.75 = 28.0 m². For multiplication/division, the result should have sig figs matching the least precise input, which is 2 sig figs from 3.2. Counting sig figs in 28.0: that's 3 sig figs, but we need only 2. Rounding to 2 sig figs: 28 m². This maintains precision consistency—we're not claiming our product is more accurate than our inputs! Choice A correctly uses 2 significant figures (28 m²) which appropriately reflects the least precise input (3.2 m with 2 sig figs). Choice B shows false precision: reporting to 28.0 m² when 3.2 m only justifies 2 sig figs in the result. While the calculator shows 28.0, that trailing zero after the decimal claims precision we don't have. Sig fig rules prevent false precision in calculations—follow them! Significant figures quick guide for calculations: Multiplication/division → result has sig figs of least precise input (3.2 × 8.467 → 27, two sig figs). These rules prevent false precision. Remember: sig figs represent measurement reliability, not arbitrary rounding! Your calculator will show many digits, but you must round to match the precision of your least precise measurement—that's the bottleneck for accuracy.
  4. Two measurements are multiplied to estimate the area of a small table: 2.5 ft (measured to the nearest 0.1 ft) and 3.14 ft (measured to the nearest 0.01 ft). Measurements were made to those precisions. Report the product with appropriate precision.
    Answer: 7.9 ft² This question tests your understanding that the precision of your reported answer should match the precision of your measurements—you can't claim accuracy beyond what your measurement tools or methods allow. Significant figures tell you how precise a measurement is: 3.2 has 2 sig figs (precise to tenths), while 3.20 has 3 sig figs (precise to hundredths). When you multiply or divide measurements, the result should have the same number of sig figs as your least precise input. Example: 3.2 m × 7.856 m = 25.1392 m² → report as 25 m² (2 sig figs from 3.2). This prevents claiming the product is more accurate than the measurements that went into it! Calculating area with 2.5 ft (2 sig figs) and 3.14 ft (3 sig figs): 2.5 × 3.14 = 7.85 ft². For multiplication, the result should have sig figs matching the least precise input, which is 2 sig figs from 2.5. Counting sig figs in result: 7.9 has 2 sig figs (rounding 7.85 up). This maintains precision consistency—we're not claiming our product is more accurate than our inputs! Choice C correctly uses 2 significant figures which appropriately reflects input precision. Choice A shows false precision: reporting to thousandths when measurements only justify precision to tenths at best. Example: if you measure with a tool accurate to 0.1 cm, reporting 5.3874 cm claims you can distinguish thousandths of a centimeter—but you can't with that tool! Report 5.4 cm instead, matching your measurement capability. Significant figures quick guide for calculations: Multiplication/division → result has sig figs of least precise input (3.2 × 8.467 → 27, two sig figs). Addition/subtraction → result has decimal places of least precise input (3.2 + 8.467 → 11.7, tenths place). These rules prevent false precision. Remember: sig figs represent measurement reliability, not arbitrary rounding! The precision decision framework: (1) What's the precision of your measurements? (limited by tools), (2) What's the context? (money → cents, counts → integers, scientific → sig figs), (3) What precision does the calculation support? (can't exceed inputs), (4) What precision is practical/useful? (blueprint vs estimate). Answer all four, and you'll know how to round! When in doubt, match the precision of your inputs—you can't calculate yourself to higher precision than you measured.
  5. A store sign lists a product weight as 1.50 lb. The scale used in the store reads to the nearest 0.1 lb. Identify the false precision in the statement.
    Answer: The 1.50 suggests precision to the nearest 0.01 lb, which the scale cannot measure This question tests your understanding that the precision of your reported answer should match the precision of your measurements—you can't claim accuracy beyond what your measurement tools or methods allow. False precision is reporting too many digits: saying 'we need 3.7142857 people for the job' is silly—you can't have fractional people! Or 'the stick is 12.384729 cm' when you measured with a ruler marked in cm (so really 12 cm or maybe 12.4 cm at most). Excessive decimals don't make you look more accurate; they show you don't understand measurement limitations. Round appropriately! The statement '1.50 lb' shows false precision: the scale measures to nearest 0.1 lb, so reporting to hundredths suggests finer precision. With measurement to tenths, we can only reliably report to tenths. The extra zero is unjustified—it suggests accuracy beyond what the measurement method actually provides. Appropriate reporting: 1.5 lb. Choice B correctly identifies that the 1.50 suggests precision to the nearest 0.01 lb, which the scale cannot measure which appropriately reflects measurement capability. Choice C over-rounds, losing precision unnecessarily: the measurements justify reporting to tenths, but this choice suggests something incorrect. While not as bad as false precision, unnecessary rounding loses information. If your measurements support tenths, report to tenths; don't round to ones unless needed! False precision red flags: (1) More decimals than your measuring tool can detect, (2) Fractional counts of discrete things, (3) More sig figs than any input had, (4) Excessive precision for the context (measuring a room 'exactly 12.0000000 feet'). If you see these in your work or others', recognize it as inappropriate precision. Better to round sensibly than claim unjustified accuracy! Trailing zeros matter: 3.5 vs 3.50 vs 3.500 represent different claimed precision (tenths vs hundredths vs thousandths). Only include trailing zeros after the decimal if your measurement actually supports that precision! If measured to hundredths, write 3.50 (showing you measured hundredths). If measured to tenths, write 3.5 (don't add fake zeros). Trailing zeros after decimal are significant—they're precision claims!
  6. A survey estimates the number of students who will attend a school event using a model and gets 47.3. Attendance is a count of people. What should be reported as the predicted attendance with appropriate precision?​
    Answer: 47 students This question tests your understanding that the precision of your reported answer should match the precision of your measurements—you can't claim accuracy beyond what your measurement tools or methods allow. Context determines appropriate precision: reporting money? Use cents ($47.23). Counting people? Use whole numbers (47 people, not 47.3!). Measuring with a ruler marked in mm? Report to nearest mm. Scientific measurement? Use significant figures from your instruments. The situation tells you what level of precision makes sense—follow the natural precision of the context! In the context of counting students for attendance, the value 47.3 students should be reported as 47 students because you can't have 0.3 of a person attending an event. Reporting as 47.3 students would be false precision—people come in whole units only! Context determines meaningful precision level! Choice B correctly reports a whole number (47 students) which appropriately reflects that attendance is a count of discrete people. Choice A reports a fractional value for a discrete count: '47.3 students' doesn't make sense—you can't have part of a student! Discrete quantities must be whole numbers. Round to nearest integer: 47 students. Context matters: some quantities (like length, time) can be fractional, but counts cannot! Common sense check: does your reported precision make sense? '3.7 people' → no, round to 4. '$24.983561' for grocery bill → no, round to $24.98. '0.00000001 seconds' from stopwatch showing tenths → no, you can't measure that precisely! If your answer looks ridiculous with too many decimals (or a decimal where shouldn't be one), it probably is. Use judgment based on context!
  7. A recipe scale measures flour to the nearest 1 g. You weigh flour and the display shows 253 g. Why is reporting the mass as 253.0 g inappropriate?
    Answer: Because the scale cannot justify the extra decimal place; it suggests precision to 0.1 g This question tests your understanding that the precision of your reported answer should match the precision of your measurements—you can't claim accuracy beyond what your measurement tools or methods allow. False precision is reporting too many digits: saying 'we need 3.7142857 people for the job' is silly—you can't have fractional people! Or 'the stick is 12.384729 cm' when you measured with a ruler marked in cm (so really 12 cm or maybe 12.4 cm at most). Excessive decimals don't make you look more accurate; they show you don't understand measurement limitations. Round appropriately! The statement '253.0 g' shows false precision: the scale measures to nearest 1 g, so adding .0 suggests tenths precision. With measurement to wholes, we can only reliably report to wholes. The extra digit 0 is unjustified—it suggests accuracy beyond what the measurement method actually provides. Appropriate reporting: 253 g. Choice B correctly identifies that the scale cannot justify the extra decimal place; it suggests precision to 0.1 g which appropriately reflects measurement capability. Choice A ignores the sig fig rule: with inputs having certain precision, the report should match. This choice suggests something incorrect about accuracy. Sig fig rules prevent false precision in calculations—follow them! False precision red flags: (1) More decimals than your measuring tool can detect, (2) Fractional counts of discrete things, (3) More sig figs than any input had, (4) Excessive precision for the context (measuring a room 'exactly 12.0000000 feet'). If you see these in your work or others', recognize it as inappropriate precision. Better to round sensibly than claim unjustified accuracy! Trailing zeros matter: 3.5 vs 3.50 vs 3.500 represent different claimed precision (tenths vs hundredths vs thousandths). Only include trailing zeros after the decimal if your measurement actually supports that precision! If measured to hundredths, write 3.50 (showing you measured hundredths). If measured to tenths, write 3.5 (don't add fake zeros). Trailing zeros after decimal are significant—they're precision claims!
  8. You estimate attendance at a school event by counting rows and averaging: 1111 rows with about 2424 people each gives 11×24=26411\times 24=264. What precision is appropriate when reporting the number of people?
    Answer: 264 people This question tests your understanding that the precision of your reported answer should match the precision of your measurements—you can't claim accuracy beyond what your measurement tools or methods allow. Context determines appropriate precision: reporting money? Use cents ($47.23). Counting people? Use whole numbers (47 people, not 47.3!). Measuring with a ruler marked in mm? Report to nearest mm. Scientific measurement? Use significant figures from your instruments. The situation tells you what level of precision makes sense—follow the natural precision of the context! In the context of counting people at an event, the value 264 should be reported as 264 people because you cannot have fractional people—counts must be whole numbers. Reporting as 264.0 people would be false precision—you can't have 0.5 or 0.7 of a person attending! Context determines meaningful precision level! Choice C correctly reports a whole number (264 people) which appropriately reflects that we're counting discrete objects (people) that cannot be fractional. Choice A reports a fractional value for a discrete count: '264.0 people' doesn't make sense—you can't have part of a person! Discrete quantities must be whole numbers. Round to nearest integer: 264 people. Context matters: some quantities (like length, time) can be fractional, but counts cannot! Common sense check: does your reported precision make sense? '264.5 people' → no, round to 264 or 265. If your answer looks ridiculous with a decimal where there shouldn't be one, it probably is. Use judgment based on context! When counting discrete objects like people, cars, or books, always report whole numbers—decimals are meaningless and show you don't understand what you're measuring.
  9. A class estimates the number of chairs needed for an event using a formula and gets 47.3. Since chairs are a whole-number count, what precision is appropriate when reporting the number of chairs to set out?
    Answer: 48 chairs This question tests your understanding that the precision of your reported answer should match the precision of your measurements—you can't claim accuracy beyond what your measurement tools or methods allow. Context determines appropriate precision: reporting money? Use cents ($47.23). Counting people? Use whole numbers (47 people, not 47.3!). Measuring with a ruler marked in mm? Report to nearest mm. Scientific measurement? Use significant figures from your instruments. The situation tells you what level of precision makes sense—follow the natural precision of the context! In the context of counting chairs, the value 47.3 should be reported as 48 chairs because counts must be whole numbers and to have enough, round up. Reporting as 47.3 chairs would be false precision—can't have 0.3 chair. Context determines meaningful precision level! Choice D correctly rounds to the next whole number which appropriately reflects context requirements. Choice A reports a fractional value for a discrete count: '47.3 chairs' doesn't make sense—you can't have part of a chair! Discrete quantities must be whole numbers. Round to nearest integer: but since needed is 47.3, round up to 48 chairs. Context matters: some quantities (like length, time) can be fractional, but counts cannot! Common sense check: does your reported precision make sense? '3.7 people' → no, round to 4. '$24.983561' for grocery bill → no, round to $24.98. '0.00000001 seconds' from stopwatch showing tenths → no, you can't measure that precisely! If your answer looks ridiculous with too many decimals (or a decimal where shouldn't be one), it probably is. Use judgment based on context! The precision decision framework: (1) What's the precision of your measurements? (limited by tools), (2) What's the context? (money → cents, counts → integers, scientific → sig figs), (3) What precision does the calculation support? (can't exceed inputs), (4) What precision is practical/useful? (blueprint vs estimate). Answer all four, and you'll know how to round! When in doubt, match the precision of your inputs—you can't calculate yourself to higher precision than you measured.
  10. A stopwatch displays time to the nearest 0.1 s. You record a runner's time as 12.7 s. Which reporting shows appropriate precision for this measurement?
    Answer: 12.7 s This question tests your understanding that the precision of your reported answer should match the precision of your measurements—you can't claim accuracy beyond what your measurement tools or methods allow. The fundamental principle: you cannot report a calculated or measured value more precisely than your least precise measurement. If you measure length to the nearest centimeter (like 24 cm), you can't honestly report area to the nearest millimeter (like 576.00 cm²)—your measurement tool wasn't that precise! Calculations don't magically create precision; they can only preserve (or lose) the precision from your inputs. Reporting excessive decimal places is false precision—claiming accuracy you don't actually have. In the context of a stopwatch displaying to the nearest 0.1 s, the value 12.7 s should be reported as 12.7 s because the stopwatch precision is to tenths of a second. Reporting as 12.700 s would be false precision—the stopwatch can't distinguish between 12.700 s and 12.749 s. Context determines meaningful precision level! Choice C correctly reports to tenths of a second (12.7 s) which appropriately reflects the stopwatch's measurement capability of displaying to nearest 0.1 s. Choice A shows false precision: reporting to 12.700 s when the stopwatch only justifies precision to tenths. Example: if you measure with a tool accurate to 0.1 s, reporting 12.700 s claims you can distinguish thousandths of a second—but you can't with that stopwatch! Report 12.7 s instead, matching your measurement capability. Trailing zeros matter: 12.7 vs 12.70 vs 12.700 represent different claimed precision (tenths vs hundredths vs thousandths). Only include trailing zeros after the decimal if your measurement actually supports that precision! If measured to tenths, write 12.7 (don't add fake zeros). Trailing zeros after decimal are significant—they're precision claims! The precision of your measuring instrument determines how you should report your measurement—a stopwatch showing tenths means you report to tenths, not more, not less.
  11. A bathroom scale measures to the nearest 0.1 lb. It reads 156.4 lb. Which reporting shows appropriate precision?
    Answer: 156.4 lb This question tests your understanding that the precision of your reported answer should match the precision of your measurements—you can't claim accuracy beyond what your measurement tools or methods allow. The fundamental principle: you cannot report a calculated or measured value more precisely than your least precise measurement. If you measure length to the nearest centimeter (like 24 cm), you can't honestly report area to the nearest millimeter (like 576.00 cm²)—your measurement tool wasn't that precise! Calculations don't magically create precision; they can only preserve (or lose) the precision from your inputs. Reporting excessive decimal places is false precision—claiming accuracy you don't actually have. In the context of a bathroom scale measuring to nearest 0.1 lb, the value 156.4 lb should be reported as 156.4 lb because the scale's precision is to tenths of a pound. Reporting as 156.40 lb would be false precision—the scale can't distinguish between 156.40 lb and 156.44 lb. Context determines meaningful precision level! Choice C correctly reports to tenths of a pound (156.4 lb) which appropriately reflects the scale's capability of measuring to nearest 0.1 lb. Choice B shows false precision: reporting to 156.40 lb when the scale only justifies precision to tenths. Example: if you measure with a tool accurate to 0.1 lb, reporting 156.40 lb claims you can distinguish hundredths of a pound—but you can't with that scale! Report 156.4 lb instead, matching your measurement capability. Trailing zeros matter: 156.4 vs 156.40 represent different claimed precision (tenths vs hundredths). Only include trailing zeros after the decimal if your measurement actually supports that precision! If measured to tenths, write 156.4 (don't add fake zeros). Trailing zeros after decimal are significant—they're precision claims! When using a digital scale or any measuring device, report your measurement to match the device's displayed precision—no more, no less.
  12. A stopwatch shows time to the nearest 0.1 second. A runner's time is recorded as 12.7 s. In a report, which value shows appropriate precision for the recorded time?​
    Answer: 12.7 s This question tests your understanding that the precision of your reported answer should match the precision of your measurements—you can't claim accuracy beyond what your measurement tools or methods allow. Context determines appropriate precision: reporting money? Use cents ($47.23). Counting people? Use whole numbers (47 people, not 47.3!). Measuring with a ruler marked in mm? Report to nearest mm. Scientific measurement? Use significant figures from your instruments. The situation tells you what level of precision makes sense—follow the natural precision of the context! In the context of a stopwatch showing time to the nearest 0.1 second, the value 12.7 s should be reported as 12.7 s because the stopwatch precision is to tenths of a second. Reporting as 12.70 s would be false precision—the trailing zero suggests the stopwatch could measure to hundredths, but it can't! Context determines meaningful precision level! Choice B correctly reports to 0.1 s precision (12.7 s) which appropriately reflects the stopwatch's measurement capability of displaying to the nearest 0.1 second. Choice A shows false precision: reporting to 12.70 s when the stopwatch only measures to 0.1 s precision. The extra zero (.70 vs .7) claims you can distinguish hundredths of a second—but you can't with that stopwatch! Report 12.7 s instead, matching your measurement capability. Common sense check: does your reported precision make sense? '3.7 people' → no, round to 4. '$24.983561' for grocery bill → no, round to $24.98. '0.00000001 seconds' from stopwatch showing tenths → no, you can't measure that precisely! If your answer looks ridiculous with too many decimals (or a decimal where shouldn't be one), it probably is. Use judgment based on context!
  13. A hiker estimates distance on a map and gets 12.38 km. The map scale and measuring method are only reliable to about the nearest 0.1 km. Round the distance appropriately for this context.
    Answer: 12.4 km This question tests your understanding that the precision of your reported answer should match the precision of your measurements—you can't claim accuracy beyond what your measurement tools or methods allow. The fundamental principle: you cannot report a calculated or measured value more precisely than your least precise measurement. If you measure length to the nearest centimeter (like 24 cm), you can't honestly report area to the nearest millimeter (like 576.00 cm²)—your measurement tool wasn't that precise! Calculations don't magically create precision; they can only preserve (or lose) the precision from your inputs. Reporting excessive decimal places is false precision—claiming accuracy you don't actually have. In the context of map estimation reliable to the nearest 0.1 km, the value 12.38 km should be reported as 12.4 km because the method only justifies precision to tenths. Reporting as 12.38 km would be false precision—can't claim hundredths when the reliability is to tenths. Context determines meaningful precision level! Choice A correctly rounds to tenths which appropriately reflects context requirements. Choice B shows false precision: reporting to hundredths when context only justifies precision to tenths. Example: if you measure with a tool accurate to 0.1 cm, reporting 5.3874 cm claims you can distinguish thousandths of a centimeter—but you can't with that tool! Report 5.4 cm instead, matching your measurement capability. False precision red flags: (1) More decimals than your measuring tool can detect, (2) Fractional counts of discrete things, (3) More sig figs than any input had, (4) Excessive precision for the context (measuring a room 'exactly 12.0000000 feet'). If you see these in your work or others', recognize it as inappropriate precision. Better to round sensibly than claim unjustified accuracy!
  14. A receipt total is computed as 47.2389147.23891 dollars before rounding. For paying at a store (money to the nearest cent), which reporting shows appropriate precision?​
    Answer: $47.24 This question tests your understanding that the precision of your reported answer should match the precision of your measurements—you can't claim accuracy beyond what your measurement tools or methods allow. Context determines appropriate precision: reporting money? Use cents ($47.23). Counting people? Use whole numbers (47 people, not 47.3!). Measuring with a ruler marked in mm? Report to nearest mm. Scientific measurement? Use significant figures from your instruments. The situation tells you what level of precision makes sense—follow the natural precision of the context! In the context of money at a store, the value $47.23891 should be reported as $47.24 because money rounds to cents (hundredths of a dollar). Reporting as $47.23891 would be false precision—stores can't charge fractions of cents! Context determines meaningful precision level! Choice B correctly reports to cents ($47.24) which appropriately reflects standard money precision in commerce. Choice A shows false precision: reporting to $47.23891 when money transactions only work with cents. The extra digits (.891) claim you can pay in thousandths of cents—but you can't in real commerce! Report $47.24 instead, matching how money actually works. The precision decision framework: (1) What's the precision of your measurements? (limited by tools), (2) What's the context? (money → cents, counts → integers, scientific → sig figs), (3) What precision does the calculation support? (can't exceed inputs), (4) What precision is practical/useful? (blueprint vs estimate). Answer all four, and you'll know how to round! When in doubt, match the precision of your inputs—you can't calculate yourself to higher precision than you measured.
  15. A digital thermometer reads to the nearest 0.1°C. It shows 19.6°C. What is an appropriate level of precision for reporting this temperature?
    Answer: 19.6°C This question tests your understanding that the precision of your reported answer should match the precision of your measurements—you can't claim accuracy beyond what your measurement tools or methods allow. The fundamental principle: you cannot report a calculated or measured value more precisely than your least precise measurement. If you measure length to the nearest centimeter (like 24 cm), you can't honestly report area to the nearest millimeter (like 576.00 cm²)—your measurement tool wasn't that precise! Calculations don't magically create precision; they can only preserve (or lose) the precision from your inputs. Reporting excessive decimal places is false precision—claiming accuracy you don't actually have. In the context of a digital thermometer reading to nearest 0.1°C, the value 19.6°C should be reported as 19.6°C because the thermometer's precision is to tenths of a degree. Reporting as 19.60°C would be false precision—the thermometer can't see the difference between 19.60°C and 19.64°C. Context determines meaningful precision level! Choice A correctly reports to tenths of a degree (19.6°C) which appropriately reflects the thermometer's capability of reading to nearest 0.1°C. Choice B shows false precision: reporting to 19.60°C when the thermometer only justifies precision to tenths. Example: if you measure with a tool accurate to 0.1°C, reporting 19.60°C claims you can distinguish hundredths of a degree—but you can't with that thermometer! Report 19.6°C instead, matching your measurement capability. Trailing zeros matter: 19.6 vs 19.60 represent different claimed precision (tenths vs hundredths). Only include trailing zeros after the decimal if your measurement actually supports that precision! If measured to tenths, write 19.6 (don't add fake zeros). Trailing zeros after decimal are significant—they're precision claims! Match your reported precision to your instrument's capability—a thermometer reading to 0.1°C means you report to tenths, not hundredths.
  16. A receipt shows a subtotal of $47.23891 from a calculation. For paying in dollars and cents, round $47.23891 appropriately for this context.
    Answer: $47.24 This question tests your understanding that the precision of your reported answer should match the precision of your measurements—you can't claim accuracy beyond what your measurement tools or methods allow. Context determines appropriate precision: reporting money? Use cents ($47.23). Counting people? Use whole numbers (47 people, not 47.3!). Measuring with a ruler marked in mm? Report to nearest mm. Scientific measurement? Use significant figures from your instruments. The situation tells you what level of precision makes sense—follow the natural precision of the context! In the context of paying with dollars and cents, the value $47.23891 should be reported as $47.24 because money in this context rounds to cents (hundredths of a dollar). Reporting as $47.239 would be impractical—we don't have mills (tenths of cents) in circulation. Context determines meaningful precision level! Choice B correctly rounds to cents ($47.24) which appropriately reflects how money is actually used in dollars and cents transactions. Choice C doesn't consider the context: while the calculation might give $47.239, in the context of paying with cash or standard transactions, reporting to thousandths of a dollar is impractical and unnecessary. For payment purposes, cents (hundredths) is sufficient and appropriate. Match precision to how the answer will be used! The precision decision framework: (1) What's the precision of your measurements? (not applicable here), (2) What's the context? (money → cents), (3) What precision does the calculation support? (many decimals), (4) What precision is practical/useful? (cents for payment). Answer all four, and you'll know how to round! When dealing with money in everyday transactions, always round to cents—that's the smallest unit we use.
  17. A tank is filled at a rate measured as 3.5 L/min (measured to the nearest 0.1 L/min). The filling time is 12 min (measured to the nearest minute). Measurements were made to these precisions. Report the calculated volume added with appropriate precision.
    Answer: 42 L This question tests your understanding that the precision of your reported answer should match the precision of your measurements—you can't claim accuracy beyond what your measurement tools or methods allow. Significant figures tell you how precise a measurement is: 3.2 has 2 sig figs (precise to tenths), while 3.20 has 3 sig figs (precise to hundredths). When you multiply or divide measurements, the result should have the same number of sig figs as your least precise input. Example: 3.2 m × 7.856 m = 25.1392 m² → report as 25 m² (2 sig figs from 3.2). This prevents claiming the product is more accurate than the measurements that went into it! Given measurements of 3.5 L/min (to nearest 0.1 L/min, 2 sig figs) and 12 min (to nearest 1 min, 2 sig figs), we calculate volume: 3.5 × 12 = 42 L. Now, how should we report this? The first measurement has precision to tenths with 2 sig figs, the second to ones with 2 sig figs. For multiplication, we use the least precise number of significant figures, which is 2 sig figs from either. Rounding to 2 sig figs: 42 L. This reflects our actual measurement capability, not false precision. Choice A correctly uses 2 significant figures which appropriately reflects input precision. Choice B shows false precision: reporting to tenths when measurements only justify precision to ones. Sig figs rules prevent false precision in calculations—follow them! Significant figures quick guide for calculations: Multiplication/division → result has sig figs of least precise input (3.2 × 8.467 → 27, two sig figs). Addition/subtraction → result has decimal places of least precise input (3.2 + 8.467 → 11.7, tenths place). These rules prevent false precision. Remember: sig figs represent measurement reliability, not arbitrary rounding!
  18. A purchase total on a receipt is $47.23891 before rounding. For paying in dollars and cents (to the nearest $0.01), which reporting shows appropriate precision?
    Answer: $47.24 This question tests your understanding that the precision of your reported answer should match the precision of your measurements—you can't claim accuracy beyond what your measurement tools or methods allow. Context determines appropriate precision: reporting money? Use cents ($47.23). Counting people? Use whole numbers (47 people, not 47.3!). Measuring with a ruler marked in mm? Report to nearest mm. Scientific measurement? Use significant figures from your instruments. The situation tells you what level of precision makes sense—follow the natural precision of the context! In the context of paying in dollars and cents to the nearest $0.01, the value $47.23891 should be reported as $47.24 because money rounds to cents, and 0.00891 rounds up the third decimal. Reporting as $47.23891 would be false precision—can't have fractional cents in standard transactions. Context determines meaningful precision level! Choice B correctly rounds to cents which appropriately reflects context requirements. Choice A shows false precision: reporting to five decimals when context only justifies precision to two decimals. Example: if you measure with a tool accurate to 0.1 cm, reporting 5.3874 cm claims you can distinguish thousandths of a centimeter—but you can't with that tool! Report 5.4 cm instead, matching your measurement capability. Common sense check: does your reported precision make sense? '3.7 people' → no, round to 4. '$24.983561' for grocery bill → no, round to $24.98. '0.00000001 seconds' from stopwatch showing tenths → no, you can't measure that precisely! If your answer looks ridiculous with too many decimals (or a decimal where shouldn't be one), it probably is. Use judgment based on context!
  19. You time a short sprint using a stopwatch that displays tenths of a second. The recorded time is 12.7 s. In a report, what is an appropriate way to record this time?
    Answer: 12.7 s This question tests your understanding that the precision of your reported answer should match the precision of your measurements—you can't claim accuracy beyond what your measurement tools or methods allow. Context determines appropriate precision: reporting money? Use cents ($47.23). Counting people? Use whole numbers (47 people, not 47.3!). Measuring with a ruler marked in mm? Report to nearest mm. Scientific measurement? Use significant figures from your instruments. The situation tells you what level of precision makes sense—follow the natural precision of the context! In the context of timing with a stopwatch displaying tenths of a second, the value 12.7 s should be reported as 12.7 s because the tool's precision is to tenths. Reporting as 12.70 s would be false precision—can't claim hundredths when the stopwatch doesn't show them. Context determines meaningful precision level! Choice B correctly reports to tenths which appropriately reflects measurement capability. Choice A shows false precision: reporting to hundredths when measurement only justifies precision to tenths. Example: if you measure with a tool accurate to 0.1 cm, reporting 5.3874 cm claims you can distinguish thousandths of a centimeter—but you can't with that tool! Report 5.4 cm instead, matching your measurement capability. Trailing zeros matter: 3.5 vs 3.50 vs 3.500 represent different claimed precision (tenths vs hundredths vs thousandths). Only include trailing zeros after the decimal if your measurement actually supports that precision! If measured to hundredths, write 3.50 (showing you measured hundredths). If measured to tenths, write 3.5 (don't add fake zeros). Trailing zeros after decimal are significant—they're precision claims!
  20. A cashier system calculates a total of $47.23891 before rounding. Round $47.23891 appropriately for the amount a customer should be charged in dollars.
    Answer: $47.24 This question tests your understanding that the precision of your reported answer should match the precision of your measurements—you can't claim accuracy beyond what your measurement tools or methods allow. Context determines appropriate precision: reporting money? Use cents ($47.23). Counting people? Use whole numbers (47 people, not 47.3!). Measuring with a ruler marked in mm? Report to nearest mm. Scientific measurement? Use significant figures from your instruments. The situation tells you what level of precision makes sense—follow the natural precision of the context! In the context of charging money, the value $47.23891 should be reported as $47.24 because money rounds to cents. Reporting as $47.2389 would be false precision—can't have fractional cents in charging. Context determines meaningful precision level! Choice A correctly rounds to cents which appropriately reflects context requirements. Choice C shows false precision: reporting to ten-thousandths when context only justifies precision to cents. Example: if you measure with a tool accurate to 0.1 cm, reporting 5.3874 cm claims you can distinguish thousandths of a centimeter—but you can't with that tool! Report 5.4 cm instead, matching your measurement capability. The precision decision framework: (1) What's the precision of your measurements? (limited by tools), (2) What's the context? (money → cents, counts → integers, scientific → sig figs), (3) What precision does the calculation support? (can't exceed inputs), (4) What precision is practical/useful? (blueprint vs estimate). Answer all four, and you'll know how to round! When in doubt, match the precision of your inputs—you can't calculate yourself to higher precision than you measured. Common sense check: does your reported precision make sense? '3.7 people' → no, round to 4. '$24.983561' for grocery bill → no, round to $24.98. '0.00000001 seconds' from stopwatch showing tenths → no, you can't measure that precisely! If your answer looks ridiculous with too many decimals (or a decimal where shouldn't be one), it probably is. Use judgment based on context!

Start this quiz