The correct answer is B - Ask the team for suggestions. Agile teams are self-organizing. The Scrum Master should facilitate problem-solving by enabling the team to collaboratively decide how to handle bottlenecks.
This approach respects the team's autonomy and encourages shared ownership.
From the PMI Agile Practice Guide:
"Scrum Masters facilitate team collaboration and self-organization. When problems arise, they engage the team in identifying and implementing solutions, rather than solving issues unilaterally." (PMI Agile Practice Guide, Section 4.3 - Servant Leadership and Team Empowerment) Mike Griffiths explains:
"The Scrum Master's role is to facilitate rather than direct. If a team member falls behind, the team should collectively explore options for support, ensuring accountability and transparency." (Mike Griffiths, PMI-ACP Exam Prep, Chapter 4 - Team Performance) Incorrect options:
* A undermines team autonomy and assigns tasks, which the Scrum Master should not do.
* C may help, but addressing issues privately doesn't promote transparency.
* D involves the Product Owner unnecessarily in team internal issues.

Spikes are meant for experimentation and learning, not guaranteed outcomes. According to the PMI Agile Practice Guide (Section 5.2 Spikes), if a spike does not lead to a clear solution, the team can extend or reframe it, especially when aiming for a sustainable long-term solution. Agile supports encouraging experimentation and learning from failure.
Mike Griffiths (PMI-ACP Exam Prep Book, Chapter 7: Problem Detection and Resolution) recommends adapting when a spike's results are inconclusive-redefining the scope and collaborating as a team increases the chance of a valuable outcome.
* Option B is correct: it continues learning and promotes team collaboration.
* Option A undercuts team ownership.
* Option C prioritizes a short-term fix and undermines agile values.
* Option D is not needed at this early stage-root cause analysis is better for recurring or systemic issues.

The correct answer is A - Self-organize. One of the fundamental principles of agile is that teams are self- organizing and cross-functional. During iteration planning, once the stories are accepted into the sprint, the team collaborates to break down those stories into tasks and assign work among themselves based on skills and interest.
From the PMI Agile Practice Guide:
"Agile teams are self-organizing, meaning they collectively decide how to accomplish their work, rather than being directed by others. This principle supports autonomy and trust, and enhances team ownership and commitment." (PMI Agile Practice Guide, Section 4.3 - Team Performance) Mike Griffiths reinforces:
"Agile teams are trusted to manage themselves. Once user stories are selected during iteration planning, the team decomposes stories into tasks and self-assigns work collaboratively." (Mike Griffiths, PMI-ACP Exam Prep, Chapter 4 - Team Performance) Incorrect options:
* B contradicts agile principles of self-assignment and voluntary collaboration.
* C may be valuable for clarification but is not the first action after stories are added.
* D identifying the Scrum Master is irrelevant to the task breakdown phase.

The correct answer is C - Initiate an estimation session because agile planning is iterative and collaborative.
When delivery timing is in question, especially during a release planning session, the team must first estimate the size of the work (epics and user stories). Once estimates are made (often using story points or relative sizing techniques), velocity can be used to forecast delivery timelines.
From the PMI Agile Practice Guide:
"Estimation is typically performed at the beginning of a release or iteration planning session to determine how much work can be completed. Teams use estimation to size items and then apply their known or projected velocity to forecast completion." (PMI Agile Practice Guide, Section 5.3 - Estimation and Velocity) Mike Griffiths' PMI-ACP Exam Prep Book also states:
"Before making any delivery commitments, teams should first engage in collaborative estimation to understand the scope and effort of the work. These estimates then inform velocity-based forecasting." (Mike Griffiths, Chapter 5 - Adaptive Planning) Why the other options are incorrect:
* A - Scrum Masters do not estimate work; estimation is a team activity.
* B - You cannot determine deliverables based on velocity until the work has been estimated.
* D - Historical data can support forecasting but must be preceded by proper estimation of current backlog items.

The correct answer is D - Engaged key stakeholders periodically to collect requirements.
Agile is based on frequent stakeholder collaboration. Continuous engagement ensures evolving needs are captured and prevents misalignment. Waiting for planning meetings or demos is too late to catch missing input.
PMI Agile Practice Guide:
"Agile teams ensure stakeholder engagement is ongoing throughout the project. This helps validate requirements and prevent surprises during reviews." (PMI Agile Practice Guide, Section 4.2 - Stakeholder Engagement) Mike Griffiths:
"Stakeholders should be consulted early and often. Relying on static requirements leads to gaps. Agile teams maintain constant feedback loops." (PMI-ACP Exam Prep, Chapter 3 - Value-Driven Delivery) Incorrect options:
* A is too early and one-time.
* B may help but is reactive.
* C is a predictive approach inconsistent with agile.