Operational artifacts of a DBMS: Which two internal files are directly used during database operation to ensure metadata access and recoverability?

Introduction / Context:
Database Management Systems rely on internal structures to operate reliably. Two critical artifacts are the data dictionary and the transaction log—used respectively for metadata management and durability/recovery.

Given Data / Assumptions:

• The DBMS must know table/column definitions, constraints, and relationships.
• The DBMS must record changes for recovery and rollback.
• The question asks for the pair that supports both needs.

Concept / Approach:
The data dictionary (system catalog) stores metadata: schemas, indexes, privileges. The transaction log records each change so the DBMS can commit, roll back, and recover after failures. Languages and utilities are interfaces; the dictionary and log are the operative internal files.

Step-by-Step Solution:

Verification / Alternative check:
Crash recovery replays or rolls back transactions using the log; query planners read statistics and definitions from the dictionary.

Why Other Options Are Wrong:

• Language options: SQL DML/QL are user interfaces, not internal files.
• Utilities: tools, not operational storage artifacts.
• Data dictionary and query language: only one internal file; the language is not a file.

Common Pitfalls:
Confusing the DBMS's external interfaces with its internal operational storage structures.

Final Answer:
Data dictionary and transaction log