Formal change approval workflow is the correct option because it is the process that ensures stakeholders are notified and the potential effects are evaluated before a modification is applied to IT systems.

A Formal change approval workflow typically includes a request for change, an impact assessment, review by relevant stakeholders, and an approval gate before implementation. This sequence ensures that risks are identified and mitigations are planned and that responsible parties have been informed and have given consent.

Incident response plan is incorrect because an incident response plan defines how to react to security incidents after they occur and it does not provide the prechange notification and approval steps required for routine change control.

Google Cloud Deployment Manager is incorrect because it is an infrastructure provisioning tool and not a governance process. It can automate deployments but it does not by itself enforce stakeholder notification or a formal approval process.

Emergency change policy is incorrect because such a policy is designed for expedited fixes when immediate action is required. It may reduce or bypass the normal approval timeline and therefore does not guarantee that stakeholders are notified and effects are evaluated before the change is applied.

Full AWS Practitioner Certification Question