Exam AZ-400 topic 9 question 20 discussion

I’ll go for B (self hosted agent) becaute it allows to set a timeout of rule out any timeout issues due to the agent. As indicated in MS Documentation in the reference below: “To increase the max timeout for a job, you can opt for any of the following. Buy a Microsoft hosted agent which will give you 360 minutes for all jobs, irrespective of the repository used Use a self-hosted agent to rule out any timeout issues due to the agent” Ref: https://learn.microsoft.com/en-us/azure/devops/pipelines/troubleshooting/troubleshooting?view=azure-devops#job-time-out

The BUILD job is returning timeout error, not a few jobs, so no need for parallel jobs. We need self-hosted agent to be able to customize it to out needs.

Change the timeout settings in the agent job

as somebody else wrote in diff comment, if there is a doubt chose the purchase reply -> that's MS, they need to sell :)

A. Change the configuration of the build agent. you need to change the timeout setting as there is only one build jobs

I'm convinced

Agree with arr73. And there is only 1 job. So going for self hosted agent

All MS-Hosted (parallel) jobs will timeout at 360 minutes. Although this appears to be the least administrative effort, there's still a timeout of 360m. Having to go back after a second timeout of 360m, then deploy a self-hosted agent would be more effort. The only way to entirely eliminate the variable of timeout is to use a self-hosted agent.

For private projects there is one free Microsoft-hosted agent which can run jobs up to 60 minutes each time. You can pay for additional parallel jobs which have 360 minutes as the hard limit. https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops&tabs=yaml

Purchasing more parallel jobs allows you to leverage additional Microsoft-hosted agents within the same pool. This increases the available resources for your build job, potentially reducing queuing time and timeouts.

Minimize Administrative effort

Minimize administrative effort

This is very odd question, because none of the provided answers will solve the timeout problem with the job. The thing which could realy fix this is 'timeoutInMinutes' property of the job.

Purchase more

Ill go with D, because ist said "The solution must minimize administrative effort."