Migrating .NET Core Web Application to Azure: Recommended Solution

Deploying the Web Application: Isolated App Service Plan on VNET1

Prev Question Next Question

Question

Note: This question is part of series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.

After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.

You are designing an Azure solution for a company that wants to move a .NET Core web application from an on-premises data center to Azure. The web application relies on a Microsoft SQL Server 2016 database on Windows Server 2016. The database server will not move to Azure.

A separate networking team is responsible for configuring network permissions.

The company uses Azure ExpressRoute and has an ExpressRoute gateway connected to an Azure virtual network named VNET1.

You need to recommend a solution for deploying the web application.

Solution: Deploy the web application to a web app hosted in an isolated App Service plan on VNET1.

Does this meet the goal?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B.

B

Instead, use VNet Integration.

Note: VNet Integration gives your web app access to resources in your virtual network. VNet Integration is often used to enable access from apps to a databases and web services running in your VNet.

https://docs.microsoft.com/en-us/azure/app-service/web-sites-integrate-with-vnet

The proposed solution of deploying the .NET Core web application to an isolated App Service plan on VNET1 would meet the stated goal of moving the application to Azure, while keeping the existing SQL Server 2016 database on Windows Server 2016 on-premises.

Here is a breakdown of the key points to consider:

  • Azure ExpressRoute: The fact that the company uses Azure ExpressRoute is relevant because it allows for a private, dedicated connection between the on-premises data center and Azure, which can help ensure security and performance for the application and database traffic.
  • ExpressRoute Gateway: The mention of an ExpressRoute gateway connected to VNET1 indicates that this virtual network is already set up and can be used for the application deployment.
  • .NET Core Web Application: The application runs on .NET Core, which is a cross-platform framework that can be deployed to Azure App Service, among other options.
  • Microsoft SQL Server 2016: The database that the application relies on is running on Windows Server 2016 in the on-premises data center, and will not be moved to Azure.
  • Separate Networking Team: It's worth noting that a separate team is responsible for configuring network permissions, which could impact the deployment and connectivity of the application.

With these considerations in mind, let's evaluate the proposed solution:

  • Deploy to an isolated App Service plan: An App Service plan is a hosting option for Azure App Service that provides dedicated resources for running web apps. The "isolated" tier provides additional security and isolation by running the web app in a dedicated Azure environment. This can be useful for scenarios where strict network isolation is required, such as when the application needs to connect to on-premises resources. By deploying the web application to an isolated App Service plan on VNET1, the application can leverage the private connectivity provided by Azure ExpressRoute and access the on-premises SQL Server 2016 database securely. This would meet the goal of moving the web application to Azure while keeping the database on-premises.

Overall, the proposed solution does meet the goal of moving the .NET Core web application to Azure while keeping the SQL Server 2016 database on-premises. Therefore, the answer to the question is A. Yes.

Prev Question Next Question