The correct answer is D - Create a risk burndown chart showing the reduction of risks over time.
In Agile, risk management is integrated into each iteration. A risk burndown chart is a visual information radiator that tracks the total risk exposure and how it changes over time, making risk transparent and easy for the team to understand.
From the PMI Agile Practice Guide:
"A risk burndown chart can be used to communicate the decreasing level of project risk over time and encourage discussion on risk mitigation strategies." (PMI Agile Practice Guide, Section 6.4 - Risk Management) Mike Griffiths also states:
"Agile teams use tools like risk burndown charts to visualize risks and track mitigation. They provide real- time understanding of current and remaining risks." (Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 6 - Problem Detection and Resolution) Other options:
* A is a responsibility assignment matrix (not risk-focused).
* B and C are traditional (predictive) methods and don't align with Agile risk communication.

The correct answer is A - The team will be unable to understand the iteration ' s status. Agile relies on transparency and timely updates to progress tracking tools such as task boards, burndown charts, and digital boards. Incomplete or delayed updates obscure the team ' s true progress, making it difficult to inspect and adapt.
From the PMI Agile Practice Guide:
"Visibility of progress is key to agile. Without timely updates to task boards or status indicators, teams lose the ability to inspect and adapt effectively during iterations." (PMI Agile Practice Guide, Section 5.2 - Information Radiators) Mike Griffiths emphasizes:
"If user stories or tasks are not updated, burndown charts and velocity metrics become inaccurate. This compromises team transparency and decision-making." (Mike Griffiths, PMI-ACP Exam Prep, Chapter 6 - Problem Detection and Resolution) Incorrect options:
* B is not directly impacted by status updates.
* C might result as a side effect, but A is more fundamental.
* D misrepresents the problem-it is about progress tracking, not collaboration metrics.

The correct answer is D - Provide a delivery range based on the team's estimated velocity.
In Agile, planning is iterative and inherently uncertain. Rather than committing to a fixed schedule, it is best practice to provide a forecasted delivery window based on the team's actual measured velocity. This reflects the inspect-and-adapt mindset of Agile.
From the PMI Agile Practice Guide:
"Agile teams forecast delivery using velocity ranges derived from completed work. Ranges reflect uncertainty and promote realistic expectations with stakeholders." (PMI Agile Practice Guide, Section 5.4 - Adaptive Planning) Mike Griffiths affirms:
"Planning with ranges rather than fixed commitments respects the uncertainty of estimates and the empirical nature of Agile delivery. Forecasts should be based on velocity trends and updated iteratively." (Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 5 - Adaptive Planning) Why the other options are less suitable:
* A suggests triangulating data but wrongly implies a precise commitment.
* B is more of a work preparation activity, not a planning technique.
* C (analogous estimation) is better suited for initial planning, not for an in-progress agile project with real velocity data.

Agile promotes transparency and ongoing communication with all stakeholders, including legal and compliance teams. According to the PMI Agile Practice Guide (Section 7.1 Communications), one of the Scrum Master ' s responsibilities is to keep stakeholders informed of project progress and projections using tools like burnup/burndown charts, velocity trends, or product roadmaps.
Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement) emphasizes that sharing the trajectory of progress and scope delivery builds trust and provides clarity to non-technical stakeholders.
* Option C is correct: sharing actual progress and trends with legal ensures alignment and transparency.
* Option A misplaces the responsibility-it ' s the stakeholders who need visibility.
* Option B shifts product decisions prematurely.
* Option D assumes satisfaction trumps contractual obligations-this can cause legal issues.

The correct answer is C - Encourage all feedback then work with the customer to prioritize work for future sprints. Agile welcomes continuous feedback and values customer collaboration. All feedback should be collected and considered, but the product backlog is reprioritized to align with capacity and business goals.
From the PMI Agile Practice Guide:
"Agile promotes constant feedback to refine product direction. Feedback is incorporated into the backlog, prioritized based on value, and delivered incrementally according to capacity." (PMI Agile Practice Guide, Section 3.4 - Value-Driven Delivery and Continuous Customer Collaboration) Mike Griffiths adds:
"Stakeholder feedback is essential in agile. Not all feedback can be implemented immediately, but it should be welcomed, evaluated, and prioritized transparently in collaboration with the product owner and stakeholders." (Mike Griffiths, PMI-ACP Exam Prep, Chapter 3 - Value-Driven Delivery) Incorrect options:
* A implies a heavy process not aligned with agile.
* B prematurely limits feedback before collaborative prioritization.
* D ignores the product owner's prioritization role.