It is not possible for each squad to have its own separate velocity report when they use parallel sprints, Both company-managed projects and team-managed projects allow parallel sprints, and Users cannot finish more than one active sprint at the same time are correct.

It is not possible for each squad to have its own separate velocity report when they use parallel sprints is correct because velocity is calculated at the board level and it aggregates completed work across the active sprints on that board. When multiple squads run sprints in parallel against the same backlog the reporting context is shared so you will not get separate velocity charts per squad.

Both company-managed projects and team-managed projects allow parallel sprints is correct because the parallel sprints feature is supported for boards used by both project types in Jira Software Cloud. Both kinds of projects can host boards that run simultaneous sprints provided the feature is available for the site.

Users cannot finish more than one active sprint at the same time is correct because the product requires sprint completion to be done one sprint at a time. This prevents conflicting state changes and ensures unresolved issues are handled in a controlled manner when you complete each sprint.

When finishing an active sprint you can move unresolved issues into another active sprint is incorrect. When you complete a sprint the UI asks where unresolved issues should go and the common targets are the backlog or a future sprint, but moving them directly into another currently active sprint is not the standard completion flow.

Board level settings determine whether parallel sprints are available is incorrect. The availability of parallel sprints is governed at the product or site level and is not solely a per-board toggle, so boards may need the feature enabled globally before they can use it.

A project administrator can enable or disable parallel sprints for a company-managed project is incorrect. Enabling or disabling the feature is typically a Jira administration or site level action rather than something a project administrator can change for a single company-managed project.

Full AWS Practitioner Certification Question