Why does numeric precision deserve specific attention when validating COBOL-to-Java transformation?
Select an answer to reveal the explanation.
Short Explanation
If you ignore rounding differences, the numbers just quietly drift. Nothing crashes, nothing warns you, so you have to check precision explicitly.
Full Explanation
COBOL's fixed decimal arithmetic and Java's numeric types can round and truncate differently, so a transformation can be structurally correct while still producing a slightly different figure. That makes numeric precision a specific validation target in COBOL-to-Java transformation testing.
The claim that Java does not support decimal arithmetic at all is incorrect because Java does support decimal arithmetic, through types designed for exact decimal handling.
The claim that COBOL programs never perform numeric calculations is incorrect because numeric calculation is central to most COBOL business logic.
The claim that precision differences only affect how output is displayed, never the underlying stored value, is incorrect because precision differences affect the stored value itself, not merely how it is displayed.
For the exam, treat numeric precision as a specific, checkable validation target.