Azure Artifacts introduces the concept of multiple feeds that you can use to organize and control access to your packages.
Packages you host in Azure Artifacts are stored in a feed. Setting permissions on the feed allows you to share your packages with as many or as few people as your scenario requires.
Feeds have four levels of access: Owners, Contributors, Collaborators, and Readers.
References: https://docs.microsoft.com/en-us/azure/devops/artifacts/feeds/feed-permissions?
view=vsts&tabs=new-nav

Smart Detection automatically warns you of potential performance problems and failure anomalies in your web application. It performs proactive analysis of the telemetry that your app sends to Application Insights. If there is a sudden rise in failure rates, or abnormal patterns in client or server performance, you get an alert.
Reference:
https://docs.microsoft.com/en-us/azure/azure-monitor/app/proactive-diagnostics

The Feature Manager in the Azure portal for App Configuration provides a UI for creating and managing the feature flags that you use in your applications.
App Configuration offers the following benefits:
A fully managed service that can be set up in minutes
Flexible key representations and mappings
Tagging with labels
Point-in-time replay of settings
Dedicated UI for feature flag management
Comparison of two sets of configurations on custom-defined dimensions
Enhanced security through Azure-managed identities
Encryption of sensitive information at rest and in transit
Native integration with popular frameworks
App Configuration complements Azure Key Vault, which is used to store application secrets.
Reference:
https://docs.microsoft.com/en-us/azure/azure-app-configuration/overview

Explanation:

The process to associate an automated test with a test case is:
* Create a test project containing your automated test. What types of tests are supported?
* Check your test project into an Azure DevOps or Team Foundation Server (TFS) repository.
* Create a build pipeline for your project, ensuring that it contains the automated test. What are the differences if I am still using a XAML build?
* Use Visual Studio Enterprise or Professional 2017 or a later version to associate the automated test with a test case as shown below. The test case must have been added to a test plan that uses the build you just defined.
Reference:
https://docs.microsoft.com/en-us/azure/devops/test/associate-automated-test-with-test-case

Explanation: