FCP_ZCS_AD-7.4 FCP - Azure Cloud Security 7.4 Administrator Questions and Answers

Azure Route Server simplifies dynamic routing by allowing your FortiGate VMs to exchange BGP routes directly with Azure’s networking fabric. This eliminates the need to manually update route tables and enables seamless, centralized communication between on-premises branches and Azure resources through both VPN Gateway and ExpressRoute Gateway.

The Reverse Proxy mode is the most appropriate FortiWeb operation mode for this scenario. In this mode, FortiWeb sits between internet users and the Linux web servers, terminating client connections and then forwarding requests to the backend servers. This enables deep inspection, protection from web attacks (like SQL injection and XSS), and full WAF functionality, making it ideal for securing front-end web servers exposed to the internet.

Using FortiGate at both ends of a site-to-site IPsec VPN tunnel provides the advantage of applying consistent security policies, configurations, and management tools across both the on-premises and Azure environments. This simplifies policy enforcement, improves operational efficiency, and ensures uniform threat protection.

Since port 80 traffic is reaching the FortiGate (as shown in the sniffer output) but port 22 traffic is not, the issue lies before the FortiGate, at the Azure Load Balancer level. Azure Load Balancers require an Inbound NAT rule to forward specific ports (like SSH on port 22) to a specific backend VM. Creating a new Inbound NAT rule for port 22 will allow SSH traffic to be properly routed to the FortiGate VM.

In an active-active FortiGate cluster deployment in Azure, you must assign the public IP address to an Azure load balancer. This is required because Azure does not support multiple VMs sharing a single public IP directly. The Azure Load Balancer handles inbound traffic and distributes it to the active FortiGate instances.

Azure does not allow the deployment of virtual machines (VMs) in a gateway subnet. The gateway subnet is specifically reserved for Azure VPN Gateway or ExpressRoute Gateway instances, and deploying other resources in it can cause gateway deployment or operation failures.

For VMs in the 10.0.1.0/26 subnet to access the internet through the FortiGate VM, their default gateway must be changed to the internal IP address of the FortiGate’s NIC in that subnet (e.g., LAB1-FGT-A-Nic2). This ensures traffic is routed through FortiGate for inspection and NAT, rather than directly using Azure’s default system routes.