As of httpd 2.4 all of the LoadModule statements have moved from the httpd.conf into conf.modules.d/$configurationFile. The difference is the order in which the files are loaded. The conf.modules.d configurations are loaded before the httpd.conf body is processed, and the conf.d configurations are loaded after the body is processed. What I think this means (haven't tested yet, just noticed while reviewing the security guide) is that in the current state if a user puts any of the directives provided by modules loaded in conf.d configuration scripts httpd will fail to start because the module isn't loaded yet and therefore the Directive is invalid.

Let's move the LoadModule statements from our conf.d configuration files, such as these from the zip's conf.d directory:

# grep LoadModule conf.d/*
conf.d/mod_bmx.conf.sample:LoadModule bmx_module         modules/mod_bmx.so
conf.d/mod_bmx.conf.sample:LoadModule bmx_status_module  modules/mod_bmx_status.so
conf.d/mod_bmx.conf.sample:LoadModule bmx_vhost_module   modules/mod_bmx_vhost.so
conf.d/mod_cluster.conf:LoadModule proxy_cluster_module modules/mod_proxy_cluster.so
conf.d/mod_cluster.conf:LoadModule cluster_slotmem_module modules/mod_cluster_slotmem.so
conf.d/mod_cluster.conf:LoadModule manager_module modules/mod_manager.so
conf.d/mod_cluster.conf:LoadModule advertise_module modules/mod_advertise.so
conf.d/mod_jk.conf.sample:LoadModule jk_module modules/mod_jk.so
conf.d/mod_rt.conf.sample:LoadModule rt_module modules/mod_rt.so

into the appropriate conf.modules.d configuration files.