The Scrum Master can help the Product Owner maintain and update a list of Accepted...

A deliverable that fails its User Story Acceptance Criteria is a Rejected Deliverable. It is not marked Done and normally returns to, or remains in, the Prioritized Product Backlog where it can be reprioritized and completed during a future Sprint. SCRUMstudy explicitly states that rejected User Stories are added back to the updated backlog for future Sprints.

Option A is therefore false because future correction is specifically permitted and expected when necessary. Option B incorrectly states that the Scrum Master defines Acceptance Criteria. They are primarily defined by the Product Owner based on customer requirements. Option D is incorrect because the objective is not to create increments that may satisfy Acceptance Criteria; completed deliverables should satisfy the applicable criteria before acceptance.

Carrying rejected work into a later Sprint is undesirable because the aim is to create potentially shippable, acceptable results during each Sprint, but Scrum provides a clear mechanism for managing such incomplete work.

Therefore, C accurately describes the handling of a rejected deliverable.

Study Guide reference: Review and Retrospect - > Demonstrate and Validate Sprint - > Accepted and Rejected Deliverables.

========