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 - specifically improving devices based on test results. Testing means trying out the device to see if it works. We test multiple times to learn when device works best and when it does not work. Testing helps us learn problems so we can improve the device. Chen tested his drum code in 3 trials. Tests included: Test 1 (loud machines) - 5/5 heard, SUCCESS; Test 2 (very loud) - 4/5 heard, MOSTLY WORKED; Test 3 (drum in center) - 5/5 heard, SUCCESS. Results: perfect success when drum was centered (5/5), slight problem with very loud conditions when drum wasn't centered (4/5). Pattern discovered: central placement ensures everyone hears the drum. The correct answer says "Move the drum to the center so more hear it" which accurately reflects the improvement shown in Test 3. This is supported by evidence: Test 3 with "drum in center" achieved perfect 5/5 success, solving the problem from Test 2 where only 4/5 heard. The answer shows understanding that sound spreads equally from a central location. Wrong answers like "Make the drum smaller so it is quieter" are incorrect because the problem was one person NOT hearing in Test 2 - making it quieter would make this worse. Students might choose this if they misunderstand the goal (everyone needs to hear) or think quieter is always better. Help students analyze test results by asking: "What made Test 3 work perfectly when Test 2 had a problem?" Draw diagrams showing sound spreading from center vs. edge positions. Emphasize: the goal is for ALL workers to hear the safety signal. Practice: "If someone couldn't hear, do we need louder or quieter? Where should we put it so everyone is equally close?" Watch for: students who suggest making signals quieter when the problem is not being heard.

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 - specifically testing visibility conditions. Testing means trying out the device to see if it works. We test multiple times in different conditions (distance, weather, time of day) to learn when device works best and when it does not work. Sofia tested her flag in 4 trials. Tests included: two sunny distance tests (both successful), one rainy test (partially worked), and one night test (failed). Results: 2 fully successful tests in sunny conditions, 1 partial success in rain, 1 complete failure at night. Pattern discovered: device works when there's light to see the flag but NOT in darkness. The correct answer says "It worked in daylight, but did not work at night without light" which accurately describes the pattern from test results. This is supported by evidence: Tests 1-2 succeeded in sun, Test 3 partially worked with some daylight despite rain, Test 4 failed at night. The answer shows understanding that visual signals need light to be seen. Option B claims "It worked best at night, but did not work on sunny days" which is wrong because it reverses the actual results - the flag worked in sunny conditions and failed at night. Students might choose this if they confuse when visual signals work or misread the test data. Help students analyze test results by creating charts: Test # | Light Condition | Success Level. Have students identify the pattern: "Flags need light to be seen!" Emphasize that visual communication devices depend on visibility conditions. Practice sorting results: "Full success in sun, partial in rain (less light), failure at night (no light)." Watch for students who don't connect light levels to visibility of visual signals.

This question relates to 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 - testing device part. Testing means trying out the device to see if it works, and we test multiple times in different conditions like near or far, day or night, quiet or noisy to learn when the device works best and when it does not. Good testing includes multiple trials, recording results as success or fail, and noticing patterns like it works in some conditions but not others, which helps us learn problems so we can improve the device, and recording results helps us remember what we learned. Sofia tested the flag in 4 trials with conditions including sunny at 20 and 50 feet, cloudy at 20 feet, and night; tests 1 and 2 succeeded fully in sunny, test 3 partially in cloudy, and test 4 failed at night. The correct answer says 'The flag worked best on sunny days, even from 50 feet away' which accurately describes the conditions when the device works best, supported by evidence from tests 1 and 2 succeeding in sunny conditions at both distances. A distractor like 'The flag worked best at night when it was very dark' is wrong because it focuses on the wrong variable and reverses success, as test 4 failed at night, and students might choose this if they do not track multiple test results. Help students analyze test results by creating simple charts: Test # | Condition | Success? Have students identify patterns: 'When did it work? When did it NOT work? What's the pattern?' Emphasize: multiple tests needed because conditions change, one test is not enough; explain that failed tests are good - they show what to improve! If all tests succeed, we might test in too-easy conditions; practice: '3 out of 4 tests worked = mostly works, but needs improvement for dark or cloudy.' Connect to iteration: test results tell us what to change; watch for students who give up after one failure, or who think any failure means device is broken, or who do not notice patterns across multiple tests.

This question relates to 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 - testing device part. Testing means trying out the device to see if it works, and we test multiple times in different conditions like near or far, day or night, quiet or noisy to learn when the device works best and when it does not. Good testing includes multiple trials, recording results as success or fail, and noticing patterns like it works in some conditions but not others, which helps us learn problems so we can improve the device, and recording results helps us remember what we learned. Sofia tested the flag signal in 4 trials with conditions including sunny, cloudy, night, and distances of 20 and 50 feet; tests 1 and 2 succeeded in sunny conditions, test 3 partially worked in cloudy, and test 4 failed at night. The correct answer says 'The flag did not work well when it was dark or very cloudy' which accurately describes the pattern from test results where it failed or partially failed in low light but succeeded in bright conditions, supported by evidence from test 4 failing and test 3 partially working. A distractor like 'The flag did not work when it was sunny and bright outside' is wrong because it reverses when it worked versus failed, as tests 1 and 2 showed success in sunny, and students might choose this if they do not connect conditions to success or failure. Help students analyze test results by creating simple charts: Test # | Condition | Success? Have students identify patterns: 'When did it work? When did it NOT work? What's the pattern?' Emphasize: multiple tests needed because conditions change, one test is not enough; explain that failed tests are good - they show what to improve! If all tests succeed, we might test in too-easy conditions; practice: '3 out of 4 tests worked = mostly works, but needs improvement for dark conditions.' Connect to iteration: test results tell us what to change; watch for students who give up after one failure, or who think any failure means device is broken, or who do not notice patterns across multiple tests.

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 - specifically synthesizing test patterns. Testing means trying out the device to see if it works. We test multiple times in different conditions to understand all factors affecting performance. Recognizing patterns helps us understand device capabilities and limitations. Carlos tested his whistle in 4 trials. Tests included: 10 feet (success), 30 feet (success), 50 feet with wind blowing away (failed), and 50 feet in calm air (success). Results: 3 successful tests including at 50 feet when calm, 1 failed test at 50 feet when wind blew away. Pattern discovered: whistle works at distances up to 50 feet in calm conditions but NOT when wind carries sound away from listener. The correct answer says "It worked up to 50 feet in calm air, but failed when wind blew away" which accurately synthesizes both the distance capability and the wind limitation. This is supported by Test 4 proving 50-foot range works in calm air while Test 3 shows same distance fails with adverse wind. The answer demonstrates understanding of how environmental conditions affect sound travel. Option A claims "It worked in wind, but did not work when the air was calm" which is wrong because it completely reverses the pattern - the whistle actually failed in wind and succeeded in calm air. Students might choose this if they confuse which condition helped vs. hindered sound travel. Help students analyze multiple variables by creating comparison charts: Distance | Wind | Result. Emphasize that two tests at the same distance with different results reveals the importance of wind conditions. Practice pattern recognition: "What's different between Test 3 and Test 4? Both at 50 feet, but different wind conditions and different results!" Teach that wind direction matters for sound - wind can carry sound toward or away from the listener.

This question relates to the skill 1-PS4-4, which involves using tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance, specifically focusing on the testing device part. Testing means trying out the device to see if it works, and we test multiple times in different conditions like sunny, rainy, or night to learn when the device works best and when it does not. Good testing includes multiple trials, recording results as success or fail, and noticing patterns, such as it works in daylight but not at night; this helps us learn problems so we can improve the device, and recording results helps us remember what we learned. Sofia tested the flag signal device in 4 trials, with tests including conditions like sunny at different distances, rainy, and nighttime; results showed 2 successful tests in sunny, 1 partially worked in rainy, and 1 failed at night, for example, Test 1 in sunny at 20 feet worked as friend saw, but Test 4 at nighttime failed as friend could not see; the pattern discovered is the device works in daylight but not at night. The correct answer says 'The flag worked best in daylight, but failed at night' which accurately describes the pattern from test results and conditions when it works or fails, supported by evidence from Tests 1-2 succeeding in sunny daylight, Test 3 partially in rainy daylight, and Test 4 failing at night; this shows understanding that testing reveals when and where the device works, not just yes or no if it works. A distractor like 'The flag worked at night, but not on sunny days' is wrong because it reverses when it worked versus failed, claiming success at night where Test 4 actually failed and failure in sunny where Tests 1-2 succeeded; students might choose this if they do not connect conditions to success/failure or have difficulty identifying patterns in data. To help students, create simple charts like Test # | Condition | Success? and have them identify patterns by asking 'When did it work? When did it NOT work? What's the pattern?'; emphasize that multiple tests are needed because conditions change, failed tests show what to improve, practice saying '2 out of 4 tests fully worked = mostly works, but needs improvement for night,' connect to iteration as results tell us what to change, and watch for students who think one failure means total failure or do not notice patterns across tests.

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 - specifically using test results to guide device use. Testing means trying out the device to see if it works. We test multiple times in different conditions to learn when device works best and when it does not work. Good testing helps us know when to use our device for best results. Marcus tested his light board in 4 trials. Tests included: Test 1 (20 feet) - 10/10 saw, SUCCESS; Test 2 (50 feet) - 8/10 saw, MOSTLY WORKED; Test 3 (bright sunny) - 4/10 saw, PARTIALLY WORKED; Test 4 (cloudy, 50 feet) - 9/10 saw, SUCCESS. Results: high success on cloudy days (9/10) and close distances (10/10), low success in bright sun (4/10). Pattern discovered: device works well on cloudy days but poorly in bright sunshine. The correct answer says "He should use it on cloudy days or indoors" which accurately reflects when the device worked best. This is supported by evidence: Test 4 on a cloudy day had 9/10 success while Test 3 in bright sun only had 4/10 success. The answer shows understanding that bright sunlight makes it hard to see electric lights. Wrong answers like "He should use it only in bright sun at noon" are incorrect because Test 3 showed bright sun had the worst results (only 4/10 saw it). Students might choose this if they think more light always helps, not understanding that bright sunlight can wash out electric lights. Help students analyze test results by comparing success rates: "9 out of 10 on cloudy days vs. 4 out of 10 in bright sun - which is better?" Explain: electric lights show up better when background isn't too bright. Practice: "If you want most kids to see the signal, choose conditions with highest success rate." Watch for: students who think bright conditions always help visibility, not realizing contrast matters.

This question relates to 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 - testing device part. Testing means trying out the device to see if it works, and we test multiple times in different conditions like near or far, day or night, quiet or noisy to learn when the device works best and when it does not. Good testing includes multiple trials, recording results as success or fail, and noticing patterns like it works in some conditions but not others, which helps us learn problems so we can improve the device, and recording results helps us remember what we learned. Sofia tested the flag signal in 4 trials with conditions including sunny, cloudy, night, and distances of 20 and 50 feet; tests 1 and 2 succeeded in sunny conditions, test 3 partially worked in cloudy, and test 4 failed at night. The correct answer says 'The flag did not work well when it was dark or very cloudy' which accurately describes the pattern from test results where it failed or partially failed in low light but succeeded in bright conditions, supported by evidence from test 4 failing and test 3 partially working. A distractor like 'The flag did not work when it was sunny and bright outside' is wrong because it reverses when it worked versus failed, as tests 1 and 2 showed success in sunny, and students might choose this if they do not connect conditions to success or failure. Help students analyze test results by creating simple charts: Test # | Condition | Success? Have students identify patterns: 'When did it work? When did it NOT work? What's the pattern?' Emphasize: multiple tests needed because conditions change, one test is not enough; explain that failed tests are good - they show what to improve! If all tests succeed, we might test in too-easy conditions; practice: '3 out of 4 tests worked = mostly works, but needs improvement for dark conditions.' Connect to iteration: test results tell us what to change; watch for students who give up after one failure, or who think any failure means device is broken, or who do not notice patterns across multiple tests.

This question relates to the skill 1-PS4-4, which involves using tools and materials to design and build a device that uses light or sound to solve the problem of communicating over a distance, specifically focusing on the testing device part. Testing means trying out the device to see if it works, and we test multiple times in different conditions like night or day to learn when the device works best and when it does not. Good testing includes multiple trials, recording results as success or fail, and noticing patterns, such as it works at night but not in bright day; this helps us learn problems so we can improve the device, and recording results helps us remember what we learned. Emma tested the flashlight code device in 4 trials, with tests including night with different flashes and bright daytime; results showed 3 successful tests at night and 1 failed in bright daytime, for example, Test 1 at night succeeded as brother came, but Test 4 in bright daytime failed as brother did not see; the pattern discovered is the device works at night but not in bright daytime. The correct answer says 'Test 4 showed it did not work' which accurately describes the specific test that failed, supported by evidence from Test 4 failing in daytime while Tests 1-3 succeeded at night; this shows understanding that testing reveals when and where the device works, not just yes or no if it works. A distractor like 'Test 1 showed it did not work' is wrong because it confuses details from different tests, claiming failure in Test 1 which actually succeeded; students might choose this if they do not track multiple test results or focus on one test not the pattern across tests. To help students, create simple charts like Test # | Condition | Success? and have them identify patterns by asking 'When did it work? When did it NOT work? What's the pattern?'; emphasize that multiple tests are needed because conditions change, failed tests show what to improve, practice saying '3 out of 4 tests worked = mostly works, but needs improvement for daytime,' connect to iteration as results tell us what to change, and watch for students who think one failure means the device is broken or do not notice patterns across tests.

This question relates to 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 - testing device part. Testing means trying out the device to see if it works, and we test multiple times in different conditions like near or far, day or night, quiet or noisy to learn when the device works best and when it does not. Good testing includes multiple trials, recording results as success or fail, and noticing patterns like it works in some conditions but not others, which helps us learn problems so we can improve the device, and recording results helps us remember what we learned. Jamal tested the dinner bell in 4 trials with conditions including different ring numbers, door closed, and door cracked; tests 1, 2, and 4 succeeded, but test 3 failed when door closed. The correct answer says 'Keep the door open or cracked so Jamal can hear' which accurately describes the improvement based on the specific problem found in tests, supported by evidence from test 3 failing when closed and test 4 succeeding when cracked. A distractor like 'Keep the door closed tightly so the bell stays inside' is wrong because it identifies a problem not shown in tests and would make it worse based on results, and students might choose this if they have difficulty identifying patterns in data. Help students analyze test results by creating simple charts: Test # | Condition | Success? Have students identify patterns: 'When did it work? When did it NOT work? What's the pattern?' Emphasize: multiple tests needed because conditions change, one test is not enough; explain that failed tests are good - they show what to improve! If all tests succeed, we might test in too-easy conditions; practice: '3 out of 4 tests worked = mostly works, but needs improvement for closed doors.' Connect to iteration: test results tell us what to change; watch for students who give up after one failure, or who think any failure means device is broken, or who do not notice patterns across multiple tests.