When discrepancies arise between documented scope and current deliverables, the first step is to understand why and how they occurred. The project manager should work with the team to review the change history and clarify whether these changes were officially approved. This enables informed conversations with stakeholders and potential corrective action.
According to the PMBOK Guide - Seventh Edition (Measurement and Stakeholder Performance Domains), issue resolution starts with identification and root cause analysis before initiating change or communications actions.
Option A addresses communication frequency but not the root cause.
Option C is premature if a valid change was already made.
Option D may be done later but doesn't resolve the current concern.
References:
PMBOK Guide - Seventh Edition, Scope and Stakeholder Performance Domains PMI Change Control Best Practices