Database Management Systems

Performance monitoring is an ongoing operational activity in database administration, continuously tracking query performance, resource usage, and system health. The other options are one-time setup or design activities.

Security review occurs during the design phase when defining access controls, user permissions, and data security policies. The structure and storage phases focus on technical implementation, not security planning.

Metadata is data about data - it describes the structure, schema, and data dictionary but does not include actual user data values. Options A, B, C, and E all describe legitimate characteristics of metadata.

RDBMS procedural SQL extensions (PL/SQL, T-SQL) add programming constructs like conditionals and loops for procedural logic. Encryption, GUI widgets, threading, and network sockets are systems-level features outside SQL scope.

A mandatory 1:1 relationship often indicates insufficient attribute analysis - additional attributes may reveal why entities are separate or show they should be merged. This is a modeling smell suggesting incomplete analysis.

HTML tables are used to organize and display data in rows and columns, helping maintain proper formatting and structure on web pages. They were historically also misused for page layout before CSS became widely adopted. Option C describes this formatting purpose, though somewhat vaguely.

The dse.ldif file in directory servers contains the directory specific entry configuration including attribute indexes. This file stores backend configuration information for the directory service.

The dse.ldif file contains indexes for attributes in a Directory Server. LDIF (LDAP Data Interchange Format) files are used to store directory data, and dse.ldif specifically holds the backend configuration including attribute indexes that optimize search and lookup operations. Option A (99user.ldif) is typically for user-specific customizations, while options C and D are not standard LDIF configuration files for this purpose.

ETL lifecycle specifically includes Data Validation as a core task type. Data Mining, Report Generation, and Data Modeling are separate activities that occur outside the ETL lifecycle - Data Mining is analysis, Report Generation is downstream BI, and Data Modeling is a design phase activity.

A single Source qualifier transformation cannot pull data from multiple databases - it can only connect to one source at a time. To combine data from multiple databases, you would need multiple source qualifiers joined together using a Joiner transformation. This is a fundamental architectural constraint in ETL tools.

Enterprise Information Integration (EII) is fundamentally about the capability to access data from any source regardless of format or system - it provides unified access to heterogeneous data sources. The other options either describe unauthorized access (B), data silos (C), or remote manipulation (D), which are not the core purpose of EII.

ETL is fundamental to data warehousing and decision support systems, making it essential for high-performance decision support environments and Master Data Management hubs. It is not designed for OLTP systems, which require real-time transaction processing rather than batch-oriented extraction, transformation, and loading.

Business Intelligence encompasses all these aspects: the skills and technologies for decision-making (A), the architecture for decision support systems (B), and providing multi-temporal views of business operations (C). BI is a comprehensive discipline that integrates all these elements to support data-driven decision making.

A data warehouse has four key characteristics: it is subject-oriented (organized by major subject areas), integrated (consistent data standards), time-variant/temporal (captures historical changes over time), and non-volatile (data is read-only, not updated or deleted). Option D correctly lists all four properties.