Why are user-interface screenshots a poor basis for assertions about transformed behaviour?
Select an answer to reveal the explanation.
Short Explanation
Screenshots only check the presentation layer, so you'll notice a moved button and miss a wrong balance or database update. That's exactly backwards for transformed behavior.
Full Explanation
The correct choice says screenshots test the presentation layer and miss data effects such as file and database updates, and they break on any cosmetic change while ignoring real value differences. Visual comparison is too sensitive to irrelevant change and too insensitive to what matters, since most of a mainframe program's effect is on data rather than a screen. The repository-storage objection is wrong because storage is not the issue. The no-interface claim is wrong because interfaces may exist; they are just the wrong assertion target. The compute-cost claim is wrong because cost is minor beside correctness. For the exam, assert on computed values and data effects, not rendered output.