Database Management Systems

Pull mode information delivery relies on users actively requesting reports or queries, such as ad hoc queries, prestored reports, and OLAP analyses, rather than receiving pushed notifications.

Master Data Management (MDM) is specifically designed to create and maintain a single, consistent view of an organization's critical data entities (like customers, products, suppliers) across all systems and applications. Data Quality Management focuses on improving data accuracy, Metadata Management manages data about data, and Data Security Management protects data access - none of these specifically create unified reference views.

ETL (Extract, Transform, Load) is recommended for large data volumes with low quality because transformation happens before loading, allowing early error detection and correction. ELT loads raw data first then transforms it, which is better for cloud environments with good data quality. ELTL is not a standard pattern. EII (Enterprise Information Integration) provides virtual views without physical data movement.

Registry style MDM maintains a centralized index or registry of master data without physically consolidating all records. This allows real-time access to reference data across systems. Consolidation physically merges data, Coexistence maintains separate copies with synchronization, and Transaction style supports real-time transactions but doesn't provide centralized reference in the same way.

Report bursting generates multiple personalized report segments from a single report execution, which minimizes database queries compared to running reports separately for each user. It does not involve multiple execution of the same report. By delivering only relevant sections to each recipient, it actually reduces network traffic rather than increasing it.

The Staging Area is a temporary storage location where data extracted from source systems is held before transformation and loading into the data warehouse. It allows for ETL processes to work without impacting source systems, enables data quality checks, and provides a recovery point. Data Marts are subsets of data warehouses. ODS is for operational reporting.

ODS (Operational Data Store) is designed to be volatile, meaning data can be updated, deleted, or modified frequently. This volatility is what makes it suitable for operational reporting and tactical decision-making. Data Warehouses, in contrast, are non-volatile (data is not updated or deleted once loaded). The statement claims ODS is non-volatile, which is false.

ODS supports detailed, current operational data that enables detailed decision making at the operational level. It provides operational reporting capabilities for day-to-day business monitoring. Drill-through from data warehouses to ODS is a common pattern for accessing detailed transactional data. Therefore, ODS provides all these capabilities.

Active data warehouse architecture uses a centralized, integrated approach where data marts are derived from the same warehouse and share dimensions/facts, not kept separate and segregated. The statement actually describes the Independent Data Mart architecture, where each mart operates as an isolated silo. Active warehouses emphasize consistency and integration across business units.

ELT (Extract, Load, Transform) is recommended for small and medium data volumes with good data quality and off-peak loads because it leverages the target system's processing power after loading. ETL transforms before loading, adding overhead. ELTL and EII are not standard data integration patterns in this context.

DSPOBJLCK (Display Object Locks) is the correct IBM i command to show active locks on any object. DSPLCK is not a valid command, DSPSYSLCK would display system-level locks (not object-specific), and DSPACTLCK is not a standard command.

ASRA is a CICS transaction abend that occurs when a program encounters a data exception or program check, such as SOC7 (data exception) or SOC4 (storage violation). Option A would cause an AEY3 or AEY9 abend, while option C is an ASRA timeout abend (different type). ASRA specifically means the program crashed.

In DB2, locks can be obtained at the tablespace level, which is a logical grouping of tables. Locking at the tablespace level provides concurrency control for data managed within that tablespace. Options like directory, bufferpool, and column are not lockable objects in DB2.

The DB2 precompiler processes embedded SQL statements in host language source code and replaces them with CALL statements to DB2 runtime services. This transformation allows the host language compiler to process the code without needing to understand SQL syntax directly.

A Database Request Module (DBRM) contains the SQL statements extracted from the source program by the precompiler, along with some additional control information.