MENU
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?
Suggested Answer: C
Get Premium ANS-C01 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
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.
38 comments · newest first
GA
Garry
10 months ago
C keeps it simple while still addressing both workloads.
MA
Marguerita
10 months ago
Surprised that A is even an option, seems overly complicated!
LO
Louisa
10 months ago
Option C seems like the best choice for efficiency.
LO
Lorrie
11 months ago
B would require too many changes, not ideal.
SH
Shawnta
11 months ago
I disagree, I think D is more straightforward.
CR
Craig
11 months ago
I’m leaning towards option D since it mentions Direct Connect, which seems like a solid solution for on-premises access, but I’m not entirely sure about the public VIF part.
RO
Ronnie
11 months ago
I practiced a similar question where we had to decide between gateway and interface endpoints. I feel like option A might be overcomplicating things with the proxy fleet.
KE
Kenny
11 months ago
I think option C sounds familiar because it mentions using a DNS resolver, but I’m a bit confused about how that would work with the gateway endpoint for VPC workloads.
DU
Dustin
12 months ago
I remember studying about VPC endpoints and how they can help with private connectivity to S3, but I'm not sure if the interface endpoint is the best choice here.
EM
Emiko
12 months ago
I'm leaning towards Option C. Using the S3 interface endpoint for the on-premises workloads and keeping the S3 gateway endpoint for the VPC workloads seems like a good balance.
CA
Carry
1 year ago
Option B seems promising, but I'm not sure if deleting the existing S3 gateway endpoint is the best approach. I'll need to weigh the pros and cons of each option.
MI
Mira
1 year ago
Okay, I think I've got a strategy here. The key is to find the most operationally efficient solution that provides connectivity for both the VPC and on-premises workloads.
TO
Tora
1 year ago
Hmm, I'm a bit confused by the different endpoint types and how they interact with the on-premises workloads. I'll need to review the details more closely.
PU
Pura
1 year ago
This looks like a tricky question. I'll need to carefully consider the different options and their implications.
LU
Lucia
1 year ago
I think option C could be a good alternative, using the S3 interface endpoint.
AL
Alfreda
1 year ago
Ah, the age-old debate of gateway vs. interface endpoints. Option B is like trying to fix a leaky faucet with duct tape. Option C is the plumber's solution - clean and effective.
HE
Helaine
1 year ago
Definitely, using the S3 interface endpoint with on-premises DNS resolver is the way to go.
MA
Marsha
1 year ago
I agree, Option C with the S3 interface endpoint seems like the best approach.
MI
Miriam
1 year ago
Option B seems like a temporary fix, not a long-term solution.
GL
Glory
1 year ago
Proxy servers? Load balancers? What is this, the 90s? Option C is the way to go, my dudes. Keep it simple, keep it secure.
FL
Florencia
1 year ago
Wait, we're using AWS Direct Connect now? That's a bit overkill, don't you think? I'd go with option C - the S3 interface endpoint setup seems like the most efficient solution.
EL
Elena
1 year ago
Yeah, the S3 interface endpoint setup in option C sounds like the best choice for efficiency.
IS
Isreal
1 year ago
I agree, setting up AWS Direct Connect seems like too much for this scenario.
JA
Janessa
1 year ago
Ah, the classic proxy server approach. Option A could work, but I feel like the overhead of the proxy fleet might be overkill here. Option C is more streamlined in my opinion.
LE
Lemuel
1 year ago
Let's go with Option C then, it seems like the best choice for our setup.
KA
Kati
1 year ago
Option C does seem like a cleaner approach to handle the connectivity.
SU
Suzi
1 year ago
Yeah, I think Option C is a simpler and more efficient solution.
DO
Dong
1 year ago
I agree, Option A seems like it might be a bit too much to manage.
DA
Danilo
1 year ago
I like the simplicity of option C. Using the S3 interface endpoint for on-premises and the existing S3 gateway for the VPC workloads is a clean and straightforward approach.
AL
Alita
1 year ago
Definitely, using the S3 interface endpoint for on-premises and the S3 gateway for VPC workloads is a smart solution.
AR
Arminda
1 year ago
I agree, it keeps things simple and efficient.
HI
Hillary
1 year ago
Option C seems like the best choice for this scenario.
SA
Santos
1 year ago
But option A uses the S3 gateway endpoint, which is already in place.
LU
Luisa
1 year ago
I disagree, I believe option B is more efficient.
JA
Jarvis
1 year ago
The proxy fleet solution in option B seems like the most operationally efficient way to handle both the VPC and on-premises workloads. The S3 interface endpoint allows for better control and security.
ST
Stephane
1 year ago
User 2
RE
Renato
1 year ago
User 1
SA
Santos
1 year ago
I think option A is the best solution.