Question #1
Refer to the exhibit.
An organization deployed the application servers in the AWS VPC that connects to the corporate data center using Transit Gateway Connect. Demand for the applications has grown and the connection requires more bandwidth.
What is required to achieve higher bandwidth?
- A . Use routable public IP addresses instead of private IP addresses for connectivity.
- B . You cannot increase bandwidth the connection has a fixed limit.
- C . No configuration change is required because GRE tunnels are scaled to provide higher bandwidth.
- D . You add a Transit VPC between the organization’s VPCs.
Correct Answer: C
C
Explanation:
Understanding Transit Gateway Connect:
Transit Gateway Connect is a feature of AWS Transit Gateway that simplifies the integration of SD-WAN networks with AWS. It uses Generic Routing Encapsulation (GRE) tunnels to facilitate this connection.
GRE Tunnels and Bandwidth:
GRE tunnels can dynamically scale to meet increasing bandwidth demands. They allow multiple tunnels between the same endpoints, which can aggregate bandwidth without requiring additional configuration.
Scaling Bandwidth with GRE:
The GRE protocol used by Transit Gateway Connect can support high bandwidth requirements by
spreading traffic across multiple tunnels. As demand grows, additional tunnels can be automatically
used to handle the increased traffic load.
Comparison with Other Options:
Option A suggests using public IP addresses, which is not relevant to bandwidth scaling.
Option B is incorrect because bandwidth can be increased through GRE scaling.
Option D suggests adding a Transit VPC, which is unnecessary for increasing bandwidth when using
Transit Gateway Connect.
Reference: AWS Transit Gateway Documentation: AWS Transit Gateway
GRE Tunnels and AWS: AWS GRE Tunnels
C
Explanation:
Understanding Transit Gateway Connect:
Transit Gateway Connect is a feature of AWS Transit Gateway that simplifies the integration of SD-WAN networks with AWS. It uses Generic Routing Encapsulation (GRE) tunnels to facilitate this connection.
GRE Tunnels and Bandwidth:
GRE tunnels can dynamically scale to meet increasing bandwidth demands. They allow multiple tunnels between the same endpoints, which can aggregate bandwidth without requiring additional configuration.
Scaling Bandwidth with GRE:
The GRE protocol used by Transit Gateway Connect can support high bandwidth requirements by
spreading traffic across multiple tunnels. As demand grows, additional tunnels can be automatically
used to handle the increased traffic load.
Comparison with Other Options:
Option A suggests using public IP addresses, which is not relevant to bandwidth scaling.
Option B is incorrect because bandwidth can be increased through GRE scaling.
Option D suggests adding a Transit VPC, which is unnecessary for increasing bandwidth when using
Transit Gateway Connect.
Reference: AWS Transit Gateway Documentation: AWS Transit Gateway
GRE Tunnels and AWS: AWS GRE Tunnels
Question #2
You want to deploy the Fortinet HA CloudFormation template to stage and bootstrap the FortiGate configuration in the same region in which you created your VPC, which is Ohio US-East-2.
Based on this information, which statement is correct?
- A . You create an S3 bucket to stage and bootstrap FortiGate with an FGCP unicast configuration. The S3 bucket can be hosted in any region.
- B . The Fortinet HA cloud formation template automatically creates an S3 bucket.
- C . You create an S3 bucket to stage and bootstrap FortiGate with an FGCP unicast configuration. The S3 bucket needs to be hosted in the Ohio US-East-2 region.
- D . You create a DynamoDB to stage and bootstrap FortiGate with an FGCP unicast configuration. It needs to be hosted in the Ohio US-East-2 region.
Correct Answer: C
C
Explanation:
Understanding Fortinet HA CloudFormation Template:
The Fortinet High Availability (HA) CloudFormation template is used to automate the deployment
and configuration of FortiGate instances in AWS.
Staging and Bootstrapping FortiGate:
Staging involves preparing the necessary configuration files and resources needed for deployment.
Bootstrapping is the process of automatically configuring FortiGate instances upon deployment.
S3 Bucket Requirement:
The configuration files required for staging and bootstrapping are typically stored in an S3 bucket.
Since the deployment is in the Ohio (US-East-2) region, it is recommended to host the S3 bucket in the same region to minimize latency and ensure regional compliance.
Comparison with Other Options:
Option A is incorrect because while an S3 bucket is required, it should be in the same region (US-East-2).
Option B is incorrect as the template does not automatically create the S3 bucket.
Option D is incorrect as DynamoDB is not used for staging and bootstrapping in this scenario.
Reference: Fortinet Documentation: FortiGate on AWS
AWS S3 Documentation: AWS S3
C
Explanation:
Understanding Fortinet HA CloudFormation Template:
The Fortinet High Availability (HA) CloudFormation template is used to automate the deployment
and configuration of FortiGate instances in AWS.
Staging and Bootstrapping FortiGate:
Staging involves preparing the necessary configuration files and resources needed for deployment.
Bootstrapping is the process of automatically configuring FortiGate instances upon deployment.
S3 Bucket Requirement:
The configuration files required for staging and bootstrapping are typically stored in an S3 bucket.
Since the deployment is in the Ohio (US-East-2) region, it is recommended to host the S3 bucket in the same region to minimize latency and ensure regional compliance.
Comparison with Other Options:
Option A is incorrect because while an S3 bucket is required, it should be in the same region (US-East-2).
Option B is incorrect as the template does not automatically create the S3 bucket.
Option D is incorrect as DynamoDB is not used for staging and bootstrapping in this scenario.
Reference: Fortinet Documentation: FortiGate on AWS
AWS S3 Documentation: AWS S3
Question #3
An organization has the requirement to connect a data VPC to the on-premises infrastructure of a branch office in a hybrid cloud environment. The connectivity needs the higher bandwidth but the organization does not want to use multiple connections between sites.
Which AWS solution meets the requirement?
- A . Transit VPC with IPSec
- B . Internet Gateway
- C . Transit Gateway multicast
- D . Transit Gateway Connect
Correct Answer: D
D
Explanation:
Understanding the Requirement:
The organization needs to connect a data VPC to the on-premises infrastructure with high bandwidth.
The solution should avoid multiple connections between sites.
Transit Gateway Connect:
Transit Gateway Connect is designed to integrate with SD-WAN networks and provides scalable bandwidth using GRE tunnels.
It simplifies hybrid cloud connectivity by allowing high bandwidth connections without the need for
multiple physical connections.
Benefits of Transit Gateway Connect:
Supports scalable bandwidth through GRE tunnels.
Facilitates seamless integration with on-premises and cloud environments. Reduces complexity by avoiding the need for multiple VPN connections. Comparison with Other Options:
Option A (Transit VPC with IPSec) is not preferred due to complexity and potential limitations in bandwidth scalability.
Option B (Internet Gateway) is not suitable for private, high-bandwidth connections.
Option C (Transit Gateway multicast) does not address the requirement for high bandwidth in a
hybrid cloud setup.
Reference: AWS Transit Gateway Documentation: AWS Transit Gateway Connect
Hybrid Cloud Connectivity: AWS Hybrid Cloud
D
Explanation:
Understanding the Requirement:
The organization needs to connect a data VPC to the on-premises infrastructure with high bandwidth.
The solution should avoid multiple connections between sites.
Transit Gateway Connect:
Transit Gateway Connect is designed to integrate with SD-WAN networks and provides scalable bandwidth using GRE tunnels.
It simplifies hybrid cloud connectivity by allowing high bandwidth connections without the need for
multiple physical connections.
Benefits of Transit Gateway Connect:
Supports scalable bandwidth through GRE tunnels.
Facilitates seamless integration with on-premises and cloud environments. Reduces complexity by avoiding the need for multiple VPN connections. Comparison with Other Options:
Option A (Transit VPC with IPSec) is not preferred due to complexity and potential limitations in bandwidth scalability.
Option B (Internet Gateway) is not suitable for private, high-bandwidth connections.
Option C (Transit Gateway multicast) does not address the requirement for high bandwidth in a
hybrid cloud setup.
Reference: AWS Transit Gateway Documentation: AWS Transit Gateway Connect
Hybrid Cloud Connectivity: AWS Hybrid Cloud
Question #4
Refer to the exhibit.
Traffic is initiated from the EC2 instance and is destined for the internet.
Which traffic flow is correct?
- A . EC2 instance > NAT GW > IGW > internet
- B . There is no route to the internet in the Private Route Table. The traffic does not reach the internet.
- C . EC2 instance > GWLBe > NAT GW > IGW > internet
- D . EC2 instance > GWLBe > internet
Correct Answer: C
C
Explanation:
Understanding the Architecture:
The architecture includes an EC2 instance in a private subnet, a Gateway Load Balancer Endpoint (GWLBe), a NAT Gateway (NAT GW), and an Internet Gateway (IGW). Route Tables and Routing:
The private route table for the subnet containing the EC2 instance has a route pointing to the GWLBe for internet-bound traffic.
The public route table for the subnet containing the NAT Gateway has routes to the IGW.
Traffic Flow Analysis:
Traffic initiated from the EC2 instance destined for the internet will first be routed to the GWLBe as per the private route table.
The GWLBe will forward the traffic to the NAT Gateway.
The NAT Gateway will then route the traffic to the IGW, which finally sends the traffic to the internet.
Comparison with Other Options:
Option A suggests direct routing to the NAT GW from the EC2 instance, which is incorrect. Option B incorrectly states there is no route to the internet in the private route table. Option D suggests direct routing from GWLBe to the internet, which is not the case.
Reference: AWS Documentation on Route Tables: AWS Route Tables
Gateway Load Balancer Overview: AWS Gateway Load Balancer
C
Explanation:
Understanding the Architecture:
The architecture includes an EC2 instance in a private subnet, a Gateway Load Balancer Endpoint (GWLBe), a NAT Gateway (NAT GW), and an Internet Gateway (IGW). Route Tables and Routing:
The private route table for the subnet containing the EC2 instance has a route pointing to the GWLBe for internet-bound traffic.
The public route table for the subnet containing the NAT Gateway has routes to the IGW.
Traffic Flow Analysis:
Traffic initiated from the EC2 instance destined for the internet will first be routed to the GWLBe as per the private route table.
The GWLBe will forward the traffic to the NAT Gateway.
The NAT Gateway will then route the traffic to the IGW, which finally sends the traffic to the internet.
Comparison with Other Options:
Option A suggests direct routing to the NAT GW from the EC2 instance, which is incorrect. Option B incorrectly states there is no route to the internet in the private route table. Option D suggests direct routing from GWLBe to the internet, which is not the case.
Reference: AWS Documentation on Route Tables: AWS Route Tables
Gateway Load Balancer Overview: AWS Gateway Load Balancer
Question #5
A customer has implemented GWLB between the partner and application VPCs. FortiGate appliances are deployed in the partner VPC with multiple AZs to inspect traffic transparently.
Which two things will happen to application traffic based on the GWLB deployment? (Choose two.)
- A . Inbound and outbound traffic will go to multiple devices, which will perform load balancing.
- B . Inbound and outbound traffic will go to the same device, which will perform stateful processing.
- C . The content of the original traffic exchanged between the GWLB and FortiGate will be preserved.
- D . The original traffic exchanged between the GWLB and FortiGate will be hashed for data integrity.
Correct Answer: A, B
A, B
Explanation:
Understanding Gateway Load Balancer (GWLB):
GWLB is designed to distribute traffic across multiple appliances for both inbound and outbound traffic, providing scalability and high availability.
Traffic Load Balancing:
GWLB can send traffic to multiple FortiGate appliances for load balancing purposes, ensuring efficient use of resources (Option A).
Stateful Processing:
For stateful processing, GWLB ensures that traffic flows (both inbound and outbound) for a given connection are directed to the same FortiGate appliance. This maintains session integrity (Option B). Preservation and Hashing of Traffic:
Options C and D are incorrect as they suggest incorrect behavior regarding traffic content preservation and hashing for data integrity, which are not primary functions of GWLB.
Reference: AWS Gateway Load Balancer Documentation: AWS Gateway Load Balancer
FortiGate Integration with GWLB: Fortinet Documentation
A, B
Explanation:
Understanding Gateway Load Balancer (GWLB):
GWLB is designed to distribute traffic across multiple appliances for both inbound and outbound traffic, providing scalability and high availability.
Traffic Load Balancing:
GWLB can send traffic to multiple FortiGate appliances for load balancing purposes, ensuring efficient use of resources (Option A).
Stateful Processing:
For stateful processing, GWLB ensures that traffic flows (both inbound and outbound) for a given connection are directed to the same FortiGate appliance. This maintains session integrity (Option B). Preservation and Hashing of Traffic:
Options C and D are incorrect as they suggest incorrect behavior regarding traffic content preservation and hashing for data integrity, which are not primary functions of GWLB.
Reference: AWS Gateway Load Balancer Documentation: AWS Gateway Load Balancer
FortiGate Integration with GWLB: Fortinet Documentation
Question #6
Refer to the exhibit.
A customer is using the AWS Elastic Load Balancer (ELB).
Which two statements are correct about the ELB configuration? (Choose two.)
- A . The load balancer is configured to load balance traffic among multiple availability zones.
- B . The Amazon Resource Name is used to access the load balancer node and targets.
- C . You can use the DNS name to reach the targets behind the ELB.
- D . The load balancer is configured for the internal traffic of the virtual public cloud (VPC).
Correct Answer: A, C
A, C
Explanation:
Load Balancer Configuration Overview:
The provided configuration indicates that the ELB is an internet-facing load balancer.
Multi-AZ Load Balancing:
The load balancer is configured to distribute traffic across multiple availability zones (A, B, and C), ensuring high availability and fault tolerance (Option A).
Accessing Targets via DNS:
The DNS name of the load balancer (LabELB-716e15332f6401f8.elb.us-east-2.amazonaws.com) can be used to reach the targets behind the ELB, facilitating traffic routing to the appropriate instances (Option C).
Comparison with Other Options:
Option B is incorrect as the ARN is not used to access the load balancer directly.
Option D is incorrect because the load balancer is configured for internet-facing traffic, not just
internal VPC traffic.
Reference: AWS Elastic Load Balancer Documentation: AWS ELB
Understanding ELB DNS: AWS ELB DNS
A, C
Explanation:
Load Balancer Configuration Overview:
The provided configuration indicates that the ELB is an internet-facing load balancer.
Multi-AZ Load Balancing:
The load balancer is configured to distribute traffic across multiple availability zones (A, B, and C), ensuring high availability and fault tolerance (Option A).
Accessing Targets via DNS:
The DNS name of the load balancer (LabELB-716e15332f6401f8.elb.us-east-2.amazonaws.com) can be used to reach the targets behind the ELB, facilitating traffic routing to the appropriate instances (Option C).
Comparison with Other Options:
Option B is incorrect as the ARN is not used to access the load balancer directly.
Option D is incorrect because the load balancer is configured for internet-facing traffic, not just
internal VPC traffic.
Reference: AWS Elastic Load Balancer Documentation: AWS ELB
Understanding ELB DNS: AWS ELB DNS
Question #7
Which two statements about the FortiCloud portal are true? (Choose two.)
- A . You can gain remote access to your FortiGate VM directly from the portal.
- B . To assign permissions in the identity and access management (JAM) portal, you must write a JSON script.
- C . You can access the FortiFlex portal only after you purchase a FortiFlex license and register it on FortiCare.
- D . You can access only cloud services that you have subscribed to on AWS marketplace.
Correct Answer: A, C
A, C
Explanation:
Remote Access to FortiGate VM:
The FortiCloud portal allows users to remotely access their FortiGate VM instances. This is particularly useful for managing and configuring instances without needing direct network access (Option A).
FortiFlex Portal Access:
The FortiFlex portal is a feature that becomes available only after purchasing a FortiFlex license and
registering it on FortiCare. This portal provides additional functionalities and services related to
FortiFlex (Option C).
IAM Permissions:
Option B is incorrect because the Identity and Access Management (IAM) permissions in the FortiCloud portal do not require writing JSON scripts; they can be managed through the portal interface.
Subscription to Cloud Services:
Option D is incorrect because FortiCloud provides access to services beyond those subscribed through the AWS marketplace, including services directly offered by Fortinet.
Reference: FortiCloud Documentation: FortiCloud
FortiFlex Portal: FortiFlex Licensing
A, C
Explanation:
Remote Access to FortiGate VM:
The FortiCloud portal allows users to remotely access their FortiGate VM instances. This is particularly useful for managing and configuring instances without needing direct network access (Option A).
FortiFlex Portal Access:
The FortiFlex portal is a feature that becomes available only after purchasing a FortiFlex license and
registering it on FortiCare. This portal provides additional functionalities and services related to
FortiFlex (Option C).
IAM Permissions:
Option B is incorrect because the Identity and Access Management (IAM) permissions in the FortiCloud portal do not require writing JSON scripts; they can be managed through the portal interface.
Subscription to Cloud Services:
Option D is incorrect because FortiCloud provides access to services beyond those subscribed through the AWS marketplace, including services directly offered by Fortinet.
Reference: FortiCloud Documentation: FortiCloud
FortiFlex Portal: FortiFlex Licensing
Question #8
Which three statements correctly describe FortiGate Cloud-Native Firewall (CNF)? (Choose three.)
- A . It provides carrier-grade protection.
- B . It scales seamlessly.
- C . It uses AWS Elastic Load Balancing (ELB).
- D . It is considered to be a Firewall-as-a-Service (FWaaS).
- E . It can be managed by FortiManager and AWS firewall manager.
Correct Answer: BDE
BDE
Explanation:
Scalability:
FortiGate Cloud-Native Firewall (CNF) is designed to scale seamlessly with your cloud infrastructure,
providing the necessary protection without requiring manual intervention for scaling (Option B).
Firewall-as-a-Service:
FortiGate CNF is offered as a Firewall-as-a-Service (FWaaS), which simplifies the deployment and management of firewall capabilities directly in the cloud environment (Option D).
Management:
FortiGate CNF can be managed using FortiManager and AWS Firewall Manager, providing comprehensive management capabilities both from Fortinet’s platform and AWS’s native management tools (Option E).
Other Considerations:
Option A (carrier-grade protection) is not specifically highlighted as a feature of FortiGate CNF. Option C (uses AWS Elastic Load Balancing) is incorrect as FortiGate CNF operates independently of AWS ELB, although it can integrate with various AWS services.
Reference: FortiGate CNF Documentation: FortiGate CNF
AWS Firewall Manager: AWS Firewall Manager
BDE
Explanation:
Scalability:
FortiGate Cloud-Native Firewall (CNF) is designed to scale seamlessly with your cloud infrastructure,
providing the necessary protection without requiring manual intervention for scaling (Option B).
Firewall-as-a-Service:
FortiGate CNF is offered as a Firewall-as-a-Service (FWaaS), which simplifies the deployment and management of firewall capabilities directly in the cloud environment (Option D).
Management:
FortiGate CNF can be managed using FortiManager and AWS Firewall Manager, providing comprehensive management capabilities both from Fortinet’s platform and AWS’s native management tools (Option E).
Other Considerations:
Option A (carrier-grade protection) is not specifically highlighted as a feature of FortiGate CNF. Option C (uses AWS Elastic Load Balancing) is incorrect as FortiGate CNF operates independently of AWS ELB, although it can integrate with various AWS services.
Reference: FortiGate CNF Documentation: FortiGate CNF
AWS Firewall Manager: AWS Firewall Manager
Question #9
AWS native network services offer vast functionality and inter-connectivity between the cloud and on-premises networks.
Which three additional functions can FortiGate for AWS offer to complement the native services offered by AWS? (Choose three.)
- A . Higher VPN throughput
- B . Web filtering
- C . OSPF over IPSec
- D . Advanced dynamic routing
- E . Secure SD-WAN with application visibility
Correct Answer: BCE
BCE
Explanation:
Web Filtering:
FortiGate for AWS offers advanced web filtering capabilities, which allow organizations to control and
monitor web access. This feature complements AWS’s native security services by providing granular
control over web traffic (Option B).
OSPF over IPSec:
FortiGate for AWS can establish dynamic routing protocols such as OSPF (Open Shortest Path First) over IPSec tunnels. This capability enhances network routing flexibility and security, which is not natively provided by AWS (Option C).
Secure SD-WAN with Application Visibility:
FortiGate for AWS provides Secure SD-WAN functionality, offering enhanced application visibility and traffic management. This is a significant addition to AWS’s networking services, optimizing application performance and security (Option E).
Comparison with Other Options:
Option A (Higher VPN throughput) is not specifically enhanced by FortiGate as compared to AWS native services.
Option D (Advanced dynamic routing) is partially covered under OSPF over IPSec but is not as specific
as the other chosen options.
Reference: FortiGate for AWS Documentation: FortiGate on AWS
AWS Networking and Content Delivery: AWS Networking
BCE
Explanation:
Web Filtering:
FortiGate for AWS offers advanced web filtering capabilities, which allow organizations to control and
monitor web access. This feature complements AWS’s native security services by providing granular
control over web traffic (Option B).
OSPF over IPSec:
FortiGate for AWS can establish dynamic routing protocols such as OSPF (Open Shortest Path First) over IPSec tunnels. This capability enhances network routing flexibility and security, which is not natively provided by AWS (Option C).
Secure SD-WAN with Application Visibility:
FortiGate for AWS provides Secure SD-WAN functionality, offering enhanced application visibility and traffic management. This is a significant addition to AWS’s networking services, optimizing application performance and security (Option E).
Comparison with Other Options:
Option A (Higher VPN throughput) is not specifically enhanced by FortiGate as compared to AWS native services.
Option D (Advanced dynamic routing) is partially covered under OSPF over IPSec but is not as specific
as the other chosen options.
Reference: FortiGate for AWS Documentation: FortiGate on AWS
AWS Networking and Content Delivery: AWS Networking
Question #10
Your organization is deciding between deploying an active-active (A-A) or active-passive (A-P) FortiGate high availability (HA) cluster in AWS cloud.
Which two statements are true about A-A clusters compared to A-P clusters? (Choose two.)
- A . For A-A clusters, FortiGate must perform SNAT inbound to ensure symmetric traffic flow.
- B . A-A clusters rely on API calls for sfailovers.
- C . A-A clusters always require a load balancer.
- D . A-A clusters can use a software-defined network (SDN) to perform a failover.
Correct Answer: A, C
A, C
Explanation:
Symmetric Traffic Flow with SNAT:
In active-active (A-A) clusters, symmetric traffic flow is essential for maintaining session integrity across multiple instances. Source Network Address Translation (SNAT) is performed inbound to ensure that return traffic is routed correctly (Option A). Load Balancer Requirement:
A-A clusters require a load balancer to distribute incoming traffic evenly across the active instances.
This is crucial for balancing the load and providing high availability (Option C).
API Calls and Failovers:
Option B is incorrect because failovers in A-A clusters do not typically rely on API calls but are managed by the load balancer and the clustering mechanism itself. Software-Defined Network (SDN) Failover:
Option D is incorrect as SDN is not specifically required for performing failovers in A-A clusters. The failover mechanism is typically managed by the load balancer and FortiGate’s clustering technology.
Reference: FortiGate High Availability on AWS: FortiGate HA
AWS Elastic Load Balancing: AWS ELB
A, C
Explanation:
Symmetric Traffic Flow with SNAT:
In active-active (A-A) clusters, symmetric traffic flow is essential for maintaining session integrity across multiple instances. Source Network Address Translation (SNAT) is performed inbound to ensure that return traffic is routed correctly (Option A). Load Balancer Requirement:
A-A clusters require a load balancer to distribute incoming traffic evenly across the active instances.
This is crucial for balancing the load and providing high availability (Option C).
API Calls and Failovers:
Option B is incorrect because failovers in A-A clusters do not typically rely on API calls but are managed by the load balancer and the clustering mechanism itself. Software-Defined Network (SDN) Failover:
Option D is incorrect as SDN is not specifically required for performing failovers in A-A clusters. The failover mechanism is typically managed by the load balancer and FortiGate’s clustering technology.
Reference: FortiGate High Availability on AWS: FortiGate HA
AWS Elastic Load Balancing: AWS ELB