Primary objective of the Sprint Review
IMHO neither of those answers are correct. The closest one is the green highlighted answer, but still, it is too oversimplified, thus incorrect overall. The main purpose of Sprint Review is a collaboration between Scrum Team (Developers, Scrum Master, and Product Owner) and Stakeholders that may influence the upcoming Sprint and Product Backlog. If PO is not aware of results of the current Sprint, and Sprint Review is held only for his sake, then it is rather something wrong here.
Did you choose the answer highlighted as red? Can you tell us why? What is the reasoning behind it?
In case that image is ever taken offline, or people are unable to read from the image, this is the text of the green answer:
The primary objective of the Sprint Review is to demo the Sprint work and to receive feedback from the Product Owner(s) on the work completed in the Sprint.
It seems like you are taking some kind of practice exam. Unfortunately there are a lot of well meaning people who have set up such exams, with a shaky knowledge of Scrum and agility. There are also charlatans who set these up in an attempt to make money, despite not being able to offer a quality product.
Either way, you should always be critical of such exams, and I think it's a good thing that you came here, to verify the answer from a separate source.
I object to the assertion that a Sprint Review is intended to demo anything to a Product Owner. If that's the case, then it's probably a waste of stakeholders' time to attend. I'm also suspicious of the loose pluralization of Product Owner(s). By default a Sprint Review is for one product, and so there should be one Product Owner. While it is possible to hold the Sprint Reviews for multiple products simultaneously, it relates to such a specific choice made around implementing Scrum, that I wouldn't expect an exam question to acknowledge it.
Instead, I suspect the question's author doesn't understand or agree with the Product Owner role, as described in the Scrum Guide.
Piotr's answer is definitely a lot better.
I would probably include the words "Inspect" and "Adapt" at some point in an ideal answer, as they're two crucial concepts for empirical decision making.
Some things that can be inspected at a Sprint Review:
Increment, Product Backlog, what was "Done" (according to the definition of "Done"), what was not "Done", what went well, problems encountered, and how they were solved, progress towards a milestone of some kind, changes in the market place.
The most common thing to be adapted at (or as a result of) the Sprint Review, would be the Product Backlog.
Thank you very much.
I installed app from Google play called Ceftif. CSM
I will remove it since the answers are to being totally correct.
I will stick with http://mlapshin.com/index.php/psm-quiz/
MLapshin practice exams are very good, as they are directly derived from the Scrum Guide. Personally, I would not trust any other Scrum source other than MLapshin and Scrum.Org.
Regarding the Sprint Review, an often overlooked aspect that I consistently remind teams/management about is the discussion around Sprint challenges and experiences, and what the team did (if anything) to address or mitigate them. It is much more than a simple demo or showcase.