During an Iteration Review, a stakeholder asks the team to demonstrate a feature that was completed but is not yet integrated with another team's component, so the end-to-end scenario cannot be shown. The Product Owner looks to the Scrum Master for guidance on how to handle the situation in the moment. What is the most appropriate action for the Scrum Master to take?
This is correct because the Iteration Review is a working session for inspecting the increment and adapting the backlog. Demonstrating what is available while being transparent about the unresolved dependency keeps the focus on honesty and learning rather than hiding gaps. Capturing the stakeholder's concern as a candidate backlog item respects the Product Owner's authority over prioritization and turns the feedback into a concrete input for future planning.
Why this answer
The best response is to keep the Iteration Review honest and useful: show what actually works, openly acknowledge the missing integration, and turn stakeholder feedback into an input the Product Owner can prioritize. This preserves transparency, keeps the event focused on inspecting the real increment, and respects the Product Owner's ownership of the backlog while acknowledging the cross-team dependency.
Exam trap
The trap here is believing the team should hide or work around the missing integration to deliver a polished demonstration, rather than transparently showing the real state of the increment.