The Scrum Master facilitates the identification, assessment, communication, and escalation of problems and Change Requests generated by the Scrum Team. The Product Owner then evaluates business impact and determines how approved changes should be prioritized within the Prioritized Product Backlog. This separation preserves both facilitation and business accountability.
Option A is contrary to Scrum. Scrum does not attempt to eliminate change; it deliberately accommodates change while maintaining stability during the active Sprint.
Option C is primarily a Product Owner/business stakeholder responsibility when interpreted as formally submitting project changes. Scrum Team members and the Scrum Master may suggest improvements, but the Scrum Master's principal defined change-management responsibility is facilitation, not ownership of business Change Requests.
Option D incorrectly gives approval authority to the Scrum Master. Formal change approval and prioritization are driven by the Product Owner within organizational tolerance levels and applicable Scrum Guidance Body procedures.
Consequently, B accurately reflects the Scrum Master's servant-leadership role: enabling the Scrum Team to surface necessary changes and ensuring that those changes reach the appropriate Product Owner decision process.
Study Guide reference: Change - > Summary of Responsibilities Relevant to Change; Change Requests; Product Owner prioritization.
========
