Walk through how try-with-resources works and why it's strictly better than finally-based cleanup.

try-with-resources auto-closes any AutoCloseable declared in its header, in reverse order of acquisition, generating the close() calls for you.

It's better than a finally block because manual finally cleanup is verbose and, critically, an exception thrown by close() in a finally can suppress the original exception from the try body — try-with-resources instead attaches close() failures as suppressed exceptions (getSuppressed()), so you never lose the root cause. It also correctly handles multiple resources without nested finallys.