This question is best placed in the People domain because it concerns enabling team clarity, coordination, and effective execution in an agile environment. PMI guidance explains that in agile, the product backlog is the ordered list of work required for the product, and the prioritized backlog signals to the team what work is most important. PMI also notes that backlog planning helps stakeholders and teams decide what the engineering team should work on next. When team members are unclear about upcoming tasks, the most direct and agile-appropriate response is to review the prioritized backlog with the team.
Option B is too narrow because it addresses individuals instead of creating shared team alignment. Option C is too high-level; objectives explain the "why," but not the immediate "what next." Option D shifts responsibility toward functional managers, which is less appropriate in agile cross-functional delivery teams.
The prioritized backlog is the primary mechanism for transparency, sequencing, and shared understanding of upcoming work. Therefore, reviewing it with the team is the most effective strategy and the answer most consistent with PMI agile principles.