Resolving an Intermittent Microsoft-Hosted Agent Timeout on an App1 Build Job

Why the Answer Is Correct

The build job times out intermittently on a Microsoft-hosted Windows agent, and the documented reason is the per-job execution ceiling on Microsoft-hosted parallel jobs: the free allowance caps jobs at 60 minutes each, whereas paid Microsoft-hosted parallel jobs raise the hard limit to 360 minutes. Because the requirement is to minimize administrative effort, purchasing additional parallel jobs is a configuration change that removes the ceiling immediately and requires no infrastructure to build or maintain. The vote was 57 for D and 33 for B. freddyneen gave the clearest statement of the two tiers, noting that a private project gets one free Microsoft-hosted agent running jobs up to 60 minutes, and that paying for additional parallel jobs yields the 360-minute hard limit, and cited the hosted agents documentation directly.

Why the Other Options Are Wrong

Deploying a self-hosted agent (B) is the option the community runner-up chose, and arr73's reasoning is technically sound since a self-hosted agent does let you set a longer timeout and rules out agent-side timeouts. It loses on the stated constraint, though, because a self-hosted agent is infrastructure you must provision, secure, patch, and maintain, which is the opposite of minimizing administrative effort. Changing to a Microsoft-hosted Linux agent (C) does not raise the ceiling either, since the timeout limit applies to Microsoft-hosted parallel jobs regardless of the agent operating system, so the intermittent timeout would persist. Changing the configuration of the build agent (A) is likewise ineffective, because the agent configuration is not what determines the job execution limit; the limit comes from the hosted agent tier the job runs under.

Community Comment Notes

The community split 57 for D and 33 for B, and the disagreement is about which lever the question wants. arr73, the highest-liked commenter, chose B and quoted the documentation line about increasing the max timeout, which lists buying a Microsoft-hosted agent and using a self-hosted agent as the two options, and UrbanRellik added the sharpest practical argument for B, noting that even 360 minutes is still a ceiling, so going self-hosted is the only way to remove the timeout variable entirely. d526b99, AnishGS, and hotspot02103 argued the opposite way for D, with AnishGS pointing at the minimize administrative effort wording and hotspot02103 noting the exam's own bias toward the purchase option. djhyfdgjk made a technically correct objection that the real fix is the timeoutInMinutes job property, which no option offers, so the question is imperfect; within the given choices, D is the lowest-effort answer.