Mathematical Processes and Applications
What to know
This domain tests how you use mathematics rather than which formula you recall. Expect multi-step word problems that require translating language into equations, selecting a representation (table, graph, equation, diagram), estimating to judge reasonableness, tracking units through calculations, justifying a conclusion, and interpreting an answer back in context. Precision matters: report answers at the requested level of accuracy and include units.
Traps
- Keyword matching fails. “Altogether” does not always signal addition; read for the relationship, not the word.
- Answering a different quantity than requested-finding a total when the question asks for a per-person amount.
- Mixing units, such as minutes and hours or centimeters and meters, inside one calculation.
- Rounding too early and carrying the error into the final answer; round only at the end.
- Ignoring constraints such as “whole number,” “nonnegative,” or “at most,” which can eliminate otherwise valid solutions.
- Assuming unstated conditions; check whether a rate stays constant or a figure is drawn to scale.
Worked example
Convert 45 miles per hour to feet per second. Set up units as factors: (45 mi/1 hr) × (5280 ft/1 mi) × (1 hr/3600 s). Miles cancel, hours cancel, leaving feet per second: 45 × 5280 ÷ 3600 = 66 ft/s. Rule of thumb: write units beside every number and cancel them like algebraic symbols; if the units do not reduce to the target, the setup is wrong before any arithmetic happens.