Project artifacts (documents, approvals, and records) are essential for regulated or legal-influenced projects. To ensure transparency, traceability, and compliance, the project manager should:
A: Use a governance system to track documentation and ensure control.
D: Keep documents current and accessible to stakeholders.
E: Define processes with the team for consistent artifact management.
Option B focuses on assessment over storage and access.
Option C inappropriately delegates core project management responsibilities to a single function (legal).
Reference:
PMBOK Guide - Seventh Edition, Information and Documentation Management PMI Governance of Portfolios, Programs, and Projects Framework

Information radiators are a key communication tool in Agile and adaptive environments. They are visual displays of project information (e.g., task boards, burn-down charts) that are constantly updated and visible to all stakeholders. They promote transparency, immediate access to project status, and facilitate self-organizing teams.
The Agile Practice Guide specifically recommends the use of information radiators as a best practice to facilitate rapid and visible communication.
Option A (pull communication) requires users to seek out information but doesn't promote transparency.
Option B (push communication) is useful but not as effective in agile environments for real-time visibility.
Option C is incomplete-verbal techniques are informal and limited in accessibility.
Reference:
Agile Practice Guide, Section 5.5.1 - Information Radiators
PMBOK Guide - Seventh Edition, Communication Performance Domain
-

Long user stories can hinder sprint completion and value delivery. The Scrum Master should facilitate a team review of the user stories and work with the product owner to ensure the stories are right-sized and follow the INVEST principle (Independent, Negotiable, Valuable, Estimable, Small, Testable).
Option A aligns with Scrum and Agile practices of team-based refinement and collaboration with the product owner.
Option B unnecessarily involves external stakeholders.
Option C puts the burden on one team member.
Option D promotes discussion but lacks action.
Reference:
Agile Practice Guide, Chapter 5 - Product Backlog Refinement
Scrum Guide - Sprint Planning and Story Sizing