Company-managed Scrum project is correct.

Company-managed Scrum project is designed for predictable sprint cycles and provides the Scrum board, sprint planning tools, and the reporting that stakeholders expect such as Epic reporting and sprint reports. These projects offer centralized configuration and governance so Epic tracking and stakeholder reporting work consistently across the engineering squad.

Team-managed Scrum project is not the best choice because team managed projects are intended for a single team and they have simpler configuration and fewer cross team and advanced reports. That makes them less suitable when stakeholders require a formal Epic report and standardized sprint reporting across the squad.

Company-managed Kanban project is not appropriate because Kanban does not use fixed sprint cycles. It is focused on continuous flow and that prevents producing sprint based Epic reports that rely on regular sprint cadence.

Team-managed Kanban project is also incorrect because it combines the limitations of team managed projects with the Kanban flow model. It lacks both the centralized reporting and the sprint structure needed to deliver regular sprint cycles and an Epic report for stakeholders.

Full AWS Practitioner Certification Question