Database Management Systems

COM+ provides enterprise services like transactions, object pooling, and role-based security for .NET components through ServicedComponent. ADO is for data access, CLR is the runtime itself, MTS was the predecessor to COM+, and COM/DCOM is the underlying component technology but COM+ specifically adds these declarative services.

CIS (Center for Internet Security) provides widely-recognized benchmark standards for securing databases, operating systems, and other IT systems. These are configuration best practices used globally. Option A refers to the CIA triad (security principles), not benchmarks. Option C and D are not recognized standards organizations.

In Oracle Enterprise Datastage stages, the arraysize property controls how many rows are fetched in each batch from the database. A larger arraysize reduces network round-trips and improves performance. Options A, C, and D are not valid Oracle read performance tuning properties available through db options.

Bridges in DataStage are specifically designed translation mechanisms that allow importing metadata from external data modeling tools like Erwin and Rational Data Architect. The Connector wizard and Plug-In Meta Data facility are used for other types of imports, not for translating from external modeling tools.

A hierarchical system is typically defined as a system decomposed into a tree-like structure of nested subsystems and components. None of the options (596829, 596830, 596831) accurately describe this structure, making 'None of the above' (596832) the correct choice.

The bad file in Informatica captures rows rejected during the ETL process. Its first column serves as a row indicator that identifies why the entire row was rejected (such as data type errors, constraint violations, or truncation). This is distinct from column indicators, which would point to specific problematic column positions within a row. The row indicator helps diagnose the root cause of rejection.

Database connection parameters in MII are configured under Data Services -> Data Servers tab. This is where you define connection strings, drivers, and authentication details for SQL databases. The other tabs serve different purposes (buffer entries, security, SAP server configuration).

System.Data is the primary root namespace for ADO.NET database operations, and System.Data.SqlClient (misspelled with capital C in the option) represents the SQL Server data provider namespace. System.Data.DataSet is a class, not a namespace.

In ADO.NET, a DataView provides a customizable, filtered, and sorted view of data from a single DataTable. It doesn't wrap a DataSet, RowSet, DataRelation, or Recordset - it specifically works with DataTable contents to create different perspectives of the same data.

DataReader is designed for fast, forward-only, read-only data retrieval - ideal for populating read-only UI controls like dropdowns. It streams data efficiently without caching. DataAdapter fills DataSets, Command executes queries, Connection manages the connection, and Recordset is from classic ADO.

In QTP/UFT and VBScript, you use CreateObject to instantiate database connection objects like ADODB.Connection. For example: Set dbConn = CreateObject("ADODB.Connection"). This creates a COM object that can then connect to databases using connection strings. The other options (dbconnect, dbopen, CreateConn) are not standard VBScript or QTP commands for database connectivity.

A recovery scenario in QTP/UFT is designed to handle unexpected errors during test execution. It consists of three defined components: a trigger event that detects the error, recovery steps to handle the situation, and a post-recovery test run instruction that dictates how the test should proceed after recovery.

In HP QuickTest Professional (QTP/UFT), parameterization is highly flexible. Test engineers can parameterize checkpoints, database checkpoints, and test objects stored in the object repository to run tests with varying data inputs. Since all three components can be parameterized, the option selecting 1, 2, and 3 is correct.

Hibernate Session is a non-thread-safe object representing a single database transaction/unit of work and must not be shared. If multiple threads access a session concurrently, it causes race conditions and data corruption. Conversely, SessionFactory is thread-safe and designed for global, multi-threaded use.