Unattended config:
The agent can be set up from a script with no human intervention. You must pass --unattended and the answers to all questions.
To configure an agent, it must know the URL to your organization or collection and credentials of someone authorized to set up agents. All other responses are optional.
Reference:
https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/v2-windows Overview
Topic 3, Woodgrove bank
General Overview
Woodgrove Bank is a financial services company that has a main office in the United Kingdom.
Technical Requirements and Planned Changes
Planned Changes
Woodgrove Bank plans to implement the following project management changes:
Implement Azure DevOps for project tracking.
Centralize source code control in private GitHub repositories.
Implement Azure Pipelines for build pipelines and release pipelines.
Woodgrove Bank plans to implement the following changes to the identity environment:
Deploy an Azure AD tenant named woodgrovebank.com.
Sync the Active Directory domain to Azure AD.
Configure App1 to use a service principal.
Integrate GitHub with Azure AD.
Woodgrove Bank plans to implement the following changes to the core apps:
Migrate App1 to ASP.NET Core.
Integrate Azure Pipelines and the third-party build tool used to develop App2.
Woodgrove Bank plans to implement the following changes to the DevOps environment:
Deploy App1 to Azure App Service.
Implement source control for the DB1 schema.
Migrate all the source code from TFS1 to GitHub.
Deploy App2 to an Azure virtual machine named VM1.
Merge the POC branch into the GitHub default branch.
Implement an Azure DevOps dashboard for stakeholders to monitor development progress.
Technical Requirements
Woodgrove Bank identifies the following technical requirements:
The initial databases for new environments must contain both schema and reference data.
An Azure Monitor alert for VM1 must be configured to meet the following requirements:
Be triggered when average CPU usage exceeds 80 percent for 15 minutes.
Calculate CPU usage averages once every minute.
The commit history of the POC branch must replace the history of the default branch.
The Azure DevOps dashboard must display the metrics shown in the following table.

Access to Azure DevOps must be restricted to specific IP addresses.
Page load times for App1 must be captured and monitored.
Administrative effort must be minimized.

Explanation

Box 1: Upgrade TFS to the most recent RTM release.
One of the major prerequisites for migrating your Team Foundation Server database is to get your database schema version as close as possible to what is currently deployed in Azure Devops Services.
Box 2: Use the TFS Database Import Service
In Phase 3 of your migration project, you will work on upgrading your Team Foundation Server to one of the supported versions for the Database Import Service in Azure Devops Services.
References: Team Foundation Server to Azure Devops Services Migration Guide

Explanation:

Box 1: every five minutes at a random location
Test frequency: Sets how often the test is run from each test location. With a default frequency of five minutes and five test locations, your site is tested on average every minute.
Box 2:
Parse dependent requests: Test requests images, scripts, style files, and other files that are part of the web page under test. The recorded response time includes the time taken to get these files. The test fails if any of these resources cannot be successfully downloaded within the timeout for the whole test.
Reference:
https://docs.microsoft.com/en-us/azure/azure-monitor/app/monitor-web-app-availability

Reference:
https://devblogs.microsoft.com/premier-developer/alerts-based-on-analytics-query-using-custom-log-search/