Elementary School Science Quiz: Improving Communication Devices

20 questions · exam conditions

0:00

Improving Communication DevicesQuestion 1 of 20

Read how Chen improved his drum code. Original: 3 fast taps meant "stop." Test showed one worker near a loud saw could not hear the drum because the saw was too loud. Chen added a tall pole with a red flag and waved it with 3 taps. New test: all workers saw the red flag and stopped. What did Chen learn from testing that led to improvement?

Test showed the drum was too loud, so Chen made it softer and harder to notice.

Test showed workers could not hear near machines, so Chen added a red flag they could see.

Test showed it was too dark outside, so Chen taped glow sticks on a window board.

Test showed the code was perfect, so Chen changed nothing and stopped testing.

← Back to quizzes

Elementary School Science Quiz

Elementary School Science Quiz: Improving Communication Devices

Practice Improving Communication Devices in Elementary School Science with focused quiz questions that help you check what you know, review explanations, and build confidence with test-style prompts.

What this quiz covers

This quiz focuses on Improving Communication Devices, giving you a quick way to practice the rules, question types, and explanations that matter most for Elementary School Science.

How to use this quiz

Try each quiz question before looking at the correct answer. Use the explanations to review missed ideas, then come back to similar questions until the pattern feels familiar.

All questions

Question 1

Test showed the drum was too loud, so Chen made it softer and harder to notice.
Test showed workers could not hear near machines, so Chen added a red flag they could see. (correct answer)
Test showed it was too dark outside, so Chen taped glow sticks on a window board.
Test showed the code was perfect, so Chen changed nothing and stopped testing.

Explanation: This question assesses the skill 1-PS4-4: Use tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance - improving device based on test results. Improving or iterating means making something better after testing shows problems, as part of the engineering design process where you design, build, test, improve, and test again to ensure it works well. Testing reveals what works and what doesn't, allowing us to use those results to decide on targeted changes that solve specific issues, and then test again to verify the improvement. Chen's original device was a drum code with 3 fast taps meaning 'stop.' Testing showed a problem: one worker near a loud saw could not hear the drum because the saw was too loud. Chen improved the device by adding a tall pole with a red flag and waving it with 3 taps. The correct answer says 'Test showed workers could not hear near machines, so Chen added a red flag they could see' which accurately identifies the problem that testing revealed and the improvement made, showing understanding of iteration: test results (showed audibility issue) → analyze (understand why) → improve (make changes that address cause) → test again (verify it worked). A distractor like 'Test showed the code was perfect, so Chen changed nothing and stopped testing' is wrong because it claims no problem when testing showed one, and students might choose this if they do not understand how test results drive improvements. Help students understand iteration using the cycle: Test (find problem) → Think (why problem happened?) → Improve (change something to fix cause) → Test Again (did it work?). Use concrete before-after comparisons: 'Before: could not hear drum near saw. After: added flag. Now: can see signal!' Emphasize targeted improvements: identify specific problem from test, understand cause, change the specific thing causing problem (not random changes).

Question 2

Read how Chen improved his drum code. Original device: 3 fast taps meant "stop." Test showed one worker near a loud saw could not hear the drum. Problem: the drum sound was covered by noise. Chen added a red flag on a tall pole and waved it with 3 taps. New test: all workers saw the flag and stopped. What did Chen learn from testing that led to improvement?

Problem: workers could not see → Improvement: turned off lights → Result: drum worked better
Problem: drum was too soft → Improvement: added red flag → Result: workers could see stop signal (correct answer)
Problem: code was too long → Improvement: used 10 taps → Result: workers stopped late
Problem: no problem → Improvement: none → Result: everyone heard it before

Explanation: This question tests understanding of 1-PS4-4: Use tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance - improving device based on test results. Improving (or iterating) means making something better after testing shows problems. Good improvements solve specific problems found during testing. This cycle continues until device works well. Chen's original device was a drum code with 3 fast taps meaning "stop." Testing showed a problem: one worker near a loud saw could not hear the drum because the drum sound was covered by noise. The cause was that the saw's loud noise masked the drum sound. Chen improved the device by adding a red flag on a tall pole to wave with the drum taps. The improvement addresses the problem because visual signals (flag) are not affected by noise like sound signals are. The correct answer says "Problem: drum was too soft → Improvement: added red flag → Result: workers could see stop signal" which accurately identifies that the drum sound was insufficient (too soft relative to saw noise) and adding a visual signal solved it. This shows understanding of iteration: test results (showed noise interference) → analyze (sound masked by louder sound) → improve (add visual backup) → test again (all workers saw flag). Distractors like "Problem: workers could not see → Improvement: turned off lights" are wrong because the original problem was about hearing the drum, not seeing, and turning off lights would make visibility worse. Students might choose this if they confuse the original problem with the solution. Help students understand iteration using the cycle: Test (find problem) → Think (why problem happened?) → Improve (change something to fix cause) → Test Again (did it work?). Use concrete before-after comparisons: "Before: drum sound covered by saw noise. After: added visible flag. Now: workers see flag even with noise! The flag solved the noise problem." Emphasize using different senses when one is blocked: if sound fails, try sight; if sight fails, try sound. Watch for: students who think making drums louder is the only solution to noise problems.

Question 3

Read how Carlos improved his bike whistle code. Original device: 1 short meant slow, 2 short meant stop. Test showed the whistle was hard to hear when wind blew away. Problem: sound did not reach his friend. Carlos added a bright orange flag to wave when stopping. New test on a windy day: his friend saw the flag and stopped. What change made the device work better?

Problem: wind blocked sound → Improvement: added bright flag → Result: friend saw stop signal (correct answer)
Problem: too dark → Improvement: glow sticks → Result: friend saw flags at night
Problem: door blocked sound → Improvement: moved bell → Result: Jamal heard dinner
Problem: no problem → Improvement: none → Result: it worked perfectly before

Explanation: This question tests understanding of 1-PS4-4: Use tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance - improving device based on test results. Improving (or iterating) means making something better after testing shows problems. We use test results to decide what to change. Good improvements solve specific problems found during testing. Carlos's original device was a bike whistle code using different patterns. Testing showed a problem: the whistle was hard to hear when wind blew the sound away. The cause was that wind dispersed sound waves before they reached his friend. Carlos improved the device by adding a bright orange flag to wave when stopping. The improvement addresses the problem because visual signals (flag) are not affected by wind like sound signals are. The correct answer says "Problem: wind blocked sound → Improvement: added bright flag → Result: friend saw stop signal" which accurately identifies how Carlos switched from sound to sight when wind interfered. This shows understanding of iteration: test results (showed wind problem) → analyze (sound affected by wind) → improve (add visual backup) → test again (friend saw flag). Distractors like "Problem: too dark → Improvement: glow sticks" are wrong because this describes a different scenario - Carlos's problem was wind affecting sound, not darkness affecting sight. Students might choose this if they memorize solutions without understanding which problem each solves. Help students understand iteration using the cycle: Test (find problem) → Think (why problem happened?) → Improve (change something to fix cause) → Test Again (did it work?). Use concrete before-after comparisons: "Before: whistle sound blown away by wind. After: added visible flag. Now: friend sees signal even in wind! The flag solved the wind problem." Emphasize matching solutions to problems: wind affects sound but not sight, so add visual signal. Let students practice: test different signals in various conditions (wind, rain, distance), identify which conditions affect which signals. Watch for: students who apply solutions randomly without considering the specific problem.

Question 4

Read how Carlos improved his bike whistle code. Original: 1 short meant slow, 2 short meant stop. Test showed on a windy day his friend could not hear well because the wind blew the sound away. Carlos added a bright orange flag and used whistle plus waving the flag for "stop." New test: friend saw the flag and stopped. What problem did Carlos solve by improving the device?

Problem: friend could not see in the dark → Improvement: added glow sticks → Result: flag glowed at night.
Problem: friend could not hear in wind → Improvement: added bright flag → Result: friend could see the stop signal. (correct answer)
Problem: bell was too quiet → Improvement: moved bell to stairway → Result: Carlos heard dinner sooner.
Problem: no problem at all → Improvement: changed nothing → Result: it worked the same as before.

Explanation: This question assesses the skill 1-PS4-4: Use tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance - improving device based on test results. Improving or iterating means making something better after testing shows problems, as part of the engineering design process where you design, build, test, improve, and test again to ensure it works well. Testing reveals what works and what doesn't, allowing us to use those results to decide on targeted changes that solve specific issues, and then test again to verify the improvement. Carlos's original device was a bike whistle code with 1 short meaning slow and 2 short meaning stop. Testing showed a problem: on a windy day, his friend could not hear well because the wind blew the sound away. Carlos improved the device by adding a bright orange flag and using whistle plus waving the flag for 'stop.' The correct answer says 'Problem: friend could not hear in wind → Improvement: added bright flag → Result: friend could see the stop signal' which accurately identifies the problem that testing revealed and the improvement made, showing understanding of iteration: test results (showed audibility issue) → analyze (understand why) → improve (make changes that address cause) → test again (verify it worked). A distractor like 'Problem: no problem at all → Improvement: changed nothing → Result: it worked the same as before' is wrong because it claims no problem existed when testing showed wind interference, and students might choose this if they do not connect test results to improvements. Help students understand iteration using the cycle: Test (find problem) → Think (why problem happened?) → Improve (change something to fix cause) → Test Again (did it work?). Use concrete before-after comparisons: 'Before: could not hear whistle in wind. After: added flag. Now: can see signal in wind!' Emphasize targeted improvements: identify specific problem from test, understand cause, change the specific thing causing problem (not random changes).

Question 5

Read how Emma improved her flashlight code. Original: 1 flash=come here, 2=yes, 3=no. Test showed her brother could not see the white flashes in a bright daytime room because the room was too bright. Emma taped red cellophane over her flashlight and tested again. Now he saw the flashes. What problem did Emma solve by improving the device?

Problem: too bright to see white flashes → Improvement: red cellophane → Result: flashes showed up in daylight. (correct answer)
Problem: too dark at night → Improvement: moved bell to stairway → Result: brother heard rings better.
Problem: wind blew sound away → Improvement: added more bulbs → Result: whistle became easier to hear.
Problem: no one knew the code → Improvement: changed it daily → Result: brother guessed the message.

Explanation: This question assesses the skill 1-PS4-4: Use tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance - improving device based on test results. Improving or iterating means making something better after testing shows problems, as part of the engineering design process where you design, build, test, improve, and test again to ensure it works well. Testing reveals what works and what doesn't, allowing us to use those results to decide on targeted changes that solve specific issues, and then test again to verify the improvement. Emma's original device was a flashlight with white flashes for codes like 1=come here, 2=yes, 3=no. Testing showed a problem: her brother could not see the white flashes in a bright daytime room because the room was too bright. Emma improved the device by taping red cellophane over the flashlight. The correct answer says 'Problem: too bright to see white flashes → Improvement: red cellophane → Result: flashes showed up in daylight' which accurately identifies the problem that testing revealed and why the improvement solves it, showing understanding of iteration: test results (showed visibility issue) → analyze (understand why) → improve (make changes that address cause) → test again (verify it worked). A distractor like 'Problem: no one knew the code → Improvement: changed it daily → Result: brother guessed the message' is wrong because it identifies a wrong problem not from testing and a change not made, and students might choose this if they confuse code knowledge with device functionality. Help students understand iteration using the cycle: Test (find problem) → Think (why problem happened?) → Improve (change something to fix cause) → Test Again (did it work?). Use concrete before-after comparisons: 'Before: could not see white flashes in bright room. After: added red cellophane. Now: can see in daylight!' Emphasize targeted improvements: identify specific problem from test, understand cause, change the specific thing causing problem (not random changes).

Question 6

Read how Jamal improved his dinner bell. Original: 2 rings meant 5 minutes, 3 meant now. Test showed it did not work when Jamal's door was closed because the sound was blocked. He moved the bell to the stairway and tested again with the door closed. Jamal heard 3 rings. Did the improvement solve the problem?

Problem: sound blocked by door → Improvement: moved bell to stairway → Result: Jamal heard it with door closed. (correct answer)
Problem: too bright outside → Improvement: used red light → Result: Jamal saw flashes in daylight.
Problem: sound blocked by door → Improvement: changed ring code → Result: Jamal still could not hear it.
Problem: no problem → Improvement: made it prettier → Result: it worked perfectly every time.

Explanation: This question assesses the skill 1-PS4-4: Use tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance - improving device based on test results. Improving or iterating means making something better after testing shows problems, as part of the engineering design process where you design, build, test, improve, and test again to ensure it works well. Testing reveals what works and what doesn't, allowing us to use those results to decide on targeted changes that solve specific issues, and then test again to verify the improvement. Jamal's original device was a dinner bell with 2 rings meaning 5 minutes and 3 meaning now. Testing showed a problem: it did not work when the door was closed because the sound was blocked. Jamal improved the device by moving the bell to the stairway. The correct answer says 'Problem: sound blocked by door → Improvement: moved bell to stairway → Result: Jamal heard it with door closed' which accurately identifies the problem that testing revealed and the improvement made, showing understanding of iteration: test results (showed blockage) → analyze (understand why) → improve (make changes that address cause) → test again (verify it worked). A distractor like 'Problem: no problem → Improvement: made it prettier → Result: it worked perfectly every time' is wrong because it claims no problem existed when testing showed sound blockage, and students might choose this if they do not connect test results to improvements or confuse aesthetics with functional changes. Help students understand iteration using the cycle: Test (find problem) → Think (why problem happened?) → Improve (change something to fix cause) → Test Again (did it work?). Use concrete before-after comparisons: 'Before: could not hear bell through closed door. After: moved to stairway. Now: can hear with door closed!' Emphasize targeted improvements: identify specific problem from test, understand cause, change the specific thing causing problem (not random changes).

Question 7

Read how Marcus improved his window light board. Test showed kids did not always look at the window, and the lights were hard to see in sun. Marcus added a bell that rang with the flashing lights and added more bulbs. New test: kids heard the bell and looked. Why did Marcus add a bell?

Problem: kids were not looking → Improvement: added bell sound → Result: bell got attention so kids looked at lights. (correct answer)
Problem: too dark at night → Improvement: added bell sound → Result: bell made the lights glow brighter.
Problem: wind was loud → Improvement: added bell sound → Result: bell made the wind stop blowing.
Problem: no problem → Improvement: added bell sound → Result: the device worked the same as before.

Explanation: This question assesses the skill 1-PS4-4: Use tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance - improving device based on test results. Improving or iterating means making something better after testing shows problems, as part of the engineering design process where you design, build, test, improve, and test again to ensure it works well. Testing reveals what works and what doesn't, allowing us to use those results to decide on targeted changes that solve specific issues, and then test again to verify the improvement. Marcus's original device was a window light board with flashing lights for signaling. Testing showed problems: kids did not always look at the window, and lights were hard to see in sun. Marcus improved the device by adding a bell that rang with the flashing lights and more bulbs. The correct answer says 'Problem: kids were not looking → Improvement: added bell sound → Result: bell got attention so kids looked at lights' which accurately identifies a key problem and why the improvement solves it, showing understanding of iteration: test results (showed attention issue) → analyze (understand why) → improve (make changes that address cause) → test again (verify it worked). A distractor like 'Problem: no problem → Improvement: added bell sound → Result: the device worked the same as before' is wrong because it ignores the problems found in testing and claims no change in function, and students might choose this if they do not connect additions to solving specific issues. Help students understand iteration using the cycle: Test (find problem) → Think (why problem happened?) → Improve (change something to fix cause) → Test Again (did it work?). Use concrete before-after comparisons: 'Before: kids missed lights. After: added bell. Now: bell alerts them to look!' Emphasize targeted improvements: identify specific problem from test, understand cause, change the specific thing causing problem (not random changes).

Question 8

Read how Jamal improved his dinner bell. Test showed the bell did not work when his door was closed because the sound was blocked. Jamal moved the bell to the stairway and tested again with the door closed. He heard the rings. How did Jamal improve the device?

Problem: too dark → Improvement: added glow sticks → Result: Jamal saw the bell better at night.
Problem: sound blocked → Improvement: moved bell to stairway → Result: sound carried even with door closed. (correct answer)
Problem: wind blew sound → Improvement: taped red cellophane → Result: the bell rang louder in wind.
Problem: no problem → Improvement: changed ring code daily → Result: Jamal got confused each time.

Explanation: This question assesses the skill 1-PS4-4: Use tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance - improving device based on test results. Improving or iterating means making something better after testing shows problems, as part of the engineering design process where you design, build, test, improve, and test again to ensure it works well. Testing reveals what works and what doesn't, allowing us to use those results to decide on targeted changes that solve specific issues, and then test again to verify the improvement. Jamal's original device was a dinner bell for signaling meal times. Testing showed a problem: the bell did not work when his door was closed because the sound was blocked. Jamal improved the device by moving the bell to the stairway. The correct answer says 'Problem: sound blocked → Improvement: moved bell to stairway → Result: sound carried even with door closed' which accurately identifies the improvement made and why it solves the problem, showing understanding of iteration: test results (showed blockage) → analyze (understand why) → improve (make changes that address cause) → test again (verify it worked). A distractor like 'Problem: no problem → Improvement: changed ring code daily → Result: Jamal got confused each time' is wrong because it claims no problem when testing showed one and describes a change not made, and students might choose this if they confuse code changes with physical improvements. Help students understand iteration using the cycle: Test (find problem) → Think (why problem happened?) → Improve (change something to fix cause) → Test Again (did it work?). Use concrete before-after comparisons: 'Before: sound blocked by door. After: moved to stairway. Now: can hear with door closed!' Emphasize targeted improvements: identify specific problem from test, understand cause, change the specific thing causing problem (not random changes).

Question 9

Read how Jamal improved his dinner bell after a test. Original device: 2 rings=5 minutes, 3 rings=now. Test showed it did not work with a closed door because the sound was blocked. Jamal moved the bell to the stairway and kept the same code. New test: Jamal heard 3 rings with the door closed. Why does the improved device work better?

It worked better because the stairway helped the bell sound travel to Jamal's room. (correct answer)
It worked better because the bell was painted red and looked nicer.
It worked better because Jamal changed 3 rings to mean "later."
It worked better because the door got heavier and blocked less sound.

Explanation: This question assesses the skill 1-PS4-4: Use tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance, focusing on improving the device based on test results. Improving or iterating means making something better after testing shows problems, as part of the engineering design process: design, build, test, improve, and test again. Testing reveals what works and what doesn't, and we use those results to decide on changes that solve specific problems, then test again to verify the improvement. Jamal's original device was a dinner bell with 2 rings for '5 minutes' and 3 rings for 'now.' Testing showed a problem: it did not work with a closed door because the sound was blocked. The cause was the door barrier stopping sound waves. Jamal improved the device by moving the bell to the stairway and keeping the same code. The improvement addresses the problem because the stairway allows sound to travel freely to the room. The correct answer says 'It worked better because the stairway helped the bell sound travel to Jamal's room' which accurately identifies why the improvement solves the problem. This shows understanding of iteration: test results (showed blockage) → analyze (understand why) → improve (relocate for better travel) → test again (verify it worked). A distractor like 'It worked better because the door got heavier and blocked less sound' is wrong because it gives a wrong reason, as the door didn't change; the bell location did. Students might choose this if they confuse what was improved or do not understand cause-effect. Help students understand iteration using the cycle: Test (find problem) → Think (why problem happened?) → Improve (change something to fix cause) → Test Again (did it work?). Use concrete before-after comparisons: 'Before: sound blocked by door. After: stairway location. Now: sound travels!' Emphasize targeted improvements: identify specific problem from test, understand cause, change the specific thing causing problem (not random changes). Let students practice: build simple device, test it, find one problem, discuss what might fix it, try improvement, test again.

Question 10

Read how Carlos improved his bike whistle code after a test. Original device: 1 short=slow, 2 short=stop. Test showed it did not work on a windy day because the friend could not hear the whistle well. Carlos kept the whistle code and added a bright orange flag on his bike. New code: whistle + wave flag=stop, just whistle=slow. New test: windy day, friend saw the flag and stopped. Why does the improved device work better?

Problem: Wind blocked sound → Improvement: added orange flag → Result: friend could see the stop signal. (correct answer)
Problem: Bike was too slow → Improvement: added bigger wheels → Result: Carlos rode faster to catch up.
Problem: Flag was too loud → Improvement: removed the whistle → Result: the wind carried the flag sound.
Problem: No problem happened → Improvement: changed nothing → Result: whistle was always easy to hear.

Explanation: This question assesses the skill 1-PS4-4: Use tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance, focusing on improving the device based on test results. Improving or iterating means making something better after testing shows problems, as part of the engineering design process: design, build, test, improve, and test again. Testing reveals what works and what doesn't, and we use those results to decide on changes that solve specific problems, then test again to verify the improvement. Carlos's original device was a bike whistle code with 1 short for 'slow' and 2 short for 'stop.' Testing showed a problem: it did not work on a windy day because the friend could not hear the whistle well. The cause was wind interfering with sound transmission. Carlos improved the device by adding a bright orange flag on his bike, with new code: whistle + wave flag for 'stop,' just whistle for 'slow.' The improvement addresses the problem because the visual flag provides a sight-based signal that wind doesn't affect. The correct answer says 'Problem: Wind blocked sound → Improvement: added orange flag → Result: friend could see the stop signal' which accurately identifies the problem and how the visual addition solved it. This shows understanding of iteration: test results (showed sound issue in wind) → analyze (understand why) → improve (add visual element) → test again (verify it worked). A distractor like 'Problem: No problem happened → Improvement: changed nothing → Result: whistle was always easy to hear' is wrong because it claims no problem existed when testing showed wind interference. Students might choose this if they do not understand how specific conditions like wind cause problems or ignore test results. Help students understand iteration using the cycle: Test (find problem) → Think (why problem happened?) → Improve (change something to fix cause) → Test Again (did it work?). Use concrete before-after comparisons: 'Before: could not hear whistle in wind. After: added flag. Now: can see signal!' Emphasize targeted improvements: identify specific problem from test, understand cause, change the specific thing causing problem (not random changes). Let students practice: build simple device, test it, find one problem, discuss what might fix it, try improvement, test again.

Question 11

Read how Chen improved his drum code after a test. Original device: 3 fast taps meant "stop." Test showed it did not work near a loud saw because one worker could not hear the drum. Chen added a red flag on a tall pole and waved it when tapping 3 times. New test: machines were loud, and workers saw the red flag and stopped. What problem did Chen learn from testing that led to improvement?

The drum was too small to carry, so Chen needed a bigger bag.
The workers could not see the drum, so Chen needed a brighter drum.
The loud saw made the drum hard to hear, so Chen added a visual stop signal. (correct answer)
The drum taps were too colorful, so Chen changed them to quiet taps.

Explanation: This question assesses the skill 1-PS4-4: Use tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance, focusing on improving the device based on test results. Improving or iterating means making something better after testing shows problems, as part of the engineering design process: design, build, test, improve, and test again. Testing reveals what works and what doesn't, and we use those results to decide on changes that solve specific problems, then test again to verify the improvement. Chen's original device was a drum code with 3 fast taps for 'stop.' Testing showed a problem: it did not work near a loud saw because one worker could not hear the drum. The cause was the saw's noise overpowering the drum sound. Chen improved the device by adding a red flag on a tall pole, waving it when tapping 3 times. The improvement addresses the problem because the visual flag provides a sight-based signal unaffected by noise. The correct answer says 'The loud saw made the drum hard to hear, so Chen added a visual stop signal' which accurately identifies the problem from testing and the reason for the visual improvement. This shows understanding of iteration: test results (showed hearing issue in noise) → analyze (understand why) → improve (add visual element) → test again (verify it worked). A distractor like 'The drum taps were too colorful, so Chen changed them to quiet taps' is wrong because it identifies a wrong problem (color) and a change not made, confusing senses. Students might choose this if they do not understand how specific changes solve specific problems or mix up sound and sight. Help students understand iteration using the cycle: Test (find problem) → Think (why problem happened?) → Improve (change something to fix cause) → Test Again (did it work?). Use concrete before-after comparisons: 'Before: could not hear drum in noise. After: added flag. Now: can see signal!' Emphasize targeted improvements: identify specific problem from test, understand cause, change the specific thing causing problem (not random changes). Let students practice: build simple device, test it, find one problem, discuss what might fix it, try improvement, test again.

Question 12

Read how Emma improved her flashlight code. Original device: 1 flash meant come here, 2 meant yes, 3 meant no. Test showed white flashes did not work in bright daytime because they were hard to see. Emma taped red cellophane on her flashlight. New test in a bright room: her brother saw the red flashes. What problem did Emma solve by improving the device?

Problem: bright room hid flashes → Improvement: red filter → Result: brother saw flashes in daylight (correct answer)
Problem: windy day → Improvement: louder whistle → Result: friend heard it far away
Problem: nighttime darkness → Improvement: glow sticks → Result: flags glowed at night
Problem: wrong meaning → Improvement: changed code → Result: 1 flash meant no

Explanation: This question tests understanding of 1-PS4-4: Use tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance - improving device based on test results. Improving (or iterating) means making something better after testing shows problems. We use test results to decide what to change. Testing shows what works and what does not work. Emma's original device was a flashlight code using white light flashes. Testing showed a problem: white flashes did not work in bright daytime because they were hard to see. The cause was that white light does not contrast well against bright backgrounds. Emma improved the device by taping red cellophane on her flashlight. The improvement addresses the problem because red light provides better contrast against bright daylight than white light. The correct answer says "Problem: bright room hid flashes → Improvement: red filter → Result: brother saw flashes in daylight" which accurately identifies how brightness masked white flashes and how the red filter solved this. This shows understanding of iteration: test results (showed brightness interference) → analyze (white blends with bright light) → improve (add color contrast) → test again (brother saw red flashes). Distractors like "Problem: nighttime darkness → Improvement: glow sticks" are wrong because this describes a completely different scenario - Emma's problem was too much light (brightness), not darkness. Students might choose this if they memorize solution patterns without understanding the actual problem being solved. Help students understand iteration using the cycle: Test (find problem) → Think (why problem happened?) → Improve (change something to fix cause) → Test Again (did it work?). Use concrete before-after comparisons: "Before: white flash invisible in bright room. After: red cellophane added. Now: red flash visible in bright room! The color solved the brightness problem." Emphasize that different lighting conditions need different solutions: darkness needs light added, brightness needs contrast added. Watch for: students who think all visibility problems are about adding more light.

Question 13

Read how Sofia improved her flag signals. Original device: wave meant "can play?", hold up meant "yes," down meant "no." Test showed the flags did not work at night because it was too dark to see. Sofia taped glow sticks on both flags. New test at night: her friend saw the glowing flag and answered. Did the improvement solve the problem?

Problem: too windy → Improvement: louder whistle → Result: friend heard it better
Problem: too dark → Improvement: glow sticks → Result: friend saw the flags at night (correct answer)
Problem: too bright → Improvement: turned lights off → Result: no one saw
Problem: no problem → Improvement: none → Result: it stayed the same

Explanation: This question tests understanding of 1-PS4-4: Use tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance - improving device based on test results. Improving (or iterating) means making something better after testing shows problems. Testing shows what works and what does not work. This cycle continues until device works well. Sofia's original device was flag signals using different positions. Testing showed a problem: the flags did not work at night because it was too dark to see them. The cause was lack of light - flags need light to be visible. Sofia improved the device by taping glow sticks on both flags. The improvement addresses the problem because glow sticks produce their own light, making flags visible in darkness. The correct answer says "Problem: too dark → Improvement: glow sticks → Result: friend saw the flags at night" which accurately identifies the problem (darkness), the improvement (adding light source), and confirms the improvement worked. This shows understanding of iteration: test results (showed darkness problem) → analyze (need light to see) → improve (add glow sticks) → test again (friend saw glowing flags). Distractors like "Problem: too bright" are wrong because the test showed darkness was the problem, not brightness - this is the opposite condition. Students might choose this if they confuse different visibility problems or do not understand that darkness and brightness require different solutions. Help students understand iteration using the cycle: Test (find problem) → Think (why problem happened?) → Improve (change something to fix cause) → Test Again (did it work?). Use concrete before-after comparisons: "Before: could not see flag at night. After: added glow stick. Now: can see at night! The glow stick solved the dark problem." Emphasize that improvements must match the specific problem: darkness needs light added, brightness needs contrast or shading. Let students practice: test visual signals in different lighting, identify when each fails, discuss appropriate improvements. Watch for: students who suggest random improvements not connected to the darkness problem.

Question 14

Read how Jamal improved his dinner bell. Original device: 2 rings meant 5 minutes, 3 rings meant now. Test showed Jamal did not hear it when his door was closed because the door blocked sound. Jamal moved the bell to the stairway. New test: door closed, 3 rings, Jamal heard it. What problem did Jamal solve by improving the device?

Problem: sound blocked by door → Improvement: moved bell to stairway → Result: Jamal heard it with door closed (correct answer)
Problem: too sunny → Improvement: added red light → Result: bell was easier to see
Problem: bell was too loud → Improvement: moved it farther → Result: Jamal heard nothing
Problem: wrong code → Improvement: changed to 1 ring → Result: dinner came later

Explanation: This question tests understanding of 1-PS4-4: Use tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance - improving device based on test results. Improving (or iterating) means making something better after testing shows problems. Good improvements solve specific problems found during testing. After improving, we test again to see if the improvement worked. Jamal's original device was a dinner bell with different ring patterns. Testing showed a problem: Jamal did not hear it when his door was closed because the door blocked sound. The cause was that sound waves could not travel through the closed door effectively. Jamal improved the device by moving the bell to the stairway. The improvement addresses the problem because sound from the stairway can travel through the house better than sound blocked by a door. The correct answer says "Problem: sound blocked by door → Improvement: moved bell to stairway → Result: Jamal heard it with door closed" which accurately identifies the problem that testing revealed (sound blocked), the improvement made (relocated bell), and the successful result. This shows understanding of iteration: test results (showed sound blockage) → analyze (door prevents sound travel) → improve (move to open location) → test again (Jamal heard it). Distractors like "Problem: bell was too loud" are wrong because the test showed the opposite - Jamal could not hear it at all, meaning it was too quiet or blocked, not too loud. Students might choose this if they confuse sound problems or think moving something farther always makes it quieter. Help students understand iteration using the cycle: Test (find problem) → Think (why problem happened?) → Improve (change something to fix cause) → Test Again (did it work?). Use concrete before-after comparisons: "Before: bell in room, door blocked sound. After: bell in stairway. Now: sound travels to Jamal! Moving the bell solved the blocked sound problem." Let students practice: test sound devices with barriers, identify what blocks sound, try different locations. Watch for: students who think all sound problems are about volume rather than location or barriers.

Question 15

Read how Sofia improved her flag signals. Test showed the flags did not work at night because it was too dark. She added glow sticks to the flags and tested again at night. Her friend saw the glowing flag and answered "yes." Did the improvement solve the problem?

Problem: too dark to see → Improvement: glow sticks → Result: friend saw the flag at night clearly. (correct answer)
Problem: too dark to see → Improvement: changed nothing → Result: friend still could not see the flag.
Problem: door blocked sound → Improvement: added red cellophane → Result: bell became louder through the door.
Problem: too bright to see → Improvement: turned off glow sticks → Result: flag worked better at night.

Explanation: This question assesses the skill 1-PS4-4: Use tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance - improving device based on test results. Improving or iterating means making something better after testing shows problems, as part of the engineering design process where you design, build, test, improve, and test again to ensure it works well. Testing reveals what works and what doesn't, allowing us to use those results to decide on targeted changes that solve specific issues, and then test again to verify the improvement. Sofia's original device was flag signals for communication like 'can play?' or yes/no. Testing showed a problem: flags did not work at night because it was too dark. Sofia improved the device by adding glow sticks to the flags. The correct answer says 'Problem: too dark to see → Improvement: glow sticks → Result: friend saw the flag at night clearly' which accurately identifies the problem that testing revealed and the improvement made, showing understanding of iteration: test results (showed darkness issue) → analyze (understand why) → improve (make changes that address cause) → test again (verify it worked). A distractor like 'Problem: too dark to see → Improvement: changed nothing → Result: friend still could not see the flag' is wrong because it claims no improvement when one was made and worked, and students might choose this if they do not understand how changes solve problems. Help students understand iteration using the cycle: Test (find problem) → Think (why problem happened?) → Improve (change something to fix cause) → Test Again (did it work?). Use concrete before-after comparisons: 'Before: could not see flag at night. After: added glow sticks. Now: can see glowing flag!' Emphasize targeted improvements: identify specific problem from test, understand cause, change the specific thing causing problem (not random changes).

Question 16

Read how Emma improved her flashlight code. Test showed white flashes did not work in a bright room. She taped red cellophane on her flashlight, kept 1=come here, 2=yes, 3=no, and tested again in daylight. Now her brother saw the red flashes clearly. What change made the device work better?

Problem: too dark → Improvement: added glow sticks → Result: worked at night better than before.
Problem: bright room hid flashes → Improvement: added red cellophane → Result: brother saw flashes in daylight. (correct answer)
Problem: door blocked sound → Improvement: moved a bell → Result: Emma heard rings with the door shut.
Problem: no problem → Improvement: changed nothing → Result: it worked the same as before.

Explanation: This question assesses the skill 1-PS4-4: Use tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance - improving device based on test results. Improving or iterating means making something better after testing shows problems, as part of the engineering design process where you design, build, test, improve, and test again to ensure it works well. Testing reveals what works and what doesn't, allowing us to use those results to decide on targeted changes that solve specific issues, and then test again to verify the improvement. Emma's original device was a flashlight with white flashes for codes like 1=come here, 2=yes, 3=no. Testing showed a problem: white flashes did not work in a bright room because the brightness hid them. Emma improved the device by taping red cellophane on the flashlight. The correct answer says 'Problem: bright room hid flashes → Improvement: added red cellophane → Result: brother saw flashes in daylight' which accurately identifies the improvement made and why it solves the problem, showing understanding of iteration: test results (showed visibility issue) → analyze (understand why) → improve (make changes that address cause) → test again (verify it worked). A distractor like 'Problem: no problem → Improvement: changed nothing → Result: it worked the same as before' is wrong because it claims no problem existed when testing clearly showed one, and students might choose this if they do not connect test results to improvements or think devices are perfect without testing. Help students understand iteration using the cycle: Test (find problem) → Think (why problem happened?) → Improve (change something to fix cause) → Test Again (did it work?). Use concrete before-after comparisons: 'Before: could not see white flashes in bright room. After: added red cellophane. Now: can see red flashes in daylight!' Emphasize targeted improvements: identify specific problem from test, understand cause, change the specific thing causing problem (not random changes).

Question 17

Read how Marcus improved his window light board. Original: flashing lights meant "come in." Test showed it did not work on a sunny day because the lights were not bright enough, and kids were not always looking. Marcus added more bulbs and a small bell that rang when the lights flashed. New test: kids heard the bell, looked, and saw the lights. Why does the improved device work better?

Problem: lights too dim and missed → Improvement: brighter lights plus bell → Result: kids heard bell and saw flashes. (correct answer)
Problem: too dark at night → Improvement: turned off the lights → Result: kids saw better without light.
Problem: sound blocked by a door → Improvement: moved a drum → Result: the drum got quieter.
Problem: wind blew sound away → Improvement: added red cellophane → Result: the whistle became louder.

Explanation: This question assesses the skill 1-PS4-4: Use tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance - improving device based on test results. Improving or iterating means making something better after testing shows problems, as part of the engineering design process where you design, build, test, improve, and test again to ensure it works well. Testing reveals what works and what doesn't, allowing us to use those results to decide on targeted changes that solve specific issues, and then test again to verify the improvement. Marcus's original device was a window light board with flashing lights meaning 'come in.' Testing showed a problem: it did not work on a sunny day because lights were not bright enough, and kids were not always looking. Marcus improved the device by adding more bulbs and a small bell that rang when lights flashed. The correct answer says 'Problem: lights too dim and missed → Improvement: brighter lights plus bell → Result: kids heard bell and saw flashes' which accurately identifies the problems that testing revealed and why the improvements solve them, showing understanding of iteration: test results (showed visibility and attention issues) → analyze (understand why) → improve (make changes that address causes) → test again (verify it worked). A distractor like 'Problem: too dark at night → Improvement: turned off the lights → Result: kids saw better without light' is wrong because it identifies the wrong problem and a change not made, and students might choose this if they confuse day and night conditions. Help students understand iteration using the cycle: Test (find problem) → Think (why problem happened?) → Improve (change something to fix cause) → Test Again (did it work?). Use concrete before-after comparisons: 'Before: missed dim lights. After: added bell and brighter lights. Now: hear and see!' Emphasize targeted improvements: identify specific problem from test, understand cause, change the specific thing causing problem (not random changes).

Question 18

Read how Carlos improved his whistle signals after a test. Original device: 1 short=slow, 2 short=stop. Test showed wind made the whistle hard to hear. Carlos added a bright orange flag and used whistle + flag wave for "stop." New test: friend stopped in the wind. What problem did Carlos solve by improving the device?

Problem: whistle too bright → Improvement: covered it → Result: friend could see it better in sunlight.
Problem: wind made whistle hard to hear → Improvement: added a flag signal → Result: friend could see stop. (correct answer)
Problem: friend forgot to ride → Improvement: added snacks → Result: friend rode longer.
Problem: no problem at all → Improvement: no changes → Result: it always worked in wind.

Explanation: This question assesses the skill 1-PS4-4: Use tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance, focusing on improving the device based on test results. Improving or iterating means making something better after testing shows problems, as part of the engineering design process: design, build, test, improve, and test again. Testing reveals what works and what doesn't, and we use those results to decide on changes that solve specific problems, then test again to verify the improvement. Carlos's original device was whistle signals with 1 short for 'slow' and 2 short for 'stop.' Testing showed a problem: wind made the whistle hard to hear. The cause was wind dispersing sound waves. Carlos improved the device by adding a bright orange flag and using whistle + flag wave for 'stop.' The improvement addresses the problem because the flag adds a visual signal unaffected by wind. The correct answer says 'Problem: wind made whistle hard to hear → Improvement: added a flag signal → Result: friend could see stop' which accurately identifies the problem and targeted improvement. This shows understanding of iteration: test results (showed hearing issue) → analyze (understand why) → improve (add visual) → test again (verify it worked). A distractor like 'Problem: no problem at all → Improvement: no changes → Result: it always worked in wind' is wrong because it denies the test-revealed problem. Students might choose this if they ignore test results or think conditions don't affect devices. Help students understand iteration using the cycle: Test (find problem) → Think (why problem happened?) → Improve (change something to fix cause) → Test Again (did it work?). Use concrete before-after comparisons: 'Before: hard to hear in wind. After: added flag. Now: can see signal!' Emphasize targeted improvements: identify specific problem from test, understand cause, change the specific thing causing problem (not random changes). Let students practice: build simple device, test it, find one problem, discuss what might fix it, try improvement, test again.

Question 19

Read how Jamal improved his dinner bell after a test. Original device: 2 rings=5 minutes, 3 rings=now. Test showed it did not work when Jamal's door was closed because the sound was blocked. Jamal moved the bell to the stairway between floors and kept the same code. New test: door closed, Mom rang 3 times, and Jamal heard it. What change made the device work better?

Problem: Door blocked sound → Improvement: moved bell to stairway → Result: Jamal heard it with the door closed. (correct answer)
Problem: Bell was too bright → Improvement: added paper shade → Result: Jamal saw it better in the dark.
Problem: Rings were too many → Improvement: used 10 rings → Result: Mom stopped ringing so much.
Problem: Jamal was outside → Improvement: moved bell outdoors → Result: it worked better on rainy days.

Explanation: This question assesses the skill 1-PS4-4: Use tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance, focusing on improving the device based on test results. Improving or iterating means making something better after testing shows problems, as part of the engineering design process: design, build, test, improve, and test again. Testing reveals what works and what doesn't, and we use those results to decide on changes that solve specific problems, then test again to verify the improvement. Jamal's original device was a dinner bell with 2 rings for '5 minutes' and 3 rings for 'now.' Testing showed a problem: it did not work when Jamal's door was closed because the sound was blocked. The cause was the door acting as a barrier to sound waves. Jamal improved the device by moving the bell to the stairway between floors and keeping the same code. The improvement addresses the problem because the stairway location allows sound to travel more openly without being blocked by the door. The correct answer says 'Problem: Door blocked sound → Improvement: moved bell to stairway → Result: Jamal heard it with the door closed' which accurately identifies the problem, the improvement made, and why it solved the issue. This shows understanding of iteration: test results (showed sound blockage) → analyze (understand why) → improve (relocate for better sound travel) → test again (verify it worked). A distractor like 'Problem: There was no problem → Improvement: moved bell outdoors → Result: it worked better on rainy days' is wrong because it invents a different problem and change not based on the test, claiming relocation for weather when it was for sound blockage. Students might choose this if they confuse the specific test issue or think improvements are random. Help students understand iteration using the cycle: Test (find problem) → Think (why problem happened?) → Improve (change something to fix cause) → Test Again (did it work?). Use concrete before-after comparisons: 'Before: could not hear with door closed. After: moved to stairway. Now: can hear!' Emphasize targeted improvements: identify specific problem from test, understand cause, change the specific thing causing problem (not random changes). Let students practice: build simple device, test it, find one problem, discuss what might fix it, try improvement, test again.

Question 20

Read how Sofia improved her flag signals after a test. Original device: wave flag=can play, hold up=yes, down=no. Test showed it did not work at nighttime because it was too dark to see. Sofia taped glow sticks to both flags and kept the same motions. New test at night: the friend saw the glowing flag and answered. Why did Sofia add glow sticks?

Problem: Flags were wet → Improvement: added towels → Result: flags dried faster after rain.
Problem: Too dark to see → Improvement: added glow sticks → Result: flags were visible at night. (correct answer)
Problem: Friend heard too much noise → Improvement: whispered the code → Result: friend listened better outside.
Problem: No one liked the colors → Improvement: painted stripes → Result: flags looked nicer in daytime.

Explanation: This question assesses the skill 1-PS4-4: Use tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance, focusing on improving the device based on test results. Improving or iterating means making something better after testing shows problems, as part of the engineering design process: design, build, test, improve, and test again. Testing reveals what works and what doesn't, and we use those results to decide on changes that solve specific problems, then test again to verify the improvement. Sofia's original device was flag signals with wave for 'can play,' up for 'yes,' and down for 'no.' Testing showed a problem: it did not work at nighttime because it was too dark to see. The cause was lack of light making the flags invisible. Sofia improved the device by taping glow sticks to both flags and keeping the same motions. The improvement addresses the problem because glow sticks provide light, making the flags visible in the dark. The correct answer says 'Problem: Too dark to see → Improvement: added glow sticks → Result: flags were visible at night' which accurately identifies the problem from testing and how the improvement solved it. This shows understanding of iteration: test results (showed darkness issue) → analyze (understand why) → improve (add light source) → test again (verify it worked). A distractor like 'Problem: No one liked the colors → Improvement: painted stripes → Result: flags looked nicer in daytime' is wrong because it identifies a wrong problem not from testing and describes a change not made, unrelated to visibility. Students might choose this if they do not connect test results to improvements or confuse aesthetic changes with functional ones. Help students understand iteration using the cycle: Test (find problem) → Think (why problem happened?) → Improve (change something to fix cause) → Test Again (did it work?). Use concrete before-after comparisons: 'Before: could not see flag at night. After: added glow stick. Now: can see at night!' Emphasize targeted improvements: identify specific problem from test, understand cause, change the specific thing causing problem (not random changes). Let students practice: build simple device, test it, find one problem, discuss what might fix it, try improvement, test again.