Valid AZ-700 Dumps shared by ExamDiscuss.com for Helping Passing AZ-700 Exam! ExamDiscuss.com now offer the newest AZ-700 exam dumps, the ExamDiscuss.com AZ-700 exam questions have been updated and answers have been corrected get the newest ExamDiscuss.com AZ-700 dumps with Test Engine here:
You have an Azure virtual network named Vnet1. You need to ensure that the virtual machines in Vnet1 can access only the Azure SQL resources in the East US Azure region. The virtual machines must be prevented from accessing any Azure Storage resources. Which two outbound network security group (NSG) rules should you create? Each correct answer presents part of the solution. NOTE: Each correct selection is worth one point.
Recent Comments (The most recent comments are at the top.)
sam rocks - Apr 02, 2024
The correct answers are:
A. an allow rule that has the IP address range of Vnet1 as the source and destination of Sq1.EastUS D. a deny rule that has the IP address range of Vnet1 as the source and destination of Storage
Explanation:
A. This allow rule will permit the virtual machines in Vnet1 to access the Azure SQL resources in the East US region. The source and destination of the rule should be the IP address range of Vnet1, which will allow the VMs to communicate with the SQL resources.
D. This deny rule will prevent the virtual machines in Vnet1 from accessing any Azure Storage resources. The source and destination of the rule should be the IP address range of Vnet1, which will block the VMs from communicating with the Storage resources.
B. This deny rule is not necessary, as the default behavior of an NSG is to deny any traffic that is not explicitly allowed. There is no need to create a separate deny rule for the VirtualNetwork source and Sq1 destination.
C. This deny rule is not relevant to the given scenario, as it would block access to the 168.63.129.0/24 IP address range, which is used for internal Azure infrastructure purposes and not related to the requirement of restricting access to Azure Storage resources.
Therefore, the two outbound NSG rules that should be created are the allow rule for Vnet1 to Sq1.EastUS (A) and the deny rule for Vnet1 to Storage (D).
Recent Comments (The most recent comments are at the top.)
The correct answers are:
A. an allow rule that has the IP address range of Vnet1 as the source and destination of Sq1.EastUS
D. a deny rule that has the IP address range of Vnet1 as the source and destination of Storage
Explanation:
A. This allow rule will permit the virtual machines in Vnet1 to access the Azure SQL resources in the East US region. The source and destination of the rule should be the IP address range of Vnet1, which will allow the VMs to communicate with the SQL resources.
D. This deny rule will prevent the virtual machines in Vnet1 from accessing any Azure Storage resources. The source and destination of the rule should be the IP address range of Vnet1, which will block the VMs from communicating with the Storage resources.
B. This deny rule is not necessary, as the default behavior of an NSG is to deny any traffic that is not explicitly allowed. There is no need to create a separate deny rule for the VirtualNetwork source and Sq1 destination.
C. This deny rule is not relevant to the given scenario, as it would block access to the 168.63.129.0/24 IP address range, which is used for internal Azure infrastructure purposes and not related to the requirement of restricting access to Azure Storage resources.
Therefore, the two outbound NSG rules that should be created are the allow rule for Vnet1 to Sq1.EastUS (A) and the deny rule for Vnet1 to Storage (D).
Citations:
[1] https://learn.microsoft.com/en-us/sql/relational-databases/security/ledger/ledger-nsg-policies-configure?view=sql-server-ver16
[2] https://learn.microsoft.com/en-us/azure/azure-sql/database/vnet-service-endpoint-rule-overview?view=azuresql
[3] https://www.cloudbolt.io/azure-costs/azure-nsg/
[4] https://learn.microsoft.com/en-us/azure/virtual-network/network-security-group-how-it-works
[5] https://www.site24x7.com/learn/azure-network-security-groups.html...