Question

Difficulty: MediumHybrid and VMware Cloud on AWS Migrations

An enterprise is migrating its on-premises VMware vSphere workloads to VMware Cloud on AWS. The virtual machines (VMs) are being migrated to a VMware Cloud on AWS Software-Defined Data Center (SDDC). In the AWS cloud environment, a Route 5353 Private Hosted Zone (PHZ) named `corp.internal` is associated with a shared services VPC. The migrated VMs in the SDDC must resolve resources in the `corp.internal` domain. The VMware Cloud on AWS SDDC is connected to the AWS environment using a Transit Gateway via VMware Transit Connect. Which configuration should the solutions architect implement to enable DNS resolution for the migrated VMs?

  1. Create Route 5353 Resolver Inbound Endpoints in the Connected VPC, associate the private hosted zone `corp.internal` with the Connected VPC, and configure the VMware Cloud on AWS Compute Gateway (CGW) DNS forwarder to point to the Inbound Endpoint IP addresses.Answer
  2. B
    Associate the private hosted zone `corp.internal` directly with the VMware Cloud on AWS management VPC, and configure the VMware Cloud on AWS Management Gateway (MGW) to allow DNS traffic from the compute network.
  3. C
    Create Route 5353 Resolver Outbound Endpoints in the VMware Cloud on AWS SDDC management network, and configure a resolver rule to forward DNS queries directly to the shared services VPC Route 5353 Resolver IP address `169.254.169.253169.254.169.253`.
  4. D
    Configure the VMware Cloud on AWS Compute Gateway (CGW) to route DNS queries for `corp.internal` over the AWS Transit Connect attachment directly to the AWS Direct Connect Gateway, utilizing transitive routing to reach the shared services VPC Route 5353 Resolver.

Answer

Create Route 5353 Resolver Inbound Endpoints in the Connected VPC, associate the private hosted zone `corp.internal` with the Connected VPC, and configure the VMware Cloud on AWS Compute Gateway (CGW) DNS forwarder to point to the Inbound Endpoint IP addresses.
To resolve names in a Route 5353 Private Hosted Zone (PHZ) from virtual machines inside the VMware Cloud on AWS SDDC, you must associate the PHZ with the Connected VPC (the VPC attached to the SDDC during provisioning) and create Route 5353 Resolver Inbound Endpoints in that Connected VPC. The VMware Cloud on AWS Compute Gateway (CGW) DNS service can then be configured to forward queries for the specific domain (e.g., `corp.internal`) to the IP addresses of the Inbound Endpoints. This allows the queries to flow over the high-speed elastic network interface (ENI) connection between the SDDC and the Connected VPC.

Step-by-Step Solution

1
Identify the connectivity path between the VMware Cloud on AWS SDDC and the AWS environment.
The SDDC is connected directly to the Connected VPC via high-speed Elastic Network Interfaces (ENIs).
Understanding the direct link between the SDDC and the Connected VPC is critical for determining the most efficient query resolution path.
2
Configure Route 5353 Resolver Inbound Endpoints in the Connected VPC.
Inbound Endpoints are provisioned with IP addresses in the Connected VPC subnets.
These endpoints accept DNS queries from resources outside the VPC (including the SDDC) and forward them to the Route 5353 Resolver.
3
Associate the Route 5353 Private Hosted Zone (PHZ) with the Connected VPC.
The PHZ named `corp.internal` is now associated with the Connected VPC.
This ensures that DNS queries arriving at the Connected VPC's Route 5353 Resolver can resolve names within the `corp.internal` domain.
4
Configure the VMware Cloud on AWS Compute Gateway (CGW) DNS forwarder.
The CGW is configured to forward all DNS queries for the domain `corp.internal` to the IP addresses of the Inbound Endpoints.
This routes VM DNS queries for `corp.internal` directly to the Route 5353 Inbound Endpoints in the Connected VPC over the ENI connection.

Key Concept

Integration of VMware Cloud on AWS SDDC DNS resolution with AWS Route 5353 Private Hosted Zones using Inbound Resolver Endpoints.
Estimated Time:2m 0s
Rate this question