Queries, Epics, Projects, Assignees, and Stories are correct methods to create swimlanes on an organization-managed board in Jira.

Queries lets you define swimlanes using JQL or saved filters so that each lane contains issues that match a specific query. This is useful when you need custom grouping that does not map to a single built in field.

Epics creates lanes for each epic so you can see all issues grouped under their parent epic on the board. This is commonly used to visualize progress by epic across the team.

Projects allows lanes to represent different projects when a board aggregates work from multiple projects. This makes cross project boards easier to scan by project scope.

Assignees groups issues by the person assigned so each lane corresponds to an owner. This helps with workload visibility and handoff tracking.

Stories creates lanes based on parent stories so subtasks or related issues are visually grouped under their story. This is helpful for teams that track work primarily at the story level.

Components is incorrect because component is not offered as a swimlane option in the board layout for organization-managed boards. Components can be used in filters and reports but not as a built in swimlane type.

Issue types is incorrect because grouping by issue type is not a swimlane choice in the board layout for organization-managed boards. You can filter or quick filter by issue type instead of creating lanes for them.

Full AWS Practitioner Certification Question