A company serves internet applications using a single Route 53 public hosted zone for its domain. A three-tier application is being redeveloped; frontend EC2 instances are in public subnets with Elastic IPs, and backend components are in private RFC1918 subnets. Application components must be able to resolve and reach each other inside the VPC using the same hostnames used on the public internet. The engineer must also allow for future DNS changes (new names or retired entries). Which combination of actions meets these needs? (Choose three.)

To allow internal VPC components to resolve public hostnames to private IP addresses, a Route 53 private hosted zone for the same domain name must be created and associated with the VPC. This enables split-horizon DNS, where internal requests resolve to private IPs and external requests resolve to public IPs. Enabling DNS hostnames for the VPC ensures that EC2 instances receive DNS hostnames, which is a prerequisite for DNS resolution within the VPC. Creating corresponding entries in the private hosted zone, mapping public hostnames to private IP addresses, completes the internal resolution. Geoproximity routing is irrelevant for internal VPC resolution. Adding private IPs to the public hosted zone would expose internal IPs externally and is incorrect. The EventBridge/Lambda solution is overly complex and unnecessary for this requirement.