The loaded and applied property config files include an alder32 checksum of the property key values from the in memory representation. This is great, but it puts the burden on interpretation to understand java property conventions and escapes. For simple property files this works ok.
However we now support multiple files and a json representation.
having a simple to verify "content of the file checksum" can make the validation trivial and less prone to error.
The validation is used to know that the version/content of a file loaded by the broker matches what is present on the file system. Useful when the config reload delay is significant.