According to the Scrum Guide, two characteristics of the Daily Scrum are its location and time remain constant and its purpose is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. These characteristics promote consistency, transparency, and adaptation within the Development Team. The other options are not valid characteristics of the Daily Scrum, as they are either irrelevant (such as being held first thing in the morning) or inappropriate (such as being free form, facilitated by the team lead, or consisting of the Scrum Master asking for status).

The correct answer is A, because in accordance with Scrum theory, a group of 100 people should be divided into multiple Development Teams by understanding the product, the product vision and the rules of the Scrum framework, and then dividing itself into teams. This approach respects the self-organization and empowerment of the people who will do the work, and allows them to form cross-functional and collaborative teams that can deliver value.

According to the Nexus Guide2, which is a framework for scaling Scrum, one way to form multiple Development Teams from a large group of people is to ask them to self-organize into teams based on dependencies, skills, domain knowledge, and personal preferences. This approach respects the autonomy and empowerment of the Developers and allows them to choose how they want to work together.

In the Scrum framework, there is no specific role or accountability for a Tester. Instead, the responsibility for quality lies with the entire Scrum Team, particularly the Developers. Scrum emphasizes cross-functional teams, where every team member contributes to all aspects of the development process, including testing. The Developers collectively ensure that the work meets the Definition of Done and maintains high-quality standards. This approach fosters collaboration, shared responsibility, and continuous improvement, aligning with the core principles of Scrum.

According to the Scrum Guide1, the Sprint Planning meeting has a time-box of eight hours or less for a one-month Sprint. The Scrum Master ensures that the meeting is time-boxed and keeps the Scrum Team focused on the objective. If the Development Team cannot forecast how many Product Backlog items it can complete, it should still start the Sprint and work on the most likely items to meet the Sprint Goal. The Sprint Backlog can be updated throughout the Sprint as more is learned. The Scrum Master should also support the team to discuss the reasons for the lack of clarity in the Product Backlog items and how to prevent it from happening again in the next Sprint Retrospective.