A backout plan provides a documented procedure to revert or undo a change if it fails or causes issues, helping to restore the environment quickly and prevent extended downtime. Having a backout plan in place minimizes impact during failed changes.
User notification (A) informs users but does not prevent failures. Change approval (B) and risk analysis (C) occur before the change and cannot fix issues after failure.
Backout planning is a best practice in Change Management covered in Security Program Management [6:Chapter 16 CompTIA Security+ Study Guide]

The best answer is A. Implementing an update after a board grants approval.
Change management is the formal process used to request, review, approve, test, document, and implement changes to systems and environments in a controlled manner. A common example is submitting a proposed change to a change advisory board (CAB) or other approval authority, receiving approval, and then implementing the update according to procedure.
This answer reflects the structured governance process that Security+ associates with proper change management.
Why the other options are incorrect:
* B. Setting a new password for a userThis is a routine administrative or support task, not a formal example of change management.
* C. Performing a penetration test before deploying a patchPenetration testing is a security assessment activity. It may support decision-making, but it is not itself the best example of the change management process.
* D. Auditing all system equipment before sending the list to the Chief Executive OfficerThis is closer to inventory or audit work, not change management.
From a SY0-701 perspective, change management is about controlled, approved, and documented changes to the environment. Therefore, A is the correct answer.

File Integrity Monitoring (FIM) detects unauthorized changes to files, including deletions, modifications, and permission alterations. When protecting shared data, FIM creates baseline hashes of files and monitors them for unexpected changes. Any deviation triggers alerts, enabling rapid investigation and remediation.
Security+ SY0-701 identifies FIM as a crucial tool for:
Integrity monitoring
Detecting unauthorized file deletion
Identifying malicious or accidental permission changes
Supporting compliance (PCI-DSS, HIPAA, etc.)
DLP (A) protects against data leakage but does not detect permission misconfiguration or deleted files. EDR (B) monitors endpoint activity but is not optimized for shared file integrity. ACL (D) defines permissions but does not track changes.
Thus, C (FIM) is the correct solution.