In order to maintain system stability, a company ' s software developers cannot merge updates...

Separation of duties is the best description because the person developing the change is not allowed to independently approve or merge that change into the code base. This divides responsibility between development and approval, reducing the risk of unauthorized, unsafe, or malicious changes entering production. Change management is related, but the specific control described is the separation between creating a change and authorizing its implementation. Vulnerability remediation is the process of fixing security weaknesses, which is not the focus here. Collusion prevention is not the main concept; separation of duties can reduce fraud risk, but it cannot fully prevent collusion. Security+ treats separation of duties as an administrative control that supports integrity, accountability, and controlled change.