Database Management Systems

Transactional replication is the correct answer because BlackBerry Enterprise Solution uses transactional replication to ensure data consistency across the database infrastructure. This type of replication replicates data transactions in real-time, which is essential for an enterprise messaging system where data integrity and synchronization are critical. Analytical processing is not a replication type, while merge and snapshot replication are less suitable for real-time enterprise messaging systems.

24 hours is correct because the BlackBerry State Database (BBSD.nsf) is programmatically configured to be deleted after 24 hours as part of automated maintenance and cleanup routines. This prevents the accumulation of stale state data and helps maintain database performance. The 24-hour window is a standard retention period for temporary state information in the BlackBerry infrastructure.

BBprofile.nsf is correct because this database file stores information about emails sent to the handheld device and is unique for each user in the BlackBerry system. The BBprofile.nsf file maintains user-specific profile data and message tracking information. Steadystate.nsf and BBSD.nsf serve different purposes (state database and other functions), making BBprofile.nsf the correct answer.

The Microsoft BlackBerry Enterprise Server (BES) configuration database is natively created on MS SQL Server (including MSDE/SQL Server Express). Oracle and SAP are not the default database platforms used for BES configuration storage.

BBSD.nsf is the BlackBerry Server Database, which is critical for BES operations. This database stores essential configuration, state, and operational data. While BBprofile.nsf stores user profiles, BBSD.nsf is the core system database required for BES to function.

The BlackBerry Enterprise Server architecture supports a single cluster setup for high availability and load balancing. While multiple servers can exist within that cluster, the fundamental design limits configuration to one cluster per BES deployment. This architectural constraint ensures stable and predictable server communication.

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.

The correct syntax is mysql_connect() with three parameters: server hostname, username, and password. Option D shows the correct parameter order, though the database name is actually a fourth optional parameter. Options A and B use incorrect syntax, while option C is missing the required connection parameters.

The WAREHOUSELOG table in the Tivoli Data Warehouse logs detailed information about export operations, including success counts and failure reasons like ODBC errors or timeouts. This is the definitive source for export statistics.

The tacmd command is primarily used for managing UNIX Log agents in IBM Tivoli Monitoring. It can verify agent status, configuration, and connectivity. TEPS (the portal) and database status are checked through other interfaces, not tacmd.

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.