In Microsoft OLE DB architecture, what specifically does a tabular data provider do when exposing data to consumers? Select the most accurate description of its behavior and interface contract.

Introduction / Context:
OLE DB is a COM-based data access architecture from Microsoft. It separates roles into providers (which expose data) and consumers (which use data). Within providers, there are different flavors, including tabular data providers and service providers. Understanding their responsibilities is essential for integrating heterogeneous data sources with a uniform programming model.

Given Data / Assumptions:

• A tabular data provider owns or fronts a specific data store (for example, SQL Server, Excel, CSV files).
• OLE DB consumers expect results in a common tabular abstraction called a rowset.
• Service providers can add services (for example, caching, query processing) but need not own data.

Concept / Approach:
In OLE DB, the core artifact representing query results is the rowset. A tabular data provider must support the interfaces necessary to deliver rowset-style access to records, columns, and metadata. This makes consuming code independent of the back-end source while still enabling performant, cursor-like enumeration.

Step-by-Step Solution:

Verification / Alternative check:
Review typical OLE DB provider capabilities; documentation consistently describes rowset interfaces (IRowset and related) as the vehicle for delivering records from data stores.

Why Other Options Are Wrong:

• Does not own data (a): that describes a service provider, not specifically a tabular data provider.
• Transforms but no rowsets (b): contradicts the tabular model of OLE DB results.
• Both consumer and provider (c): conflates roles; a provider serves consumers.
• Only metadata (e): incomplete; tabular providers return data, not just catalogs.

Common Pitfalls:
Confusing OLE DB service providers (which add services) with tabular data providers (which expose the tabular data itself).

Final Answer:
It exposes data via rowsets (tabular, cursor-like results) to OLE DB consumers.