Database Management Systems

Frequently changing prices should be modeled as time-dependent transaction data, not static master data attributes. This preserves historical price accuracy and supports performance. The ODS (C) and fact table (D) are incorrect for this use case.

In data warehousing, fact tables contain key figures (metrics or measurements) and DIM IDs (foreign keys referencing dimension tables). The actual dimension attributes (Characteristics) live in dimension tables, not fact tables.

Hibernate is indeed an Object-Relational Mapping (ORM) framework for Java that provides a bridge between object-oriented domain models and relational databases. It allows developers to work with Java objects instead of writing raw SQL queries, automatically handling the translation between objects and database records.

'Pure relational' is the odd one out because it refers to a pure database approach without ORM, while the other options (caching, outer join fetching, lazy collection initialization) are all Hibernate ORM performance optimization techniques. Hibernate is specifically about bridging the gap between objects and relational databases, not staying purely relational.

DB2 for z/OS can be accessed from mainframe environments such as Time Sharing Option (TSO) and Customer Information Control System (CICS). These environments use attachment facilities to interact with the DB2 subsystem.

The Serializable isolation level provides perfect isolation by ensuring transactions appear to run sequentially. Read Committed allows non-repeatable reads, and Read Uncommitted allows dirty reads.

Business transactions represent meaningful real-world interactions or workflows that are initiated by and visible to the end user. While databases and EJBs handle the technical execution, the transaction itself is a user-facing concept.

.NET Framework data providers have four core components: Connection (establishes database connection), Command (executes SQL), DataReader (forward-only read access), and DataAdapter (fills DataSet). DataSet itself is a separate object, not a provider component.

ADO.NET's fundamental objects are DataReader (connected, forward-only read) and Dataset (disconnected, in-memory cache). DataAdapter and DataRelation are supporting objects, while DataTable and DataRow are Dataset contents.

DataSet contains DataTable objects, which contain DataRow and DataColumn objects. These are the core constituents. DataCollection is not a standard ADO.NET DataSet component.

In ADO.NET, SqlConnection establishes the connection, SqlCommand executes queries, and SqlDataReader retrieves the read-only stream of data from a SQL Server database. All of these classes are essential components of the System.Data.SqlClient namespace.

ADO.NET has three logical layers: Physical Data Store (database), DataSet (in-memory cache), and Data Provider (bridge between them - Connection, Command, DataAdapter, DataReader). All three layers are essential components.

Option A shows the standard one-line declaration and instantiation of SqlConnection. Option B demonstrates two-step initialization: first declaring null, then assigning with new keyword. Both are valid C# syntax patterns. Option C is incorrect because it omits the 'new' keyword required for object instantiation.