Administering Windows Server Hybrid Core Infrastructure (AZ-800) Practice

In which situation should an administrator create a stub zone?

1. For reverse lookups in the DNS infrastructure

2. To resolve internal DNS resource records

3. When integrating with partner organizations

4. To manage DNS record replication

The correct answer is: When integrating with partner organizations

Creating a stub zone is particularly useful in scenarios involving integration with partner organizations because it allows for efficient name resolution without the need to fully replicate the entire zone's data. A stub zone contains only the essential DNS records necessary to identify the authoritative DNS servers of the zone it represents, specifically the name servers and the associated resource records. This enables the local DNS server to make queries to the authoritative servers for that zone. In the context of partnering with external organizations, a stub zone simplifies the process of directing queries for the partner's domain to the correct DNS servers. This is essential for businesses that need to interact with each other’s systems and services, as it allows seamless communication and troubleshooting without exposing the entire DNS infrastructure to outside parties. Additionally, it manages the complexity of DNS resolution across organizational boundaries effectively while maintaining a degree of separation and security. This characteristic is why a stub zone is a practical choice for scenarios requiring collaboration or data exchange with partner organizations.