Question
Which practice avoids a common mistake with Two-Dimensional Arrays?
- Do not assume every row is initialized or has the same length unless your code explicitly enforces that invariant.
- Ignore the Two-Dimensional Arrays issue and rely on team discipline instead of APIs or contracts.
- Silence the Two-Dimensional Arrays problem by using raw types, broad catches, or shared mutable state.
- Prefer the version of Two-Dimensional Arrays that makes behavior less predictable as long as the code compiles.
Hint
Look for the option that protects correctness instead of hiding the problem.
Answer and rationale
Correct answer: A. Do not assume every row is initialized or has the same length unless your code explicitly enforces that invariant.
Do not assume every row is initialized or has the same length unless your code explicitly enforces that invariant. This is a common failure mode in real Java code and a frequent interview follow-up.
Track: Java