Why is Java considered robust?

Why is Java considered robust?

• A. It uses explicit memory management and pointers
• B. It has no error handling
• C. It prohibits exceptions
• D. It emphasizes early error detection and uses garbage collection, exception handling, and memory allocation

Answer: (D)

Robustness in Java comes from automatic memory management, structured error handling, and memory safety guarantees provided by the runtime. Garbage collection reclaims unused objects, which reduces memory leaks and dangling references that can cause crashes or unpredictable behavior in manual memory management. Exception handling gives a clear, centralized way to respond to unusual conditions, allowing programs to fail gracefully or recover without crashing. Memory allocation is managed by the runtime with bounds checks and a strong type system, helping catch errors early and prevent unsafe operations. Together, early error detection and the combination of garbage collection, exception handling, and managed memory allocation make Java more resistant to common faults in real-world use. Other options would reintroduce risky practices (explicit memory management and pointers), would omit error handling entirely, or would disallow exceptions, all of which would weaken robustness.

Robustness in Java comes from automatic memory management, structured error handling, and memory safety guarantees provided by the runtime. Garbage collection reclaims unused objects, which reduces memory leaks and dangling references that can cause crashes or unpredictable behavior in manual memory management. Exception handling gives a clear, centralized way to respond to unusual conditions, allowing programs to fail gracefully or recover without crashing. Memory allocation is managed by the runtime with bounds checks and a strong type system, helping catch errors early and prevent unsafe operations. Together, early error detection and the combination of garbage collection, exception handling, and managed memory allocation make Java more resistant to common faults in real-world use.

Other options would reintroduce risky practices (explicit memory management and pointers), would omit error handling entirely, or would disallow exceptions, all of which would weaken robustness.