SIMULATION - You need to configure a Microsoft SQL server named Web1234578 only to accept connections from the Subnet0 subnet on the VNET01 virtual network. To complete this task, sign in to the Azure portal.
Suggested Answer:See the explanation below.
You need to allow access to Azure services and configure a virtual network rule for the SQL Server. 1. In the Azure portal, type SQL Server in the search box, select SQL Server from the search results then select the server named web1234578. Alternatively, browse to SQL Server in the left navigation pane. 2. In the properties of the SQL Server, click Firewalls and virtual networks. 3. In the Virtual networks section, click on Add existing. This will open the Create/Update virtual network rule window. 4. Give the rule a name such as Allow_VNET01-Subnet0 (it doesn't matter what name you enter for the exam). 5. In the Virtual network box, select VNET01. 6. In the Subnet name box, select Subnet0. 7. Click the OK button to save the rule. 8. Back in the Firewall / Virtual Networks window, set the Allow access to Azure services option to On.
It is no longer up to date..
now it's in SQL SERVER > Networking > Add a virtual network rule
now it's in SQL SERVER > Networking > Add a virtual network rule
Steps.
1. Navigate to the Azure portal and locate the Web1234578 SQL server.
2. In the server's settings, go to the "Networking" section.
3. Under "Firewalls and virtual networks", select "Selected networks".
4. In the "Virtual networks" section, click "Add existing virtual network".
5. Select VNET01 from the list of virtual networks.
6. Choose Subnet0 from the list of subnets within VNET01.
7. Click "OK" to add the selected subnet.
8. Ensure that "Allow Azure services and resources to access this server" is set to "No" unless specifically required.
9. Remove any existing firewall rules that allow access from other IP ranges.
10. Click "Save" to apply the changes.
Also, guys, keep in mind that this setup alone without also setting the Microsoft.SQL Service Endpoint on the Subnet of the VNET will not successfully communicate with the SQL server- in case it's possible to do or to check on the SIM, it's an important piece of the communication config to set up the SQL Service Endpoint.
The private endpoint goal is to give the SQL Server (whish is a PaaS) a place and an identity into a VNET (IAAS), hence integrating the SQL resource to be accessible within that VNET/subnet where you plant it but also form wherever else from your environment as long as there is network connectivity to the Private Endpoint of the SQL PaaS service.
For this exercise purpose, the goal is to only have that specific VNET/Subnet be able to connect to the SQL Server and not make it fully available to the IaaS private network environment.
Answer is outdated. Current answer is SQL Server>Security>Networking. By default public access is disabled. Change radio button to "Selected Networks" and add Vnet
1. SQL Server
2. Under Security Select Networking
3. Under Public Access Tab, you will see Virtual Networks below
4. Click the + on "add a virtual network rule"
5. Enter the data.
upvoted 3 times
...
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
ylfr
Highly Voted 1 year, 10 months agosomboy
1 year, 9 months agoITFranz
Most Recent 2 days agocris_exam
6 months, 3 weeks agomachado
1 year, 4 months agocris_exam
6 months, 3 weeks agoMacke53
1 year, 4 months agoF117A_Stealth
1 year, 9 months ago