Choose two. A hybrid Active Directory domain spans on-prem Windows servers and Windows servers running in GCP. To ensure AD DNS name resolution works bi-directionally, which two steps are appropriate?

For bi-directional AD DNS resolution in a hybrid environment, you need to configure forwarding in both directions. The first correct option establishes forwarding from on-premises to GCP. An AD DNS conditional forwarder on your on-prem AD DNS servers directs queries for your AD domain to the Cloud DNS inbound endpoint IPs in GCP, allowing on-prem resources to resolve GCP-based AD records. The second correct option handles forwarding from GCP to on-premises. A Cloud DNS forwarding zone in GCP for your AD domain sends queries to your on-prem AD DNS servers, enabling GCP resources to resolve on-prem AD records. Both steps, combined with site connectivity (e.g., Cloud VPN or Interconnect), ensure seamless name resolution. Publishing the AD domain to public DNS is insecure and unnecessary for internal resolution. Using an HTTP(S) load balancer for DNS traffic is incorrect; DNS uses UDP/TCP port 53, not HTTP/HTTPS.