An on-premises application uses the hostname host1.onprem.private. Another app on an EC2 instance uses host1.awscloud.private. A Site-to-Site VPN connects the two networks, but the on-prem app cannot resolve the EC2 hostname. Which configuration will allow the on-premises DNS resolver to resolve host1.awscloud.private?

The correct option allows the on-premises DNS resolver to query AWS for hostnames within the awscloud.private domain. A Route 53 Resolver inbound endpoint is necessary to allow DNS queries from on-premises into AWS. This endpoint is associated with the VPC where the EC2 instance resides. The on-premises DNS server is then configured to forward all DNS queries for awscloud.private to the IP addresses of this inbound endpoint. This enables the on-premises application to resolve the EC2 instance's hostname. Incorrect options: Forwarding queries for onprem.private to an inbound endpoint is incorrect because the on-premises DNS server already handles onprem.private and the EC2 instance needs to resolve awscloud.private. Route 53 Resolver outbound endpoints are used for DNS queries from AWS to on-premises, not the other way around. Configuring the on-premises DNS server to forward awscloud.private queries to an outbound endpoint is incorrect because outbound endpoints serve AWS resources querying external DNS, not external resources querying AWS DNS.