The correct options are Users can add a Scrum board inside a project that is configured for Kanban, Users can create a Kanban board in a project that uses Scrum practices and A board is only a view of issues and teams can create multiple Scrum or Kanban boards in any company-managed project.

Jira boards are essentially saved views or filters over issues, so A board is only a view of issues and teams can create multiple Scrum or Kanban boards in any company-managed project is accurate. Teams often create multiple boards to represent different workflows or team views and each board can use either the Scrum or Kanban board type.

Because boards are views rather than tightly coupled project artifacts, Users can add a Scrum board inside a project that is configured for Kanban and Users can create a Kanban board in a project that uses Scrum practices are both correct. You can create a board of one type that surfaces the project issues even if the project practices or workflows are oriented toward the other board type.

Users cannot create a Kanban board in a project that uses Scrum workflows is incorrect because Jira does not block creating a Kanban board simply because the project uses Scrum workflows. Boards are views and can be created independently of the underlying workflow scheme.

Boards are hard linked to project templates and cannot be modified without recreating the project is incorrect because boards and their configurations can be edited and boards are not irrevocably tied to the project template in a way that requires project recreation to change them.

Users are prevented from having both Kanban and Scrum boards in the same project is incorrect because a single company-managed project can host multiple boards of different types at the same time and teams commonly run both kinds of boards against the same set of issues.

Full AWS Practitioner Certification Question