Issues move to the Unmapped statuses column and the column status becomes hidden from the board is correct.

Issues move to the Unmapped statuses column and the column status becomes hidden from the board is correct because removing a board column only changes the board mapping and does not delete issues or workflow statuses. The statuses that were mapped to the removed column become unmapped for that board and they appear in the board's unmapped area, while the board no longer shows a dedicated column for those statuses.

The number of issues in reports changes because deleting the column alters the counts is incorrect because deleting a column does not change the actual issues or their workflow statuses. Reporting that aggregates by status will still count those issues since their status values remain even if they are unmapped on the board.

You cannot remove a column while it still has at least one status mapped to it is incorrect because most board implementations allow a column to be removed and will simply unmap any statuses that were assigned to it. The platform does not block column deletion to force status reassignment.

Statuses associated with that column are deleted from the workflow is incorrect because removing a column from a board does not remove statuses from the underlying workflow. The statuses remain in the workflow configuration and can be remapped to other columns or reused elsewhere.

Some issues are permanently deleted from the project is incorrect because issues are not deleted when a column is removed. The issues remain in the project and retain their status values even when those statuses become unmapped on the board.

Full AWS Practitioner Certification Question