The correct answers are Any user with a Jira license can create and administer a team-managed project, Project administrators can define new roles within a team-managed project, and Team-managed projects allow adding custom quick filters on top of the board filter.

Any user with a Jira license can create and administer a team-managed project is correct because team-managed projects are designed for small autonomous teams and creation and administration are available to licensed users by default unless the site administrator has explicitly restricted project creation. This means the creator becomes the project admin and can manage the project without needing central administration permissions.

Project administrators can define new roles within a team-managed project is correct because team-managed projects provide project-scoped roles and permission controls that project admins can configure directly. The roles and permissions are managed inside the project so admins can adapt them to the team's needs without changing global settings.

Team-managed projects allow adding custom quick filters on top of the board filter is correct because boards in team-managed projects support quick filters that let the team add simple JQL or field based filters on top of the board filter to focus the view during planning and standups.

A team can run parallel sprints that span several team-managed projects is incorrect because team-managed boards and sprints are scoped to a single project or a single board that is tied to that project. They do not support cross project sprints in the way company managed projects or cross project boards might.

Project settings for a team-managed project can be shared with other projects is incorrect because team-managed projects are intentionally independent. Their configurations are local to the project and cannot be shared or inherited by other projects in the same way that company managed schemes can.

You can make a team-managed project publicly readable to anonymous visitors is incorrect because team-managed projects do not support exposing the project to anonymous public access through project level settings. Public or anonymous access is controlled at the site or global level and is not a standard capability of team-managed project settings.

Full AWS Practitioner Certification Question