Explanation
The action that ensures that a faulty kernel module is not loaded automatically when the system boots is adding a blacklist line including the name of the offending module to the file /etc/modprobe.d/blacklist.conf.
This file contains a list of kernel modules that are prevented from loading by the modprobe command, which is used to load and unload modules from the running kernel. By adding a line like blacklist <MODULE_NAME> to this file, the module will be ignored by modprobe unless it is explicitly specified as aparameter. This way, the module will not be loaded at boot time or by other modules that depend on it. The other options are either invalid or do not affect the automatic loading of the module.
Using lsmod --remove --autoclean without specifying the name of a specific module will not work, because lsmod does not have such options and it is only used to display the currently loaded modules. Using modinfo -k followed by the name of the offending module will not work, because modinfo does not have a -k option and it is only used to display information about a module. Using modprobe -r followed by the name of the offending module will only remove the module from the running kernel, but it will not prevent it from loading again at the next boot.
Deleting the kernel module's directory from the file system and recompiling the kernel, including its modules, is a drastic and unnecessary measure that will not only remove the faulty module, but also all other modules in that directory, and it will require a lot of time and expertise to perform. References:
* Linux Essentials - Linux Professional Institute Certification Programs1
* Exam 101 Objectives - Linux Professional Institute2
* Linux Kernel Module Management 101 - Linux.com1
* Chapter 2. Managing kernel modules - Red Hat Customer Portal2