Goals of Microsoft OLE DB: Which statement best captures OLE DB’s design objectives across heterogeneous data sources and DBMS features?

Introduction / Context:
OLE DB was introduced to unify access to diverse data stores—relational, hierarchical, file-based, and more—through a set of COM interfaces. Its architecture splits capabilities into components so applications can use only what they need while retaining cross-source flexibility.

Given Data / Assumptions:

• Heterogeneous data sources should be accessible consistently.
• Developers need modular functionality for commands, rowsets, transactions, and schema discovery.
• The goal is not limited to relational data.

Concept / Approach:
OLE DB defines object interfaces for discrete functions (for example, command execution, row retrieval). This increases flexibility by allowing providers and consumers to implement only the necessary parts. It also aims to offer an object interface across many data types, not solely relational databases.

Step-by-Step Solution:

Verification / Alternative check:
Review OLE DB provider documentation; it consistently emphasizes modularity, flexibility, and heterogeneous data access.

Why Other Options Are Wrong:

• Any single statement (a, b, or c) alone is incomplete.
• Option e is incorrect because OLE DB is not restricted to relational-only rowsets and includes broader object interfaces.

Common Pitfalls:
Assuming OLE DB equals “SQL-only.” It spans beyond SQL databases and can surface non-relational data via consistent COM interfaces.

Final Answer:
All of the above collectively describe OLE DB’s goals.