See solution below.
Explanation:
1.Go to the Azure portal, navigate to Traffic Manager profiles and click on the Add button to create a routing profile.

2. In the Create Traffic Manager profile, enter, or select these settings:
Name: az40011566895n1-tm
Routing method: Geographic
Resource group: RG1lod11566895
Note: Traffic Manager profiles can be configured to use the Geographic routing method so that users are directed to specific endpoints (Azure, External or Nested) based on which geographic location their DNS query originates from. This empowers Traffic Manager customers to enable scenarios where knowing a user's geographic region and routing them based on that is important.
Reference:
https://azure.microsoft.com/en-us/blog/announcing-the-general-availability-of-geographic-routing-capability- in-azure-traffic-manager/

The Azure Pipelines pool provides all Azure DevOps organizations with cloud-hosted build agents and free build minutes each month. If you need more Microsoft-hosted build resources, or need to run more jobs in parallel, then you can either:
Host your own agents on infrastructure that you manage.
Buy additional parallel jobs.
Reference:
https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/pools-queues

See explanation below
Explanation:
Task 7: Create a Pipeline to Deploy a Docker Image in a New Branch
Step 1: Create a New Branch
* In your Azure DevOps Project (Project1), navigate to Repos.
* In the left menu, click on Branches.
* Click New branch.
* Enter:
* Branch name: azure-pipelines
* Based on: main (or your default branch)
* Click Create.
This creates a new branch named azure-pipelines.
Step 2: Switch to the New Branch
* In Repos, click on Files.
* In the top-left branch selector, choose azure-pipelines.
Step 3: Use the Predefined Docker Pipeline Template
Azure Pipelines has predefined YAML templates for common tasks, including Docker.
Here's how to add it:
* In the azure-pipelines branch, click New file.
* Name the file: azure-pipelines.yml.
* Click the Show templates button in the YAML editor (if available).
* Search for the Docker template in the list of predefined templates.
* Select the Docker template to auto-populate the YAML file.
If the editor doesn't show the template picker, you can manually add the following basic Docker pipeline template:
yaml
Copy
# Predefined Docker pipeline template
trigger:
- main
resources:
- repo: self
variables:
imageName: 'mydockerimage'
stages:
- stage: Build
displayName: Build and push stage
jobs:
- job: Build
pool:
vmImage: 'ubuntu-latest'
steps:
- task: Docker@2
displayName: Build and push an image to container registry
inputs:
command: buildAndPush
repository: $(imageName)
dockerfile: '**/Dockerfile'
containerRegistry: '<your-container-registry-service-connection>'
tags: |
latest
Replace <your-container-registry-service-connection> with your actual Azure Container Registry (ACR) or DockerHub service connection name.
Step 4: Commit the Pipeline to the New Branch
* In the YAML editor, review and adjust if needed (like setting the correct container registry service connection).
* In the bottom commit message box:
* Message: e.g., Add Docker deployment pipeline
* Ensure the branch is set to azure-pipelines.
* Click Commit (not commit to main).
This creates the pipeline YAML file in the new azure-pipelines branch.
Step 5: Create the Pipeline in Azure DevOps
* In the left menu, click Pipelines.
* Click New pipeline.
* Choose:
* Azure Repos Git.
* Select your repo.
* Select Existing Azure Pipelines YAML file.
* In the branch selector, choose the azure-pipelines branch.
* Select the YAML file path (azure-pipelines.yml).
* Click Continue and then Run to validate the pipeline.

Explanation:

Box 1: Azure Pipelines service connection
Box 2: Managed Service Identity Authentication
The managed identities for Azure resources feature in Azure Active Directory (Azure AD) provides Azure serviceswith an automatically managed identity in Azure AD. You can use the identity to authenticate to any service that supports Azure AD authentication, including Key Vault, without any credentials in your code.
Reference:
https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/deploy/azure-key-vault
https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/overview

The first thing to do is to declare your SonarQube server as a service endpoint in your VSTS/DevOps project settings.
References: https://docs.sonarqube.org/display/SCAN/Analyzing+with+SonarQube+Extension+for+vsts-TFS