During execution of a complex project, the project manager receives many change requests from different teams that could prevent the project from meeting its objectives. How should the project manager ensure these changes are managed effectively?

The correct approach is to add the changes to the backlog and review priorities with the product owner. In complex projects, especially those using agile or hybrid approaches, a backlog serves as a prioritized list of work, including new features, enhancements, and bug fixes. The product owner is responsible for maximizing the value of the product resulting from the work of the development team and managing the product backlog. This ensures that all proposed changes are considered, prioritized based on their value and impact, and aligned with project objectives. Logging changes in the risk register is incorrect because these are explicit change requests, not potential uncertain events. Rejecting all change requests is unhelpful and ignores potential improvements or necessary adjustments. Reviewing management plans with a primary stakeholder is too narrow; while important, it doesn't address the process for handling multiple change requests from various teams.