Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon Exam ANS-C01 Topic 1 Question 20 Discussion

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

A company has workloads that run in a VPC. The workloads access Amazon S3 by using an S3 gateway endpoint. The company also has on-premises workloads that need to access Amazon

S3 privately over a VPN connection. The company has established the VPN connection to the VPC.

Which solution will provide connectivity to Amazon S3 from the VPC workloads and the on-premises workloads in the MOST operationally efficient way?

Show Suggested Answer Hide Answer
Suggested Answer: C

The correct solution is to use an S3 interface endpoint and an on-premises DNS resolver. An S3 interface endpoint allows you to access Amazon S3 using private IP addresses within your VPC. An on-premises DNS resolver can be configured to forward the DNS queries for the S3 domain names to the S3 interface endpoint, so that the on-premises workloads can access Amazon S3 privately over the VPN connection. This solution is operationally efficient, as it does not require any additional infrastructure or changes to the existing workloads. The VPC workloads can continue to use the S3 gateway endpoint, which provides lower latency and higher throughput than the S3 interface endpoint.


Contribute your Thoughts:

Sheridan
10 months ago
Interesting point, Eura. It's always good to consider different options before making a decision.
upvoted 0 times
...
Eura
10 months ago
I personally prefer option C. Setting up an S3 interface endpoint and configuring DNS resolver seems like a simpler solution.
upvoted 0 times
...
Earlean
10 months ago
I see your point, Sheridan. But I think having both VPC and on-premises workloads use the same endpoint in option A is more efficient.
upvoted 0 times
...
Sheridan
11 months ago
But what about option B? Would deleting the S3 gateway endpoint and using an S3 interface endpoint be better?
upvoted 0 times
...
Tiera
11 months ago
I agree with Earlean. Using an ALB as a proxy server seems like a good choice.
upvoted 0 times
...
Earlean
11 months ago
I think option A is the most operationally efficient solution.
upvoted 0 times
...
Oliva
1 years ago
Alright, I'm convinced. Option C it is. Now let's just hope the exam question doesn't throw us a curveball!
upvoted 0 times
...
Matthew
1 years ago
Agreed. I think option C is the way to go. Nice and clean, and it leverages the existing S3 gateway endpoint for the VPC workloads.
upvoted 0 times
...
Timmy
1 years ago
True, but then you have the overhead of managing the proxy fleet. And if the on-premises workloads need to access other AWS services, that could get messy.
upvoted 0 times
Amos
12 months ago
True, but then you have the overhead of managing the proxy fleet. And if the on-premises workloads need to access other AWS services, that could get messy.
upvoted 0 times
...
Delisa
12 months ago
A) Deploy a proxy fleet of Amazon EC2 instances in the VPC behind an Application Load Balancer (ALB). Configure the on-premises workloads to use the ALB as the proxy server to connect to Amazon S3. Configure the proxy fleet to use the S3 gateway endpoint to connect to Amazon S3.
upvoted 0 times
...
Arthur
12 months ago
B) Delete the S3 gateway endpoint. Create an S3 interface endpoint. Deploy a proxy fleet of Amazon EC2 instances in the VPC behind an Application Load Balancer (ALB). Configure the on-premises workloads to use the ALB as the proxy server to connect to Amazon S3. Configure the proxy fleet and the VPC workloads to use the S3 interface endpoint to connect to Amazon S3.
upvoted 0 times
...
...
Christa
1 years ago
Haha, yeah, the proxy fleet sounds like a recipe for 'operational headaches'. I'd rather not have to deal with that if I can avoid it.
upvoted 0 times
...

Save Cancel