When you deploy a single FortiGate VM using the available template from the Azure Marketplace, several other resources are also created. Which two…

When deploying a single FortiGate-VM from the Azure Marketplace using the standard template,

the process provisions several core resources to establish a functional firewall. The template is

designed to create a FortiGate instance with separate interfaces for external (public) and internal

(private) traffic. By default, this includes two virtual network interfaces (vNICs). To secure these

interfaces at the Azure level, a Network Security Group (NSG) is created and associated with

each vNIC to filter inbound and outbound traffic to the FortiGate itself.

C. One VM Scale set: A VM Scale Set is used for deploying and managing a set of auto-scaling

virtual machines for high availability, not for a single VM deployment.

D. One new route table: A route table is configured after deployment to direct traffic from

protected subnets through the FortiGate. It is not created by the single FortiGate VM template

itself.

1. Fortinet Document Library, FortiGate-VM on Microsoft Azure 7.4.1 Deployment Guide, Page

16: "The FortiGate is deployed with two network interfaces (port1 and port2) by default... A

network security group is created for each interface." This directly confirms that two vNICs and an

NSG for each are created.

URL: https://docs.fortinet.com/document/fortigate-public-cloud/7.4.1/azure-deployment-guide/121

13/deploying-fortigate-vm-from-the-azure-marketplace

2. Fortinet Document Library, FortiGate-VM on Microsoft Azure 7.4.1 Deployment Guide, Page

23: The guide provides instructions for manually creating a route table and associating it with a

subnet as a separate, post-deployment step, confirming it is not part of the initial template

creation for a single VM.

URL: https://docs.fortinet.com/document/fortigate-public-cloud/7.4.1/azure-deployment-guide/555

299/configuring-the-route-table-for-the-protected-subnet