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

The debug output shows that the UbuntuServer address object successfully resolved an IP, while the webServer did not. The most likely cause is a mismatch in the dynamic address filter or missing tags on the target VM.

Verify the filter used for the dynamic firewall address – The filter category=windows may not match any VM metadata, resulting in no matched addresses.

Verify the tags on the target VM – Ensure that the VM has the correct tags (e.g., category=windows) that match the dynamic address filter to enable resolution.

Azure Virtual WAN is designed for large-scale, automated, and global branch connectivity, supporting hub-and-spoke architectures across multiple regions. It enables centralized routing, hub-to-hub connectivity, and integrates with VPN, ExpressRoute, and SD-WAN solutions, making it ideal for complex, multi-region deployments as shown in the diagram.

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.

Azure Firewall Premium includes advanced features not available in the Standard tier, such as enhanced URL filtering and web categories, TLS inspection, IDPS (intrusion detection and prevention system), and support for private certificate authorities. These enable more granular and secure traffic inspection and control.

The first and most direct diagnostic step is to verify the BGP peering status on both the FortiGate VM and Azure Route Server. If BGP peering is not established or is in an idle or down state, route propagation will fail. This check confirms whether the two systems are communicating and exchanging routes as expected.

In a FortiGate active-active HA deployment in Azure, synchronization between instances is achieved using:

FortiGate Clustering Protocol (FGCP) – This is the primary protocol used to synchronize configuration and session information between HA peers.

Heartbeat interfaces – These interfaces are specifically configured to exchange HA state and sync data between the FortiGate VMs, ensuring cluster consistency.

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.