She corrected it:
Elena stared at the blinking cursor on her vintage terminal. She was one step away from passing Module 3 of her C programming certification. The test simulation presented a problem: "Write a program that reads two integers. If their sum is greater than 100, print 'HIGH'. If the sum is between 50 and 100 inclusive, print 'MEDIUM'. Otherwise, print 'LOW'." She smirked. Simple. She quickly typed: c essentials part 1 module 3 test
But the final test question was trickier: "What is the output of this code?" int x = 5; int y = 2; float z = x / y; printf("%f", z); She almost answered 2.5 , but caught herself. Integer division truncates. x / y = 2 , then stored as 2.000000 . The correct output: 2.000000 . She corrected it: Elena stared at the blinking
Then she remembered — Module 3’s hidden trap: 50 <= sum <= 100 is parsed as (50 <= sum) <= 100 . (50 <= 60) is 1 , then 1 <= 100 is always true. So the second if always runs, and if the first if fails, the else prints too. If their sum is greater than 100, print 'HIGH'