Which describes a proper change control process for ERP configurations?

• A. Implement changes directly after minimal approvals.
• B. Change configurations during peak hours to minimize downtime.
• C. Maintain untracked versions of configurations.
• D. A formal change request process with impact analysis, approvals, version control, testing in a separate environment, controlled release, and audit trails.

Answer: (D)

A proper change control process for ERP configurations is about formalizing every modification through a structured workflow before it reaches production. It begins with a formal change request and an impact analysis to identify risks and affected areas, followed by the necessary approvals to ensure stakeholders agree. Changes are tracked with version control so each state is preserved and auditable, and they are tested in a separate environment to verify behavior without disrupting live users. A controlled release plan guides the deployment, and audit trails capture who made what change and why, ensuring accountability and regulatory compliance. This approach reduces risk, enables safe rollback if issues arise, and helps maintain system stability and traceability. Choices that skip risk assessment, push changes during peak hours, or leave configurations untracked fail to provide the necessary control, testing, or visibility.