Question

Difficulty: HardWindows Administrative and System Management Tools

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?

  1. The 32-bit ODBC Data Source Administrator utility located in C:\Windows\SysWOW64\odbcad32.exeAnswer
  2. Performance Monitor (perfmon.msc) to build custom Data Collector Sets for logging disk counters over timeAnswer
  3. C
    Task Manager (taskmgr.exe) to record long-term historical performance logs across system reboots
  4. D
    The 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

1
Identify the proper ODBC administration binary architecture.
Recognize that on 64-bit Windows editions, 32-bit applications require DSNs created via C:\Windows\SysWOW64\odbcad32.exe rather than the default 64-bit utility in System32.
32-bit database drivers and applications interact exclusively with 32-bit registry entries created by the 32-bit ODBC manager.
2
Select the appropriate administrative tool for long-term historical resource logging.
Choose Performance Monitor (perfmon.msc) to define custom Data Collector Sets targeting physical and logical disk performance counters.
Task Manager provides live resource visualization but lacks functionality for historical data collection, whereas Performance Monitor supports persistent counter logging.

Key Concept

Windows 32-bit vs 64-bit Administrative Utilities and Performance Counter Logging
Rate this question