Using Linear Functions to Solve Problems in Context

A linear model is worth trusting over a short, steady stretch because it assumes one thing only: the quantity changes by a fixed amount each step. A town losing 150 people a year, a rental charging 0.22 dollars a mile, a tank draining at a constant rate — all of these have a constant rate of change, which is exactly what a line captures. The test leans on this because real behavior is often close to straight over the range being asked about, even if it is not straight forever.

The real skill is translation. Read for two numbers: a starting value (what you have before anything changes, the y-intercept) and a rate (how much changes per unit of input, the slope). Every word problem becomes output = start + rate x input, or a variant with extra fixed costs added in. Keep units attached to each number as you write it down — dollars per day, people per year, cents per mile converted to dollars — so the final expression's units match what the question asks for. Once the function is built, 'when does it cross some value' becomes solving an equation, and 'what does it cost' becomes evaluating the function at a given input.

This connects directly to slope as rate of change: the number multiplying the input in your function is exactly the slope of the line you'd graph, and the start value is the y-intercept. It also sets up the extrapolation question — a model built from data in one range says nothing certain about an input far outside that range, because nothing confirms the rate stayed constant that far out. Trust the line where it was built; be skeptical of it everywhere else.