Question
Which practice avoids a common mistake with Arrays and Indexed Access?
- Ignore the Arrays and Indexed Access issue and rely on team discipline instead of APIs or contracts.
- Silence the Arrays and Indexed Access problem by using raw types, broad catches, or shared mutable state.
- Prefer the version of Arrays and Indexed Access that makes behavior less predictable as long as the code compiles.
- Do not confuse an array's capacity with the number of meaningful elements when the structure is only partially filled.
Hint
Look for the option that protects correctness instead of hiding the problem.
Answer and rationale
Correct answer: D. Do not confuse an array's capacity with the number of meaningful elements when the structure is only partially filled.
Do not confuse an array's capacity with the number of meaningful elements when the structure is only partially filled. This is a common failure mode in real Java code and a frequent interview follow-up.
Track: Java