KBAT Problems
KBAT Problem: Is the Answer Even Reasonable?
A KBAT problem that rewards estimation and sanity-checking, deciding whether a computed answer can possibly be right.
Estimate before you commit
Before a long calculation, a rough estimate tells you the ballpark the answer must land in. If the final figure is ten times too big or negative when it should be positive, the estimate has caught an error you can then fix.
Understand the problem
An original checking problem. A class of 48 pupils each pays RM23.50 for a trip, and you need the total collected.
Before the exact sum, an estimate sets the scale: about 50 × RM24 = RM1200. That estimate is not the answer, it is a guard rail, so that a slip like a misplaced decimal stands out immediately as unreasonable.
Plan and solve
- Estimate first: 48 ≈ 50 and 23.50 ≈ 24, so the total is roughly 50 × 24 = RM1200.
- Compute exactly: 48 × 23.50 = 48 × 23 + 48 × 0.50 = 1104 + 24 = RM1128.
- Compare with the estimate: RM1128 is close to RM1200, so it is reasonable.
- An answer like RM11 280 or RM112.80 is ten times out, the estimate exposes the decimal error.
Check and a variant
Check the exact figure another way: 48 × 23.50 = 24 × 47 = 1128 as well, confirming it. A twist that rewards the same habit: with only RM1000, how many pupils can pay?
Estimate 1000 ÷ 24 ≈ 41, then compute 1000 ÷ 23.50 = 42.5, which rounds down to 42, because a half-payment cannot join. Estimation both starts and checks the work.
Frequently asked questions
Isn't estimating a waste of time if I'll compute exactly anyway?
No, it is quick insurance. A ten-second estimate tells you the size the answer should be, so a decimal slip or a keying error jumps out instead of slipping through.
In a KBAT question the marks often reward the judgement itself: stating a sensible estimate and comparing it to your worked answer.
How do I round when estimating?
Round each number to something easy, usually one or two significant figures, and keep the rounding balanced so errors do not all push one way. Here 48 became 50 and 23.50 became 24.
The goal is a number you can multiply in your head that lands near the true value, not precision.
When do I round the final answer up versus down?
It depends on what the answer counts. For money collected you keep the exact figure.
For 'how many pupils can afford it' you round down, since a partial payment does not count; for 'how many buses are needed' you round up, since a leftover group still needs a bus. Let the context decide.