University of Central Florida (UCF) COP3330 Object Oriented Programming Final Practice Exam

The behavior of the Java garbage collector is focused on managing memory by identifying and freeing up memory that is occupied by objects that are no longer in use, referred to as unreferenced objects. When an object becomes unreferenced, meaning there are no active references pointing to it, the garbage collector can reclaim that memory, making it available for future allocations. This process helps to prevent memory leaks and optimizes resource usage in Java applications.

The other options present different aspects of memory management that are not accurate descriptions of the garbage collector's primary function. Compacting memory is not always done by the garbage collector; it might be performed during a special type of garbage collection, but that's not a guaranteed action. The garbage collector does not automatically increase the heap size; instead, the heap size is typically managed by the Java Virtual Machine (JVM) based on the program's demands and the settings specified by the user. The `finalize` method can be invoked in certain situations, but it is not a guaranteed action performed by the garbage collector. This method is called only before the object’s memory is reclaimed, but only if it is still reachable at that time, which does not reflect the primary purpose of garbage collection itself.