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 a Standard App Service plan. Create and configure an Azure App Service Hybrid Connections endpoint.
On the on-premises network, deploy the Hybrid Connection Manager. Configure the Hybrid Connection Manager to access both the Hybrid Connection endpoint and the SQL Server instance.
Does this meet the goal?
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-vnetYes, the proposed solution meets the goal of migrating the .NET Core web application from an on-premises data center to Azure, while also keeping the SQL Server instance on-premises.
Here is a detailed explanation of the proposed solution:
Deploy the web application to a web app hosted in a Standard App Service plan: Azure App Service is a fully managed platform for building, deploying, and scaling web apps. By deploying the web application to an Azure App Service plan, the company can benefit from the scalability and high availability of the platform. A Standard App Service plan provides the necessary resources and features to host the web application, including support for custom domains, SSL certificates, and scaling options.
Create and configure an Azure App Service Hybrid Connections endpoint: Azure App Service Hybrid Connections allows the web app hosted in Azure to access resources on-premises or in other virtual networks without requiring any changes to the network infrastructure. By creating a Hybrid Connections endpoint, the company can establish a secure and reliable connection between the web app and the SQL Server instance running on Windows Server 2016.
On the on-premises network, deploy the Hybrid Connection Manager: The Hybrid Connection Manager is a lightweight agent that runs on the on-premises network and acts as a bridge between the web app in Azure and the SQL Server instance. By deploying the Hybrid Connection Manager, the company can enable the web app to access the SQL Server instance securely and without exposing it to the public internet.
Configure the Hybrid Connection Manager to access both the Hybrid Connection endpoint and the SQL Server instance: Once the Hybrid Connection Manager is deployed, it needs to be configured to access both the Hybrid Connection endpoint created in Azure and the SQL Server instance running on Windows Server 2016. By configuring the Hybrid Connection Manager, the company can ensure that the web app can communicate with the SQL Server instance and retrieve the necessary data.
Overall, the proposed solution leverages Azure App Service and Azure App Service Hybrid Connections to securely and reliably deploy the .NET Core web application in Azure while also keeping the SQL Server instance on-premises. The Hybrid Connection Manager acts as a bridge between the two environments, allowing the web app to access the SQL Server instance securely and without exposing it to the public internet.