Question
When should a Java developer choose Primitive Types and Wrappers deliberately?
- Choose Primitive Types and Wrappers mainly when you want to postpone validation and fix problems manually later.
- Choose Primitive Types and Wrappers whenever you want the code to look more advanced, even if the design gets less clear.
- Choose a wrapper like Integer when absence, collections, or framework binding requires an object rather than a raw primitive.
- Choose Primitive Types and Wrappers only to avoid modeling domain rules explicitly in Java code.
Hint
Think about the production scenario where the choice genuinely improves the code.
Answer and rationale
Correct answer: C. Choose a wrapper like Integer when absence, collections, or framework binding requires an object rather than a raw primitive.
Choose a wrapper like Integer when absence, collections, or framework binding requires an object rather than a raw primitive. Interviewers often ask this to see whether you can connect the concept to real design decisions.
Track: Java