Database Management Systems

PMON (Process Monitor) recovers failed server processes by rolling back their uncommitted transactions and releasing locks and resources they held. PMON also monitors other background processes and restarts them if they fail. Unlike SMON, PMON handles individual process recovery, not instance-wide recovery.

For consignment materials, the purchasing info record category must be explicitly defined and created as 'Consignment' rather than 'Standard'. Standard info records are used for normal purchasing processes. Using only Standard would fail to track consignment stock and settlement correctly, making the statement False.

MDM stands for Master Data Management, which is a methodology and technology for managing an organization's critical data to ensure consistency, accuracy, and stewardship. In SAP environments, MDM is used to maintain consistent master data across systems. Options A, B, and C incorrectly suggest MDM stands for variations of Manager or is specific to Material - it's a broader concept covering all master data domains.

The ReceiveTimeout property controls session lifetime in WCF - if no message is received within this timeout period, the session is considered closed and the channel faults. Unlike SendTimeout (outgoing) or OpenTimeout (connection establishment), this specifically governs incoming message tolerance.

Informatica PowerCenter, IBM DataStage, and Ab Initio are all enterprise-grade ETL tools used for data integration and transformation. Each provides visual designers, transformation libraries, and connectivity to diverse data sources.

Data warehouses are specifically designed to store and analyze historical data over time, unlike operational databases that handle current transaction processing. This temporal dimension enables trend analysis, reporting, and business intelligence.

An ETL mapping includes source definitions (where data comes from), target definitions (where data goes), and transformations (how data is modified in between). All three components are essential parts of a complete data flow. None of these alone constitute a complete mapping.

A data warehouse is a specialized database designed for query and analysis rather than transaction processing. It consolidates data from multiple sources into a single repository optimized for reporting and analytics. While it uses database technology, 'database' is the most accurate answer among the options given.

A data mart is a targeted, subject-oriented subset of a data warehouse designed to serve a specific business line, department, or user group. It is not a variable, making the other options incorrect.

Datamarts are typically classified into two main types: Independent datamarts (created directly from operational systems without a data warehouse) and Dependent datamarts (created from a central data warehouse). Some sources mention a third type (Hybrid), but the standard answer in most ETL/data warehousing contexts is 2 types.

Data warehouses are specifically designed to store historical data for long-term trend analysis and decision-making. They are optimized for read-heavy analytical queries, not the frequent read-write operations of operational databases. Operational data is stored in OLTP systems, while data warehouses archive the historical snapshots.

Data warehouses use denormalized schemas (star and snowflake schemas) which reduce the number of joins needed for queries. They also create numerous indexes to optimize query performance on large datasets. Both fewer joins and more indexes are key architectural advantages that enable fast analytical queries.