Your company has an AWS Direct Connect connection in the us-west region. They are currently using a public VIF to access an S3 bucket in the us-west region. They now want to make use of AWS Direct Connect to access an S3 bucket in the us-east region. How can this be achieved most economically?

Answer options:

A.Create another AWS Direct Connect connection from your on-premises network in the us-east region.
B.Create another Private VIF from your current AWS Direct connect connection.
C.Use the same Public VIF from your current AWS Direct connect connection.
D.Create a VPN IPsec connection.

Answer – C
The AWS Documentation mentions the following to support this.
AWS Direct Connect locations in public regions or AWS GovCloud (US) can access public services in any other public region (excluding China (Beijing)). In addition, AWS Direct Connect connections in public regions or AWS GovCloud (US) can be configured to access a VPC in your account in any other public region (excluding China (Beijing)). You can therefore use a single AWS Direct Connect connection to build multi-region services. All networking traffic remains on the AWS global network backbone, regardless of whether you access public AWS services or a VPC in another region.
Option A is possible but is not the most economical route.
Option B is incorrect since a Private VIF cannot be used for public resources.
Option D is incorrect since you can make use of the current AWS Direct Connect connection.
For more information on AWS Direct Connect Remote regions, please refer to the below URL
https://docs.aws.amazon.com/directconnect/latest/UserGuide/remote_regions.html