TheScrum Guideexplains the Definition of "Done" as "a formal description of the state of the Increment when it meets the quality measures required for the product":
* A:It increases transparency by making quality expectations visible to all.
* B:It creates a shared understanding of "complete" across the Scrum Team.

The Definition of "Done" is a team or organizational standard, not the Scrum Master's sole responsibility. The Scrum Guidestates: "If it is not an organizational standard, the Scrum Team must create a Definition of Done appropriate for the product."
* A:Accurate-it defines completion.
* B:True-it can differ by context or product.
* C:Least accurate-the Scrum Team or organization defines it, not just the Scrum Master.

The Daily Scrum is the Developers' event, not the Scrum Master's. TheScrum Guidestates: "The Daily Scrum is a 15-minute event for the Developers of the Scrum Team... The Scrum Master ensures that the Developers have the meeting, but the Developers are responsible for conducting the Daily Scrum." The Scrum Master's role is to ensure it happens and is effective, not to attend mandatorily.
* A:Documenting impediments is a support task, not a Daily Scrum requirement.
* B:Facilitation is optional, only if requested.
* C:Burndown charts aren't mandated; this isn't their purpose.