Design a DNS architecture so AWS accounts can resolve on-premises names, on-premises systems can resolve AWS names, and individual accounts can manage subdomains. The solution should use AWS native services and a single set of rules that work across accounts. Which combination of steps should the engineer take? (Choose three.)

To meet the requirements, a central Route 53 private hosted zone for the overall cloud domain allows for subdomain creation and management within individual accounts, associated with the central zone. Route 53 Resolver inbound and outbound endpoints in a central account enable DNS resolution between AWS and on-premises environments. An outbound endpoint forwards requests for on-premises names to an on-premises DNS resolver, while an inbound endpoint allows on-premises systems to query AWS names. Sharing Route 53 Resolver rules via AWS Resource Access Manager (RAM) ensures a single set of rules across accounts. Networking connectivity between accounts and to the Resolver endpoints is crucial for traffic flow. Using AWS Directory Service for Microsoft Active Directory is not the primary mechanism for cross-account DNS resolution or managing subdomains in this context; Route 53 Resolver is the native AWS service for this. While networking is essential, simply stating its existence without the correct DNS components is insufficient.