In ODBC configuration, what do we call a sharable, file-backed definition of a data source that multiple users or machines can use (often stored as a .dsn file)?

Introduction / Context:
ODBC data sources (DSNs) can be stored in different ways. Understanding User, System, and File data sources helps administrators share connection settings and simplify deployments across teams and machines.

Given Data / Assumptions:

• A “sharable” data source implies portability via a file that can be copied or placed on a share.
• ODBC supports .dsn files that encapsulate driver and connection properties.

Concept / Approach:
A File Data Source (file DSN) stores connection information in a text file (typically with a .dsn extension). Because it is file-based, it can be distributed and reused across systems. By contrast, User and System DSNs are stored in the Windows registry and are machine-bound.

Step-by-Step Solution:

Verification / Alternative check:
Windows ODBC Data Source Administrator provides tabs for User DSN, System DSN, and File DSN, illustrating their storage locations.

Why Other Options Are Wrong:

• User/System DSN: Stored in the registry; not inherently sharable as files.
• SQL text file: Not an ODBC configuration artifact for connections.
• Registry DSN: Not standard terminology; user/system DSNs are the registry-backed types.

Common Pitfalls:
Assuming DSN-less connection strings in applications replace DSNs entirely; they can coexist depending on deployment strategy.

Final Answer:
File data source