An Azure Pipelines build occasionally experiences delays before the pipeline begins execution. Which action will reduce the time it takes for the build pipeline to start?

Enabling self-hosted build agents reduces pipeline start times because these agents are always running and available within your network. Unlike Microsoft-hosted agents, which need to be provisioned and spun up for each job (introducing potential delays), self-hosted agents are persistent. This eliminates the overhead associated with agent acquisition and initialization, leading to quicker pipeline starts. Creating a new agent pool only organizes agents; it doesn't inherently speed up their availability. Splitting the build pipeline into multiple stages might optimize execution after the pipeline starts but won't affect the initial queueing or agent provisioning time. Purchasing an additional parallel job allows more pipelines to run concurrently but doesn't decrease the startup time for any single pipeline.