Core database idea — self-describing data: Evaluate the statement: "A database is called self-describing because it contains a description of itself."

Introduction / Context: The term "self-describing" highlights a defining feature of modern DBMSs: metadata (data about data) stored within the database. This question probes whether you recognize catalogs/dictionaries as first-class parts of database systems.

Given Data / Assumptions:

• Relational DBMSs maintain system catalogs (also called data dictionaries).
• Catalogs store table definitions, column names and types, constraints, indexes, views, privileges, and other schema objects.
• Applications and DBAs query these catalogs to discover structure and enforce integrity and security.

Concept / Approach: A database is self-describing because its schema and related metadata are themselves stored as data that can be queried, secured, and managed. For example, INFORMATION_SCHEMA views in SQL standards or vendor-specific system tables expose definitions and constraints, making the system introspective and consistent.

Step-by-Step Solution:

Verification / Alternative check: Run queries like SELECT * FROM INFORMATION_SCHEMA.COLUMNS (or vendor equivalents) to retrieve column metadata; observe that results live inside the DBMS itself.

Why Other Options Are Wrong:

• Incorrect: Ignores the ubiquitous presence of catalogs/dictionaries.
• Only true for NoSQL/object: Relational systems pioneered this approach; it is not limited to a specific model.

Common Pitfalls: Confusing documentation (external) with metadata (internal). Assuming schemas exist only in DDL scripts; in reality, the DBMS persists and exposes them as data.

Final Answer: Correct