When would you prefer a forward zone over configuring direct forwarders at the root or global level?

• A. When you want to apply forwarding behavior to a specific zone rather than all zones
• B. When you want to bypass forwarding entirely
• C. When you want to host the zone's data locally
• D. When you want to avoid DNS caching

Answer: (A)

Forward zones give you control over forwarding on a per-zone basis. This means you configure upstream forwarders specifically for that zone, so queries for that domain are redirected to chosen DNS servers while other zones can resolve differently or use different settings. This per-zone targeting is exactly why you’d choose a forward zone when you want the forwarding behavior to apply only to a particular zone rather than to every zone handled by the system. If forwarding were set at the root or global level, all zones would follow the same forwarding path, which isn’t desirable when only one zone should use special upstream servers. The other options don’t address this scope distinction: bypassing forwarding skips upstream servers entirely; hosting the zone’s data locally relates to authoritative data storage; and avoiding DNS caching isn’t related to where forwarding is applied.