Is GPG's MDC a valid method of identifying file corruption?

I understand that GPG, when encrypting symmetrically using AES-256, uses a Modification Detection Code. Will this ensure that any corruption (e.g. bitrot) of the encrypted file can be flagged, as opposed to passing silently? How does this protection compare to taking a sha256sum hash of the encrypted file and using that to determine integrity of the encrypted data?

N.B. I'm thinking in a backup context, where my main objective is to archive a large file, and I want to ensure that it is both encrypted, and that any corruption in the archive can be detected.

Recent Questions...