Needs to be B to get windows specifically for IIS.

Conditional Access is a capability of Azure Active Directory. With Conditional Access, you can implement automated access control decisions for accessing your cloud apps that are based on conditions.

Conditional Access policies are enforced after the first-factor authentication has been completed.

Reference:

https://docs.microsoft.com/en-us/azure/active-directory/conditional-access/overview

GitHub Enterprise is the on-premises version of GitHub.com. GitHub Enterprise includes the same great set of features as GitHub.com but packaged for running on your organization's local network. All repository data is stored on machines that you control, and access is integrated with your organization's authentication system (LDAP, SAML, or CAS).

Reference:

https://www.azuredevopslabs.com/labs/azuredevops/yaml/

npm install will install both "dependencies" and "devDependencies"

npm install --production will only install "dependencies"

npm install --dev will only install "devDependencies"

A is the right answer. Blue/green and Red/Black are same. Must be 2 ['colored' paths] to swap immediately between them. Read the line "The strategy should also allow you to roll back in the shortest time required". So answer is A.

Scenarios and use cases for gates include:

- Quality validation. Query metrics from tests on the build artifacts such as pass rate or code coverage and deploy only if they are within required thresholds.

Use Quality Gates to integrate monitoring into your pre-deployment or post-deployment. This ensures that you are meeting the key health/performance metrics

(KPIs) as your applications move from dev to production and any differences in the infrastructure environment or scale is not negatively impacting your KPIs.

Note: Gates allow automatic collection of health signals from external services, and then promote the release when all the signals are successful at the same time or stop the deployment on timeout. Typically, gates are used in connection with incident management, problem management, change management, monitoring, and external approval systems.

Reference:

https://docs.microsoft.com/en-us/azure/azure-monitor/continuous-monitoring

https://docs.microsoft.com/en-us/azure/devops/pipelines/release/approvals/gates?view=azure-devops

When authoring an Azure Pipelines or TFS Release pipeline, you can specify the deployment targets for a job using a deployment group.

If the target machines are Azure VMs, you can quickly and easily prepare them by installing the Azure Pipelines Agent Azure VM extension on each of the VMs, or by using the Azure Resource Group Deployment task in your release pipeline to create a deployment group dynamically.

Reference:

https://docs.microsoft.com/en-us/azure/devops/pipelines/release/deployment-groups

You can use the combination of Terraform and Yeoman. Terraform is a tool for creating infrastructure on Azure. Yeoman makes it easy to create Terraform modules.

Terratest provides a collection of helper functions and patterns for common infrastructure testing tasks, like making HTTP requests and using SSH to access a specific virtual machine. The following list describes some of the major advantages of using Terratest:

- Convenient helpers to check infrastructure - This feature is useful when you want to verify your real infrastructure in the real environment.

- Organized folder structure - Your test cases are organized clearly and follow the standard Terraform module folder structure.

Test cases are written in Go - Many developers who use Terraform are Go developers. If you're a Go developer, you don't have to learn another programming language to use Terratest.

- Extensible infrastructure - You can extend additional functions on top of Terratest, including Azure-specific features.

Reference:

https://docs.microsoft.com/en-us/azure/developer/terraform/create-base-template-using-yeoman

https://docs.microsoft.com/en-us/azure/developer/terraform/test-modules-using-terratest

"Feed views enable developers to share a subset of package-versions with their consumers. A common use of feed views is to share package versions that have been tested and validated but hold back on packages that are still under development and/or didn't meet a certain quality bar"

https://docs.microsoft.com/en-us/azure/devops/artifacts/concepts/views?view=azure-devops

Views is the correct answer.