After a merger, a consultant was hired to advise on information security. During an iteration, the consultant requests changes to a software component, claiming it does not meet market requirements. What should the project manager do?

The project manager should continue the iteration and review the change with the customer. In an agile environment, changes are expected and managed through a controlled process. The consultant's request is a proposed change that needs evaluation. Reviewing it with the customer (or product owner, who represents the customer) ensures that the proposed change aligns with the project's objectives and customer value, and allows for proper prioritization and impact assessment. Adding the changes immediately without review (first and fourth options) bypasses the change control process and risks scope creep or misalignment with customer needs. Canceling the iteration (third and fourth options) is an extreme measure not warranted by a change request; iterations are designed to be flexible enough to accommodate such discussions.