Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Fortinet Exam FCP_WCS_AD-7.4 Topic 3 Question 12 Discussion

Actual exam question for Fortinet's FCP_WCS_AD-7.4 exam
Question #: 12
Topic #: 3
[All FCP_WCS_AD-7.4 Questions]

An AWS administrator is designing internet connectivity for an organization's virtual public cloud (VPC). The organization has web servers with private addresses that must be reachable from the internet. The web servers must be highly available.

Which two configurations can you use to ensure the web servers are highly available and reachable from the internet? (Choose two.)

Show Suggested Answer Hide Answer
Suggested Answer: A, B

DNS Configuration:

For FortiWeb Cloud to effectively protect web applications, the DNS records for the application servers must be configured to point to FortiWeb Cloud. This ensures that all incoming traffic is routed through FortiWeb Cloud for inspection and protection (Option A).

Traffic Filtering:

FortiWeb Cloud provides robust protection by filtering incoming traffic to block the OWASP Top 10 attacks, zero-day threats, and other application layer attacks. This ensures the security and integrity of the web applications it protects (Option B).

Other Options Analysis:

Option C is incorrect because FortiWeb Cloud can protect application servers across different VPCs or regions, not just within the same VPC.

Option D is incorrect because step 2 does not require an AWS S3 bucket; it refers to the inspection and filtering of incoming traffic.


FortiWeb Cloud Overview: FortiWeb Cloud

DNS Configuration for Web Applications: DNS Configuration

Contribute your Thoughts:

Tom
1 months ago
Hmm, I'm leaning towards B and D as well. Though I wonder if C might also work, as long as the internet gateway is properly configured.
upvoted 0 times
Nicolette
4 days ago
C could work too if the internet gateway is set up correctly.
upvoted 0 times
...
Kami
16 days ago
I think B and D are the best options for high availability.
upvoted 0 times
...
...
Micheline
2 months ago
Haha, I bet the person who wrote this question is a secret comedian. They really want to see if we're paying attention to the details!
upvoted 0 times
Erasmo
22 days ago
D) Deploy web servers in multiple availability zones.
upvoted 0 times
...
Donte
1 months ago
A) Deploy a network load balancer.
upvoted 0 times
...
...
Lilli
2 months ago
I'm not sure about B, since the NAT Gateway is primarily for outbound internet traffic. I would go with A and D as the best options.
upvoted 0 times
Dick
1 months ago
I think you're right. Using a network load balancer and deploying web servers in multiple availability zones will ensure the web servers are highly available and reachable from the internet.
upvoted 0 times
...
Harris
2 months ago
I agree, deploying a network load balancer and having web servers in multiple availability zones is the best option for high availability.
upvoted 0 times
...
...
Leonor
2 months ago
I think B and D are the correct answers. The NAT Gateway allows the web servers with private addresses to be accessed from the internet, and deploying them in multiple availability zones ensures high availability.
upvoted 0 times
...
Skye
2 months ago
I also think adding a route to the default VPC route table forwarding all traffic to the internet gateway is important to ensure the web servers are reachable from the internet.
upvoted 0 times
...
Fausto
2 months ago
I agree with Johnetta. Using a network load balancer will distribute traffic evenly and deploying web servers in multiple availability zones will ensure high availability.
upvoted 0 times
...
Johnetta
2 months ago
I think deploying a network load balancer and deploying web servers in multiple availability zones are good options.
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