Explanation:

Scenario Recap
Fabric tenant with workspaces: Development, Test, QA, Production.
All workspaces are already in Premium Per User (PPU) mode (which is required for deployment pipelines).
Task: Set up a release pipeline to move through Dev # Test # QA # Production.
Step 1: Create a deployment pipeline
The first step is always to create a new deployment pipeline in the Fabric/Power BI service. This establishes the structure for Dev # Test # Prod (and optionally QA).
Step 2: Create the QA stage
By default, pipelines have 3 stages (Dev, Test, Prod).
Since we need a QA stage in addition, we must explicitly add it as a stage to the pipeline.
Step 3: Assign workspaces
Once the pipeline structure is ready (with QA included), we assign each workspace to the corresponding stage:
Development # Development
Test # Test
QA # QA
Production # Production
Why Not the Other Actions?
Move each workspace to Pro license mode # Incorrect, because deployment pipelines require Premium capacity or PPU, and the workspaces already are in PPU mode.
Create a deployment rule # Deployment rules (e.g., parameter or data source rules) are optional for environment-specific changes, but not part of the initial required setup sequence.
References
Deployment pipelines overview
Assigning workspaces to deployment pipelines