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

- Free Preparation Discussions

Amazon Exam ANS-C01 Topic 7 Question 14 Discussion

Actual exam question for Amazon's ANS-C01 exam
Question #: 14
Topic #: 7
[All ANS-C01 Questions]

An ecommerce company is hosting a web application on Amazon EC2 instances to handle continuously changing customer demand. The EC2 instances are part of an Auto Scaling group. The company wants to implement a solution to distribute traffic from customers to the EC2 instances. The company must encrypt all traffic at all stages between the customers and the application servers. No decryption at intermediate points is allowed.

Which solution will meet these requirements?

Show Suggested Answer Hide Answer

Contribute your Thoughts:

Tammi
2 months ago
I'd go with Option C. A Network Load Balancer handles TCP traffic well, and it should be able to encrypt the connections too. Seems like a solid choice.
upvoted 0 times
Garry
18 days ago
Yeah, Option C is the way to go. It meets the requirements of encrypting traffic and distributing it effectively.
upvoted 0 times
...
Edelmira
23 days ago
I agree, using a Network Load Balancer for this scenario seems like the most appropriate solution.
upvoted 0 times
...
Marci
29 days ago
Option C sounds like a good choice. Network Load Balancer is known for handling TCP traffic efficiently.
upvoted 0 times
...
...
Jess
2 months ago
Haha, Option D with the Gateway Load Balancer? That's a new one! I've never even heard of that before. Sounds like someone is trying to trick us.
upvoted 0 times
Tammy
10 days ago
C) Create a Network Load Balancer (NLB). Add a TCP listener to the NLB. Configure the Auto Scaling group to register instances with the NLB's target group.
upvoted 0 times
...
Lucille
12 days ago
B) Create an Amazon CloudFront distribution. Configure the distribution with a custom SSL/TLS certificate. Set the Auto Scaling group as the distribution's origin.
upvoted 0 times
...
Rosio
1 months ago
A) Create an Application Load Balancer (ALB). Add an HTTPS listener to the ALB. Configure the Auto Scaling group to register instances with the ALB's target group.
upvoted 0 times
...
...
Odelia
2 months ago
I'm not sure about Option B. CloudFront is great for content delivery, but I don't think it's the right fit for this use case. Seems like overkill.
upvoted 0 times
Lai
29 days ago
A) Definitely, ALB with HTTPS listener should be sufficient for encrypting traffic between customers and application servers.
upvoted 0 times
...
Elouise
1 months ago
B) I agree, CloudFront might be too much for this scenario. It's better to go with a simpler solution.
upvoted 0 times
...
Keith
1 months ago
A) Create an Application Load Balancer (ALB). Add an HTTPS listener to the ALB. Configure the Auto Scaling group to register instances with the ALB's target group.
upvoted 0 times
...
...
Alpha
2 months ago
I'm not sure, but I think option B with Amazon CloudFront could also work since it allows custom SSL/TLS certificates for encryption.
upvoted 0 times
...
Brunilda
2 months ago
Option A seems like the obvious choice here. An ALB with HTTPS listener is the perfect solution to encrypt traffic and distribute it to the EC2 instances. Easy to set up and manage.
upvoted 0 times
Ma
2 months ago
I agree, ALB is easy to set up and manage. It's the perfect solution for this scenario.
upvoted 0 times
...
Katlyn
2 months ago
Option A seems like the best choice. ALB with HTTPS listener will encrypt traffic and distribute it to EC2 instances.
upvoted 0 times
...
...
Carin
2 months ago
I agree with Kara. Option A ensures end-to-end encryption without decryption at intermediate points.
upvoted 0 times
...
Kara
2 months ago
I think option A is the best solution because it uses an Application Load Balancer with HTTPS listener for encryption.
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