and in my /etc/letsencrypt/live/MYDOMAIN.com/ directory i see:
cert.pem
chain.pem
fullchain.pem
privkey.pem
It would seem like either SSLCertificateChainFile or SSLCACertificateFile should be pointing to the fullchain.pem however both are pointing to chain.pem
this is probably a dumb question, but which one should point to fullchain.pem?
Depending on your Apache version, you may or may not need to set this directive. Again, please read the documentation.
This also depends on your Apache version. If you require to use chain.pem with the SSLCertificateChainFile directive, you won't need fullchain.pem. However, if you don't need to use chain.pem, you can use fullchain.pem without using cert.pem or chain.pem.
SSLCertificateChainFile became obsolete with version 2.4.8, when SSLCertificateFile was extended to also load intermediate CA certificates from the server certificate file.
i apologize for asking questions that are well documented. it appears my httpd.conf file has some obsolete lines.
I think this option has an unfortunate name, since of course the chain file is also a kind of "CA certificate file" (just not a "CA certificate file" that is used for client authentication, but client authentication isn't mentioned anywhere in the option name!).
Of course, I created the unfortunate option name --renew-by-default in Certbot, which has also caused lots of confusion for users and later got renamed to the more descriptive --force-renewal, so I can certainly sympathize with programmers not managing to convey the connotations they intended with their software option names.