The correct options are It is possible to add a Kanban board to a Scrum based project, Creating a Kanban board from a Scrum project will often leave many issues in the To Do column, Versions can bundle issues for a release in Scrum and they can also be used on Kanban boards, and Once a board is created its type cannot be converted from Scrum to Kanban or the reverse.

It is possible to add a Kanban board to a Scrum based project is true because boards are views built on filters and issue sources rather than rigid project templates. You can create a Kanban board that queries issues from a Scrum project so the same project can be viewed with a Kanban workflow if that view suits the team.

Creating a Kanban board from a Scrum project will often leave many issues in the To Do column is true because Scrum projects frequently use sprints and backlog handling that do not map one to one onto Kanban columns. When a Kanban board is created against a Scrum project the column to status mapping and any sprinted issues can cause a large number of backlog or unassigned issues to remain mapped to the To Do column until the board configuration is adjusted.

Versions can bundle issues for a release in Scrum and they can also be used on Kanban boards is true because Versions or Fix Versions are issue fields that exist independently of board type. You can group and track issues for a release using versions in Scrum via sprints and on Kanban boards by filtering or displaying the Fix Version field.

Once a board is created its type cannot be converted from Scrum to Kanban or the reverse is true because the board type is chosen at creation and Jira does not provide a direct conversion between board types. To change type you create a new board of the desired type and reuse the same filter or copy configuration as needed.

Sharing or copying a board always requires the Share dashboards and filters global permission is incorrect because sharing a board is typically about sharing the underlying filter or configuring board browse permissions and it does not always require that specific global permission. The actual requirement depends on how the board and its filter are shared or who needs access.

You cannot create a Scrum board inside a project that was configured as Kanban is incorrect because project template or initial configuration does not prevent creating a different board type for that project's issues. Boards are separate constructs and you can create a Scrum board that uses issues from a project originally set up with a Kanban template.

Full AWS Practitioner Certification Question