You have an EC2 instance in the AWS us-east-1 region. The application in the instance needs to access a DynamoDB table that is located in the AWS us-east-2 region. The connection must be private without leaving the Amazon network. The instance should not use any public IP for communication. How would you configure this?

Answer options:

A.Configure an inter-region VPC endpoint for the DynamoDB service.
B.Configure inter-region VPC peering and create a VPC endpoint for DynamoDB in us-east-1.
C.Create an inter-region VPC peering connection between us-east-1 and us-east-2.
D.There is no way to setup the private inter-region connections.

Answer – B
For the private connections between regions, VPC peering should be used. Then VPC endpoint allows users to access the DynamoDB service privately. 
Option A is incorrect because you cannot configure an inter-region VPC endpoint directly.
Option B is CORRECT because the VPC endpoint should be created in consumer VPC which is in us-east-1. ENI will be created in us-east-1 which will access DynamoDB over VPC peering & AWS PrivateLink.
Option C is incorrect: This option does not mention the usage of the VPC endpoint.
Option D is incorrect: Because VPC peering supports the inter-region connections.
You can refer to the below URL for inter-region peering & endpoints
https://d1.awsstatic.com/whitepapers/aws-privatelink.pdf
https://docs.aws.amazon.com/vpc/latest/privatelink/endpoint-service-overview.html