A project team completed an iteration and the product passed inspection, but an additional feature was added and the customer believes it may introduce new risks. What should the project manager do to prevent this from happening again?

The correct answer is to follow the established change control process and assess the change's further impact. This is a foundational project management principle. Any change, even one intended to add value, must go through a formal change control process to evaluate its impact on scope, schedule, cost, quality, and risk before implementation. This prevents unauthorized or unvetted changes from introducing new problems. Holding frequent reviews with the customer is good practice for confirming expectations but doesn't prevent unauthorized changes from being introduced. Managing the scope baseline is about controlling the defined scope, not preventing changes from being added outside the process. Working with the customer to verify the feature adds value is part of the change evaluation, but it's not the primary action to prevent unauthorized changes from occurring in the first place.