Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Fortinet Exam NSE7_PBC-7.2 Topic 1 Question 7 Discussion

Actual exam question for Fortinet's NSE7_PBC-7.2 exam
Question #: 7
Topic #: 1
[All NSE7_PBC-7.2 Questions]

You have been tasked with deploying FortiGate VMs in a highly available topology on the Amazon Web Services (AWS) cloud. The requirements for your deployment are as follows:

* You must deploy two FortiGate VMs in a single virtual private cloud (VPC), with an external elastic load balancer which will distribute ingress traffic from the internet to both FortiGate VMs in an active-active topology.

* Each FortiGate VM must have two elastic network interfaces: one will connect to a public subnet and other will connect to a private subnet.

* To maintain high availability, you must deploy the FortiGate VMs in two different availability zones.

How many public and private subnets will you need to configure within the VPC?

Show Suggested Answer Hide Answer

Contribute your Thoughts:

Viva
8 months ago
Yup, that sounds about right. This is a pretty classic high availability setup on AWS. As long as you configure the routing and security groups properly, you should be good to go.
upvoted 0 times
...
Annmarie
8 months ago
Ah, good point! So that would make it a total of 4 public subnets and 4 private subnets. One public and one private subnet per availability zone, plus an additional pair for the load balancer.
upvoted 0 times
...
Cassi
8 months ago
I agree with that. But we also need to consider the active-active topology requirement. Wouldn't we need an additional public subnet and private subnet to handle the load balancing?
upvoted 0 times
...
Aracelis
8 months ago
Hmm, this seems like a straightforward question. Since we need to deploy the FortiGate VMs in two different availability zones, that means we'll need at least two public subnets and two private subnets, right?
upvoted 0 times
Louisa
7 months ago
Overall, this setup provides redundancy and scalability for the deployment of FortiGate VMs in the AWS cloud.
upvoted 0 times
...
Dannette
7 months ago
The configuration will ensure that even if one availability zone goes down, the other FortiGate VM will continue to handle traffic.
upvoted 0 times
...
Alease
8 months ago
Having the FortiGate VMs in separate availability zones also helps in disaster recovery scenarios.
upvoted 0 times
...
Oliva
8 months ago
By deploying the FortiGate VMs in two different availability zones, we ensure high availability for the deployment.
upvoted 0 times
...
Tammara
8 months ago
The external elastic load balancer will distribute ingress traffic from the internet to both FortiGate VMs in an active-active topology.
upvoted 0 times
...
Ronna
8 months ago
Each FortiGate VM will have one elastic network interface connecting to the public subnet and another connecting to the private subnet.
upvoted 0 times
...
Carma
8 months ago
Yes, that's correct. We will need two public subnets and two private subnets for the deployment.
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77