QuestionQ17

VerifiedNetwork Security, Compliance, and Governance

A company operates a hybrid cloud environment. Its data center connects to the AWS Cloud through an AWS Direct Connect connection. The AWS environment includes VPCs connected in a hub-and-spoke model by a transit gateway. The AWS environment uses a transit VIF with a Direct Connect gateway for on-premises connectivity.

The company uses a hybrid DNS model. It has configured Amazon Route 53 Resolver endpoints in the hub VPC to permit bidirectional DNS traffic flow. The company runs a backend application in one of the VPCs.

The company uses a message-oriented architecture and uses Amazon Simple Queue Service (Amazon SQS) to receive messages from other applications over a private network. A network engineer wants to use an interface VPC endpoint for Amazon SQS for this architecture. Client services must be able to access the endpoint service from on premises and from multiple VPCs in the company's AWS infrastructure.

Which combination of actions should the network engineer take to ensure that the client applications can resolve DNS for the interface endpoint?

Choose three
Explanation

Enabling private DNS on an AWS service interface endpoint creates an AWS-managed private hosted zone for the endpoint VPC; it is not the mechanism for sharing that DNS override with other VPCs. A customer-managed private hosted zone for sqs.us-east-1.amazonaws.com can contain records that target the interface endpoint and can be associated with every client VPC. With on-premises DNS queries forwarded through a Route 53 Resolver inbound endpoint, on-premises clients can resolve the same private zone. Clients continue to use the standard regional SQS hostname, which resolves privately to the endpoint network interfaces.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!