Which three are bad practices?

Catching ArrayIndexOutOfBoundsException to control array iteration is a bad practice because it indicates a fundamental flaw in loop logic, which should be prevented by explicit boundary checks rather than handled as an exceptional control flow.

Catching Error (e.g., OutOfMemoryError) is a bad practice because these exceptions represent severe, unrecoverable system problems; attempting to silently restart a program after such an error masks critical issues and does not address the root cause.

Checking for FileNotFoundException and informing the user is a good practice, as it handles an expected, recoverable user input error gracefully.

Relying on catching ArrayIndexOutOfBoundsException for program recovery is a bad practice because this exception signals a programmer error and should ideally be prevented by proper bounds checking, rather than being part of a normal error recovery strategy.

Checking for IOException and enabling program recovery is a good practice, as I/O issues are common external problems that robust applications should be prepared to handle and potentially recover from.