Explanation

Box 1: A check-in policy
Administrators of Team Foundation version control can add check-in policy requirements. These check-in policies require the user to take actions when they conduct a check-in to source control.
By default, the following check-in policy types are available:
Builds Requires that the last build was successful before a check-in.
Code Analysis Requires that code analysis is run before check-in.
Work Items Requires that one or more work items be associated with the check-in.
Box 2: Build policy
Reference:
https://docs.microsoft.com/en-us/azure/devops/repos/tfvc/add-check-policies
https://azuredevopslabs.com/labs/vstsextend/sonarcloud/

See the solution below in explanation
Explanation:
To ensure that the webhook at https://contoso.com/statushook is called every time the repository named az40038443478acr1 receives a new version of an image named dotnetapp, you can follow these steps to configure a webhook in Azure Container Registry:
Navigate to the Azure Container Registry:
Go to the Azure Portal.
Find and select your Azure Container Registry instance az40038443478acr1.
Create a New Webhook:
Under Services, select Webhooks.
Click on + Add to create a new webhook.
Fill in the form with the following information:
Webhook name: Enter a unique name for your webhook.
Service URI: Enter https://contoso.com/statushook.
Custom headers: (Optional) Add any headers you want to pass along with the POST request.
Trigger actions: Select Push to trigger the webhook on image push events.
Scope: Specify the scope as az40038443478acr1:dotnetapp to target the specific image.
Status: Set to Enabled.
Save the Webhook Configuration:
Review the information and click Create to save the webhook.
Once configured, the webhook will send a POST request to https://contoso.com/statushook whenever a new version of the dotnetapp image is pushed to the az40038443478acr1 repository in your Azure Container Registry1.
This setup will automate the notification process, ensuring that the specified webhook is called with each new image version, thus fulfilling the task requirements.

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-tmRouting method: GeographicResource 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-a

Explanation

Every request made against a storage service must be authorized, unless the request is for a blob or container resource that has been made available for public or signed access. One option for authorizing a request is by using Shared Key.
Scenario: The mobile applications must be able to call the share pricing service of the existing retirement fund management system. Until the system is upgraded, the service will only support basic authentication over HTTPS.
The investment planning applications suite will include one multi-tier web application and two iOS mobile application. One mobile application will be used by employees; the other will be used by customers.
References: https://docs.microsoft.com/en-us/rest/api/storageservices/authorize-with-shared-key