You have an Azure pipeline that is used to build and deploy an app named App1. The build job uses a Microsoft-hosted Windows agent. The build job for App1 intermittently returns a timeout error. You n

Question

Options

• AChange the configuration of the build agent.
• BDeploy a self-hosted agent.
• CChange to a Microsoft-hosted Linux agent.
• DPurchase more parallel jobs.

• A
  7% (2)
• B
  73% (22)
• C
  3% (1)
• D
  17% (5)

Explanation

Explanation

Deploying a self-hosted agent (Option B) is correct because it gives you full control over the build environment's resources, timeout settings, and configuration - allowing you to extend job timeout limits and optimize performance to resolve intermittent timeout errors with minimal ongoing administrative overhead once set up.

• Option A is wrong because Microsoft-hosted agents are managed by Microsoft, and you cannot directly change their configuration (e.g., timeout limits or hardware specs); that control is not available to you.
• Option C is wrong because simply switching to a Linux agent does not address the root cause of the timeout - it changes the OS, not the underlying resource constraints or timeout behavior.
• Option D is wrong because purchasing more parallel jobs increases the number of concurrent builds, not the duration or performance of an individual build job - it won't fix a timeout issue.

Memory Tip: Think of it this way - "self-hosted = self-controlled." When Microsoft's hosted agents don't give you enough control to fix a problem, a self-hosted agent lets you own the environment and tune it to your needs. If you can't change it, host it yourself.

No community discussion yet for this question.