A company deployed new applications in the cloud and configured a site-to-site VPN to connect the internal data center with the cloud. The IT team wants the internal servers to connect to those applic

Question

Options

• ACreate a DNS server in the cloud. Configure the DNS server in the customer data center to
• BConfigure a NAT server on the cloud to allow internal servers to connect to the applications
• CRegister applications on the cloud with a public DNS sever and configure internal servers to
• DConfigure proxy service in the site-to-site VPN to allow internal servers to access applications

• A
  75% (47)
• B
  5% (3)
• C
  8% (5)
• D
  13% (8)

Explanation

With a site-to-site VPN already in place, traffic between the data center and cloud travels over private RFC 1918 address space. The missing piece is name resolution: internal servers need to resolve cloud application hostnames to their private cloud IP addresses (not public ones). By deploying a private DNS server in the cloud and configuring the on-premises DNS server to conditionally forward cloud domain queries to it, internal servers receive private IP addresses in DNS responses and route traffic through the VPN tunnel. Option B (NAT) doesn't eliminate the need for addressing coordination. Option C (public DNS) explicitly uses public IPs, violating the requirement. Option D (proxy in VPN) is not a standard or practical solution for this scenario.

No community discussion yet for this question.