FCP_ZCS_AD-7.4 · Question #31
Refer to the exhibit. You are troubleshooting a network connectivity issue between two VMs that are deployed in Azure. One VM is a FortiGate that has one interface in the DMZ subnet, which is in the…
The correct answer is C. The firewall in the Windows VM is blocking the traffic. The FortiGate VM and the Windows Server VM are in different subnets but within the same Production virtual network, which means they can communicate by default unless restricted. Azure allows ICMP between subnets, but Windows VMs have ICMP blocked by default in their firewall…
Question
Refer to the exhibit. You are troubleshooting a network connectivity issue between two VMs that are deployed in Azure. One VM is a FortiGate that has one interface in the DMZ subnet, which is in the Production VNet. The other VM is a Windows Server in the Servers subnet, which is also in the Production VNet. You cannot ping the Windows Server from the FortiGate VM. What is the reason for this?
Exhibit
Options
- AYou have not created a VPN to allow traffic between those subnets
- BBy default, Azure does not allow ICMP traffic between subnets
- CThe firewall in the Windows VM is blocking the traffic
- DYou have not configured a user-defined route for this traffic
How the community answered
(52 responses)- A4% (2)
- B17% (9)
- C71% (37)
- D8% (4)
Explanation
The FortiGate VM and the Windows Server VM are in different subnets but within the same Production virtual network, which means they can communicate by default unless restricted. Azure allows ICMP between subnets, but Windows VMs have ICMP blocked by default in their firewall settings. Therefore, the likely reason for the ping failure is that the Windows Server's firewall is blocking ICMP (ping) traffic.
Topics
Community Discussion
No community discussion yet for this question.