Identify unauthorized or accidental changes and preserve system integrity is correct. Logging a known good configuration and any deviations from that baseline is primarily about detecting changes that could compromise integrity and then preserving or restoring the system to an expected state.

Recording baselines and deviations creates an auditable timeline that supports detection of unauthorized or accidental changes and it allows security teams to validate integrity. These logs enable faster investigation and forensic analysis when an incident occurs and they support compliance evidence and automated controls that can alert or remediate when a deviation is detected.

Cloud Deployment Manager is incorrect because it names a deployment tool rather than explaining why baselines and deviations must be logged. The question asks for the critical reason for logging and not for a specific orchestration product.

Enable faster recovery and rollback when incidents occur is incorrect as the best answer. While logging baselines can help recovery and rollback, that outcome is a secondary benefit rather than the core security purpose of detecting and preventing unauthorized or accidental changes.

Generate promotional content for security offerings is incorrect because creating marketing materials is unrelated to the operational and security reasons for logging configuration baselines and deviations.

Full AWS Practitioner Certification Question