Question
In Java, which comparison about static, final, and Initialization is accurate?
- Static state exists once per class, while instance state exists separately inside each object.
- There is no practical difference in behavior, performance, or API design when static, final, and Initialization is involved.
- The oldest option related to static, final, and Initialization is always the right production choice regardless of context.
- Differences around static, final, and Initialization are mostly cosmetic, so correctness and maintainability do not change.
Hint
Focus on the behavior or tradeoff, not just the keyword.
Answer and rationale
Correct answer: A. Static state exists once per class, while instance state exists separately inside each object.
Static state exists once per class, while instance state exists separately inside each object. This is the comparison that usually separates memorization from understanding.
Track: Java