Chapter 21: Sample Math Questions: Student-Produced Response

Welcome to Last Minute Lecture.

This free chapter overview is designed to help students review and understand key concepts.

These summaries supplement not replaced the original textbook and may not be redistributed or resold.

For complete coverage, always consult the official text.

Welcome to the Deep Dive.

Today we're tackling a really specific and sometimes a tricky part of the SAT math section.

We're talking about the student produced response

you probably know them as grid ins.

Right, the ones where you bubble in your own answer.

No multiple choice options to save you.

Exactly.

You don't pick A, B, C, or D.

You actually have to generate the answer and fill it in correctly.

It feels high stakes.

It can, yeah.

So our goal today is to really break these down, make you feel confident, and give you a full guide based on the official materials.

That's spite on.

And the biggest difference, like you said, no options.

This means you absolutely need to know your stuff, get the right answer, and know the exact procedure for gridding it in.

Precision is key, then.

Absolutely paramount.

You could solve it perfectly, but a tiny mistake in bubbling means no points for that question.

Okay, let's unpack what these things actually are.

So they're math problems.

Right.

You solve them like any other math problem.

But instead of choosing an answer, you write your numerical answer in these little boxes.

Uh -huh.

At the top of the grid.

And then you fill in the corresponding bubbles below on this special grid.

Correct.

And they show up in both math sections, right?

Calculator and no calculator.

Yeah, both.

Right.

You can't really avoid them.

You gotta know how to handle them.

And that grid structure is, well, it's critical.

Writing the answer in the boxes at the top, that's helpful for you, but it's not what's scored.

Uh, okay.

So the written part is just for clarity.

Pretty much.

It's the bubbles below that must be filled in correctly.

That's the only thing the scoring machine reads.

No bubbles filled incorrectly.

Zero credit, even if 3 .5 is sitting right there in the boxes above.

Wow.

Okay.

That's non -negotiable then.

And the grid itself, how many spaces are there?

It's got four columns.

So you can grid answers from say zero up to 9, 8, 9, 9, 9, or decimals or fractions.

And if your answer is just like seven or maybe 12, it doesn't fill all four columns.

That's fine.

You just leave the unneeded columns blank and you don't have to start in the leftmost column either.

You could grid seven in the second column or the third, as long as the bubbles match.

Okay.

Flexible on placement, but strict on the bubbling.

Exactly.

So this is where those little details can really matter.

What are the absolute core strategies and maybe more importantly, the specific gridding rules people need to know.

Okay.

Yeah.

Let's get into the nitty gritty.

These are straight from the official SAT study guide, kind of the list.

First big one, your answer will never be a negative number.

Never ever.

Really?

Never for a student produced response.

So if you calculate something and get say negative five, stop.

Okay.

That's your signal.

You've made a mistake somewhere.

Go back, check your steps, check the question constraints.

It's like a built -in error check from the test makers.

That's actually super helpful.

A silent guardian, as you said earlier, no negatives.

What about fractions and decimals?

That seems like where it could get complicated.

It can seem that way, but the rules are pretty accommodating.

You can use fractions like 712 or 23.

Just use the slash bar bubble.

Okay.

Or you can use decimals, like 2 .5 is fine.

Or for that 23 example, you could grid it as 0 .666 or 0 .667.

Both are accepted.

So for repeating decimals, you just fill the grid.

Fill the grid as much as possible.

For 13, you'd grid 0 .333.

You don't need to round unless the question specifically tells you to round.

And you mentioned 23 could be 0 .666 or 0 .667.

Right.

Either is fine.

The system allows for that slight variation at the end for repeating decimals.

But here's a critical point.

If you get a fraction that's too long for the grid,

like, I don't know, 1236.

Right.

That wouldn't fit.

One, two, two, three, six, five characters.

Exactly.

You must reduce it first.

So 1236 becomes 13.

Then you can grid one, three, three, or you Okay.

So reduce fractions or convert to decimals if they don't fit.

What about leading zeros on decimals, like 0 .5?

Don't grid the leading zero unless it's part of the number, like say 10 .5.

But for something like 0 .5 or 0 .333, you just start with the decimal point bubble.

So grid 0 .5 or 0 .333 saves a column.

Gotcha.

Be as precise as the grid allows, basically.

Precisely.

And another huge one, no mixed numbers.

Ah, okay.

So if I get three and 12.

Nope.

Can't grid that.

You absolutely have to convert it to an improper fraction.

So 72 or its decimal equivalent, 3 .5.

Either 72 or 3 .5 is perfectly fine to grid, just not three space 12.

Okay.

Good to know.

What about symbols?

Dollar signs, percent signs, degrees.

Ignore them for the grid.

If the answer is $500, you just grid 500.

If it's 25%, you grid 25.

The grid is purely for the numerical value.

Makes sense.

And what if somehow a question has two right answers, like maybe X could be two or three?

That's rare, but possible.

If it happens, you just pick one.

Grid either two or three.

Don't try to put both.

Okay, just one answer needed.

Yep.

And a mechanical rule.

Only bubble one circle in any single column.

Seems obvious, but under pressure.

Right.

Easy to make a slip.

And guessing.

Penalty or no penalty?

No penalty for wrong answers on grid ends.

Same as the rest of the SAT now.

But unlike multiple choice where you might eliminate choices, guessing on a grid end is really tough.

If you have absolutely no idea, it might be better to just skip it and save time rather than plugging in a random number.

Okay.

That covers the rules.

Makes sense.

Now let's maybe put these into action.

How about some examples?

Starting with the no calculator section.

Great idea.

Let's look at how these rules apply.

First example, say you get a quadratic equation.

A squared plus 14A equals 51.

And the question adds, it must be greater than zero.

Okay.

Standard quadratic setup.

Right.

The skill is solving quadratics.

Best strategy.

Get it into standard form.

A squared plus 14A minus 51 equals zero.

Set it equal to zero.

Yep.

Then you try to factor it.

This one factors to a plus 17 minus three equals zero.

So solutions are A gay to 17 or equals three.

Exactly.

But remember that condition.

A must be greater than zero.

Right.

So the answer has to be three.

Correct.

You'd grid in three.

That condition is key.

They test if you're reading carefully.

There's sometimes an alternative way to like completing the square, but factoring is often fastest here.

Makes sense.

Paying attention to those constraints is crucial.

Okay.

What about equations with fractions?

Those can look intimidating without a calculator.

Yeah.

Like one half X plus one third Y equals four.

And maybe the question asks, what's the value of three X plus two Y?

Okay.

Doesn't ask for X or Y individually.

Right.

And that's the clue.

The objective is using the equation structure.

Don't try to need 12 X plus 13 Y equals four.

And we want three X plus two Y.

See the connection.

What happens if you multiply that whole first equation by six?

By six.

Okay.

Six times 12 X is three X.

Six times 13 Y is two Y.

Six times four is 24.

Bingo.

Three X plus two Y equals 24.

That's your answer right there.

Wow.

Okay.

So just multiply by the least common multiple of the denominator.

Exactly.

It clears the fractions and often reveals the answer directly.

Much faster than substitution or elimination here.

That's definitely working smarter.

Okay.

How about those ones where X is in the denominator?

Rational equations.

Good one.

Say 24 over X plus one minus 12 over X one equals one.

These look tough.

Yeah, they do.

The strategy is similar actually.

Eliminate the denominators, multiply the entire equation by the common denominator, which is X plus one by one.

Okay.

That's going to cancel things out.

Right.

It'll cancel the denominators in the fractions and you'll have 24 by one 12 X plus one equals one X plus one by one.

Which simplifies.

It simplifies down, usually to a quadratic equation after you expand and collect terms.

For this example, it turns out to be X squared equals 36.

X equals six or X equals nine is six.

Exactly.

And in this case, you'd check if either makes the original denominator zero, X plus one and X one are fine for both six and negative six.

So both are valid solutions.

And since it's a grid in, you could grid either six or minus six.

I'll wait.

No negative six.

So the only possible answer to grid is six.

Wow.

Okay.

That no negative rule is powerful.

All right.

One more no calculator type, circle equations.

Yeah.

They might give you something like X squared plus Y square minus six X plus eight Y equals 144 and ask for the diameter of the circle.

Okay.

Not the standard form.

Right.

The objective is to find a property diameter from this general form.

The key skill is completing the square.

For both X and Y terms.

Correct.

Group the Xs by two, six X group the wise Y two plus eight Y leave the one 44 on the other side.

Then complete the square half of negative six is negative three squared is nine.

Half of eight is four squared is 16.

Exactly.

So add nine and 16 to both sides.

The equation becomes X three two plus Y plus four two plus one 44 plus nine plus 16.

Perfect.

That's the standard form.

XH two plus YK two plus R two.

So what's R squared?

R squared is 169.

So the radius R is the square root of 169, which is 13.

Right.

But careful.

What did the question ask?

The diameter.

Sneaky.

Diameter is twice the radius.

So two times 13 is 26.

And that's what you grid.

26.

Always double check what the question is actually asking for.

Radius, diameter, area, circumference.

Great point.

Okay.

Let's switch gears.

The calculator section problems might be more complex, maybe more data, but the gridding stays the same, right?

Absolutely.

The same gridding rules.

The calculator just helps with, well, calculation.

Let's look at question five, often a data analysis one, maybe a two -way table showing elements, solids, liquids, gases, and metalloids, metals, non -metals.

And the question asks what fraction of the elements that are solids or liquids are also metalloids?

Okay.

Reading carefully.

Fraction of solids or liquids.

So that's the denominator.

Precisely.

Find the total number of solids plus the total number of liquids from the table.

Let's say that total is 92.

Okay.

Denominator is 92.

Now the numerator,

how many of those 92 elements, the solids and liquids, are also classified as metalloids?

You look that up in the table.

Let's say it's seven.

So seven out of those 92, the fraction is 792.

Exactly.

Now you grid it.

You could grid 792 or since you have a calculator.

You could calculate seven divided by 92.

Right.

Which is about 0 .07608.

You can grid that as 0 .076.

Fits perfectly.

Okay.

So either the fraction 792 or the decimal 0 .076 would work.

Correct.

As long as it fits and is accurate.

Got it.

What about unit conversions?

Those always seem to pop up.

Oh yeah.

Question six might be about say transmitting images for Mars.

An image is 11 .2 gigabits.

Data comes in at five megabits per second.

How many complete images can be received in 11 hours?

Whoa.

Okay.

Lots of units.

Gigabits, megabits, seconds, hours.

Exactly.

The objective is managing all those units and rates.

Strategy.

Get everything consistent.

First, how many seconds in 11 hours?

11 hours, 60 minute hours, 60 seconds minute.

Calculator helps here.

39 ,600 seconds.

Okay.

Now how many megabits can be received in that time?

It's five megabits per second.

So 39 ,600 seconds, five megabit second.

198 ,000 megabits.

That's the total data capacity.

Good.

Now the image size, it's 11 .2 gigabits.

We need that in megabits.

The conversion is usually given or standard.

One gigabit equals 124 megabits.

Okay.

So 11 .2 gigabits, 124 megabits gigabit, equal 11 ,468 .8 megabits per image.

Right.

Now the final step.

How many complete images fit into the total capacity?

Divide the total capacity by the size per image.

198 ,000 megabits, 11 ,468 .8 megabits image.

Which comes out to about 17 .26.

But it asks for complete images, so you can't round up.

Exactly.

You can only receive 17 full images.

So grid 17.

Unit analysis is absolutely critical here.

Easy to get lost in the conversions.

Okay.

How about inequalities on the calculator section?

Sure.

Question seven might give you a compound inequality, maybe something derived from a setup like 95 3T plus 174.

Let's say after some steps, you simplify it down to 2120 T 275.

Okay.

So it's between 1 .05 and 5 .4.

Right.

But maybe the question doesn't ask for T.

Maybe it asks for a possible value of 93.

Ah.

Okay.

So we need to find the range for that expression.

We could multiply the inequality of 2120 T 275 by 9 and then subtract 3 from all parts.

Okay.

9, 21, 23 is the whole calculator time again.

9, 1 .05, 3 is 9, 5 .45 and 9, 275, 3 is 9, 5 .43 equals 48 .6, 3 equals 45 .6.

And the question asks for a possible value of 93.

Right.

So you guys need to pick any number between 6 .45 and 45 .6.

Like 7 or 10 or 40 or even a decimal like 44 .25.

Any of those would be correct to grid.

Okay.

So find the range and pick a valid number within it.

Got it.

Need to remember that inequality sign flip if multiplying dividing by a negative, though.

Always.

That's a classic trap.

Okay.

Trigonometry next.

Maybe in the calculator section.

Yep.

Question eight could show an isosceles triangle, maybe label an angle X, give some side lengths and ask for cosecs.

Isosceles.

So two sides are equal.

Two base angles are equal.

Correct.

The key strategy often is to drop a perpendicular height from the vertex angle down to the base.

That splits the isosceles triangle into two congruent right triangles.

Exactly.

And once you have a right triangle, finding cosine is easy.

Remember S -O -H -C -A -H -T -O -A.

Adjacent overhypotenuse for cosine.

Right.

So using the side lengths in that new right triangle, you might need Pythagorean theorem to find one side, you calculate adjacent hypotenuse.

Let's say it comes out to 1224.

Which simplifies to 12.

Yep.

So cosecs equals 12.

Now, how do you grid that?

You could grid one, two, or the decimal equivalent 0 .5.

Perfect.

Or even an unsimplified but equivalent fraction that fits, like two, four, three, H, all represent 12.

So multiple correct ways to grid the same value.

As long as it's equivalent and fits.

Yep.

Okay.

Nearly there.

How about another multi -step problem, maybe involving money or percentages?

Sure.

Question nine could be about foreign exchange.

Sarah buys 602 rupees for $9 .50, but there's also a 4 % transaction fee on the dollars.

It asks for the exchange rate in rupees per dollar, rounded to the nearest whole number.

Okay.

Multi -step.

First, find the total dollar cost, including the fee.

Right.

$9 .50 plus 4 % of $9 .50.

That's $9 .51 or four cents.

Calculator.

$9 .51 in four rupees, $9 .88.

How many rupees per $1?

Set up a ratio.

602 rupees, $9 .88 over rupees $1.

Exactly.

Solve for our RR tool.

62, $9 .88.

Calculator.

602, $9 .88 is $60 .93.

And the question says round to the nearest whole number.

So 61, you'd grid six to one.

Correct.

Bringing it down into steps.

Find total cost, then calculate the rate.

Makes sense.

Okay.

One final complex one from the guide.

Maybe that prepaid card problem.

Yes.

Question 10.

This one ties several concepts together.

Sarah has 7 ,500 rupees on a prepaid card she bought at some exchange rate, dollars per rupee, let's call it D2R.

She could instead use a traveler card that charges the dollars plus a 4 % fee.

The question asks for the least number of rupees she must plan to spend so that using the prepaid card is cheaper than using the traveler card for the entire amount.

Okay.

That's intricate.

We're comparing total costs.

Exactly.

It involves setting up an inequality.

The cost with the traveler card for X rupees would be XDR, $1 .04.

The cost of X rupees on the prepaid card is just XDR dollars if X is less than or equal to 7 ,500, but the problem implies she wants to spend more.

Let's reread that source setup.

Okay.

The source sets it up comparing the value obtained.

So the value from the prepaid card is 7 ,500 rupees.

The value from the traveler card for D dollars is 7 rupees per dollar.

The traveler card cost is 1 .04 D dollars.

You want the rupees you get from the traveler card, D1 .04, to be less than or equal to the 7 ,500 rupees on the prepaid card.

No way.

That's if the traveler card is better.

We want the prepaid card to be cheaper.

So the effective rupees per dollar on the traveler card is worse.

Let's look at the source explanation again carefully.

It says you want the cost in dollars using the prepaid method.

Let's assume the initial purchase costs D dollars for 7 ,500 rupees to be less than or equal to the cost using the traveler card for reband.

Traveler card cost for R rupees is R rupees per dollar 1 .04.

The initial exchange rate was 7 ,500 rupees for D dollars or D 7 ,500 dollars per rupee.

So the traveler cost is R D 7 ,500, 1 .04.

You want D, R D 7 ,500, 1 .04.

Okay.

Divide both sides by D.

Right.

Assuming D is in zero.

So 1 .04, 1 .04.

Rearrange to solve for RRs of 7 ,500, 1 .04.

Calculator, 7 ,500, 1 .04, 8 ,7211 .53.

So the least whole number of rupees she must spend for the prepaid card to have been cheaper or equal per rupee is 7 ,13 ,212.

Okay.

That took some careful set up of following the source logic.

Setting up that inequality correctly is everything.

Absolutely.

It's about translating the word problem into a mathematical comparison.

Phew.

Okay.

We've gone through a ton of rules and examples.

Thinking back over all this, what are the biggest pitfalls or the absolute must do best practices people should walk away with?

I'd say three main things stick out.

One, always, always convert mixed numbers, either improper fractions or decimals.

The grid simply cannot handle 312.

Right.

Non -negotiable.

Two, manage your fractions and decimals for the grid.

Reduce fractions if needed.

For decimals, fill the grid, but don't add unnecessary leading zeros.

Make sure it fits and it's accurate.

Don't over -round unless told to.

Fit and accuracy.

Got it.

And three, double check that your answer makes sense.

Does the number seem reasonable for the question asked?

If you're finding the number of students and get 4 .5, something's wrong.

If you calculate an angle and get 200 degrees, check your work.

That kind of basic sanity check.

Yeah, that final glance can catch simple errors.

And of course, practice.

Use the official resources, like the problems linked to chapter 21 on sappractice .org.

Getting familiar with the types of questions and the gridding process itself builds huge confidence.

So wrapping this all up, what's the big picture for someone prepping for the SAT?

Well, this deep dive into just one chapter, chapter 21, on one question type shows the level of detail involved.

It's not enough to just know the math.

For grid -ins, you have to know how to present that answer correctly according to very specific rules.

It's about both the solution and the submission method.

Exactly.

We've covered the skills, the strategies, different question types from no calculator to calculator, walked through official examples, and highlighted the key tips.

This gives you solid foundation for tackling these student produced response questions.

Fantastic.

So we've thoroughly explored chapter 21 of the official SAT study guide, hitting all the key points on grid -ins.

We have indeed.

From the basics to complex multi -step problems covering the strategies and pitfalls, listeners should now have a comprehensive understanding of this section.

And with that, our deep dive is complete.

Huge thanks for joining us today on the deep dive.

Keep learning, keep practicing those grid -ins, and we'll catch you on the next one.