You need to capture all DNS queries and responses from a busy Windows Server DNS resolver for one hour with minimal performance impact and then analyze the data centrally. What should you configure?

The Microsoft-Windows-DNS-Server/Analytical channel provides detailed DNS query and response logging with minimal performance overhead compared to traditional debug logging. This channel is designed for high-volume environments. Collecting these events via Windows Event Forwarding (WEF) allows for centralized analysis without impacting the DNS server's performance by writing to a local file. DNS debug logging to a text file is resource-intensive and can significantly impact performance on a busy server. The DNS Server Audit log records administrative actions and changes, not detailed query/response traffic. Running ipconfig /displaydns on clients only shows client-side cache, not server-side query activity. Performance counters like Query Received/sec and Query Sent/sec provide aggregate statistics, not individual query and response details.