A systems administrator is setting up Windows 11 Pro workstations for a software development team. The team utilizes legacy 32-bit database applications that require custom Data Source Names (DSNs) and also requires long-term, historical tracking of disk queue lengths and latency metrics. Which TWO of the following tools or utilities should the administrator configure to satisfy these specific operational requirements?
- The 32-bit ODBC Data Source Administrator utility located in C:\Windows\SysWOW64\odbcad32.exeAnswer
- Performance Monitor (perfmon.msc) to build custom Data Collector Sets for logging disk counters over timeAnswer
- CTask Manager (taskmgr.exe) to record long-term historical performance logs across system reboots
- DThe 64-bit ODBC Data Source Administrator utility located in C:\Windows\System32\odbcad32.exe for 32-bit application DSN creation
Answer
The administrator must use the 32-bit ODBC Data Source Administrator utility in C:\Windows\SysWOW64\odbcad32.exe to configure DSNs for 32-bit software, and Performance Monitor (perfmon.msc) with Data Collector Sets for logging historical disk queue metrics.
The correct tools are the 32-bit ODBC Data Source Administrator in the SysWOW64 directory and Performance Monitor. On 64-bit Windows systems, 32-bit applications require DSNs configured via C:\Windows\SysWOW64\odbcad32.exe. Performance Monitor (perfmon.msc) is the built-in utility specifically designed for configuring long-term historical performance counter logs through Data Collector Sets.
Step-by-Step Solution
Key Concept
Windows 32-bit vs 64-bit Administrative Utilities and Performance Counter Logging