You are an AWS architect in your organization. Your organization would want to upload files to the AWS S3 bucket. In a VPC, you create a private subnet and VPC endpoint for S3. You also create one route table that routes the traffic from the private subnet to a NAT gateway for the internet access. In AWS S3 server logs, you notice that the requests to the S3 bucket from an EC2 instance in the VPC do not go through the NAT Gateway. What could cause this situation?

Answer options:

A.When NAT Gateway and VPC endpoint exist on same route table, NAT Gateway always takes precedence.
B.EC2 instance has an elastic IP address associated with it.
C.The requests are routed through the VPC endpoint.
D.AWS S3 is a managed service so all requests will always go through the internal AWS network.

Answer: C
Option A is incorrect. VPC Endpoint always takes precedence over NAT Gateway or Internet Gateway. In the absence of a VPC endpoint, requests to S3 are routed to NAT Gateway or Internet Gateway based on their existence in the route table.
Option B is incorrect. The elastic IP address is an IPv4 public address assigned to the instance. It does not explain the situation.
Option C is CORRECT. The traffic goes through the S3 VPC endpoint so the NAT Gateway is not used in this scenario.
Option D is incorrect. If the S3 VPC endpoint is not configured, the requests will go through the internet.