Database Management Systems

When an archive database is created in Lotus Notes, it receives a completely NEW replica ID - it is not a true replica of the original database. Archive databases are independent copies with their own identity in the replication system. This is why archived mail doesn't replicate back to the original mail file automatically.

In Lotus Notes, .nsf (Notes Storage Facility) is the standard file extension for database files. Option D (.ntf) is for template files, and .id files store user security information, not databases.

By default, RMAN (Recovery Manager) in Oracle 11g does not back up committed undo data. This is the expected behavior because undo data is primarily used for rollback and read consistency, and backing it up is not necessary for standard recovery scenarios. Therefore, the statement is true, making option A correct.

The Shared Pool in Oracle SGA contains the Library Cache (which stores parsed SQL statements and PL/SQL code) and Data Dictionary Cache (which stores data dictionary rows). Data Buffer Cache is a separate SGA component used for caching data blocks from disk, not part of Shared Pool. SQL buffer cache is not a standard Oracle memory component.

RMAN (Recovery Manager) uses the Large Pool for memory-intensive operations like backups and recovery. The Large Pool is designed for large memory allocations that don't compete with the Shared Pool, preventing performance degradation during RMAN operations. Shared Pool and Java Pool serve different purposes.

Database locks are used to manage concurrent access and maintain data integrity when multiple users try to access the same data simultaneously. Locks prevent conflicts like lost updates or inconsistent reads by serializing access to shared resources. They're not meant for security (protecting from attacks) or system maintenance.

Scan is used to produce intermediate summary records because it can read all input records and generate summary output without requiring grouping or aggregation logic. Sort is for ordering, Rollup is for grouped summaries, and Aggregate is for similar grouped operations - Scan is the appropriate choice for simple intermediate summaries.

Demographic files contain personal information about individuals such as name, address, age, gender, and contact details. Account details and transaction details are stored in separate financial systems and databases, not in demographic files. Option D is incorrect because account details are not demographic data.

In specific enterprise database architecture contexts, CMHDB serves as a customer information repository (often storing customer history data). The distractors incorrectly define it as the database administration team itself, a payment transaction system, or a global new account generator system, which represent different components.

CMHDB commonly uses DB2 as its database storage system. DB2 is IBM's relational database product commonly used in mainframe and enterprise environments. VSAM, IMS, and IDMS are alternative database/storage technologies but DB2 is the standard for CMHDB.

The CMHDB process does not store data in Oracle, IMS, or IDMS databases directly. It likely uses a different database system or storage mechanism altogether, hence None of the above is correct. This question specifically refers to the CMHDB process storage, not general CMHDB data storage.

For DB2 testing, CMHDB uses tables in the PDEV environment. PDEV likely stands for Production Development or a parallel development environment used for testing DB2-related functionality. EPRD, WROC, and LDEV are not the correct table environments for DB2 testing.

CRD_PROD_LOOKUP (Card Product Lookup) is the CMHDB table that stores product-level information. This table name directly indicates its purpose - looking up card product details. The other tables (MARKET_LOOKUP, CUST_LOOKUP, CM_LOOKUP) serve different purposes for market, customer, and credit management lookups respectively.