Database Management Systems

Checkpoint information in QTP is stored in the Local Repository associated with each action. Unlike shared objects that can be stored in a shared repository, checkpoints are specific to an action and are maintained locally within that action's object repository.

JDBC (Java DataBase Connectivity) is a Java API for connecting to databases. Option B correctly states what JDBC stands for. Option C is true because JDBC can access relational databases, spreadsheets (via JDBC-ODBC bridge or specific drivers), and flat files. Option A is incorrect because JDBC is primarily for relational databases - object and XML data sources require specialized adapters. Option D describes ORM tools like Hibernate, not JDBC itself.

To answer this question, the user needs to have knowledge about the JDBC (Java Database Connectivity) API and its packages.

Option A: This option is incorrect. There is no package called javax.jdbc in the JDBC API.

Option B: This option is also incorrect. There is no package called java.jdbc.sql in the JDBC API.

Option C: This option is correct. The JDBC API contains two key packages: java.sql and javax.sql.

Option D: This option is incorrect. There is no package called java.rdb or javax.rdb in the JDBC API.

Therefore, the correct answer is:

The Answer is: C. java.sql and javax.sql.

Type 1 JDBC drivers act as a bridge between JDBC and ODBC, translating JDBC calls into ODBC calls that are then processed by ODBC drivers. This was the earliest JDBC driver type and is now considered legacy technology, as it requires ODBC to be installed on the client machine.

In QTP, when you create a checkpoint, its configuration and properties are stored locally within the action's Local Object Repository (.mtr file).

Type 4 JDBC drivers are pure Java implementations that convert JDBC calls directly into the database's native network protocol without any intermediate middleware. This makes them platform-independent and typically the fastest and most efficient driver type. Type 1 uses ODBC bridge, Type 2 uses native client libraries, and Type 3 uses middleware translation.

A JDBC DataSource is a factory object that provides connections to a physical data source. It is the preferred way to establish database connections in modern Java applications as it supports connection pooling, distributed transactions, and driver isolation. Unlike the DriverManager, a DataSource is registered with JNDI and encapsulates connection details.

A JDBC transaction is bound to a Connection object. It is completed when commit() or rollback() is called on that connection, or implicitly when the connection is closed.

To understand the meaning of the transaction isolation level TRANSACTION_REPEATABLE_READ, we need to know about transaction isolation levels in database management systems.

Transaction isolation level is a concept that ensures the correctness and consistency of database transactions. It defines the level of isolation between concurrent transactions in the system.

The TRANSACTION_REPEATABLE_READ isolation level guarantees that during the transaction, any row that is read will be locked for the duration of the transaction. This means that if the transaction tries to read the same row again, it will get the same value as before. This ensures that the transaction sees a consistent snapshot of the data.

Now let's go through each option to see which one is correct:

A. (a) Dirty reads, non-repeatable reads, and phantom reads can occur - This option is incorrect. The TRANSACTION_REPEATABLE_READ level prevents dirty reads and non-repeatable reads, but phantom reads can still occur.

B. (b) Dirty reads are prevented; non-repeatable reads and phantom reads can occur - This option is incorrect. The TRANSACTION_REPEATABLE_READ level prevents dirty reads, but non-repeatable reads and phantom reads can still occur.

C. (c) Dirty reads and non-repeatable reads are prevented; phantom reads can occur - This option is correct. The TRANSACTION_REPEATABLE_READ level prevents dirty reads and non-repeatable reads, but phantom reads can still occur.

D. (d) Dirty reads, non-repeatable reads, and phantom reads are prevented - This option is incorrect. The TRANSACTION_REPEATABLE_READ level only prevents dirty reads and non-repeatable reads, but phantom reads can still occur.

Therefore, the answer is: C. (c) Dirty reads and non-repeatable reads are prevented; phantom reads can occur.

JSON is specifically designed as a lightweight data interchange format - it's used to serialize and transmit structured data between different systems, particularly between client and server in web applications. Unlike HTML (markup), DHTML (dynamic HTML), or SOAP (protocol with XML), JSON is purely a data representation format.

QTP supports parameterization across checkpoints (data-driven validation), test objects (dynamic property values), and database checkpoints (parameterized queries and expected results). This comprehensive parameterization enables flexible, data-driven testing.

DBD (Database Description) is the DL/I control block that contains the physical database description including segment layouts, field definitions, and access methods. It defines how data is physically stored.

A Dictionary object stores data as key-value pairs, where each unique key maps to a corresponding item or value. This is the fundamental data structure for associative arrays and maps across programming languages.

Active Screen captures and displays snapshots of your application at each step during the recording session. This feature helps testers visually verify what the application looked like at specific recording points, aiding in test maintenance and debugging.

Metadata extensions in Informatica are optional, not mandatory. They allow users to associate custom metadata with repository objects, but are not required for every transformation.