DBMS Unit Wise Question Bank

UNIT 1 — Introduction to DBMS & Data Models (Detailed

Answers)

2-Mark Questions

1. Define DBMS.
A Database Management System (DBMS) is system software that
enables users to define, create, maintain and control access to
databases. It provides mechanisms for storage, retrieval, update, and
administration of data while enforcing integrity, security, concurrency
control, and recovery.

2. What is data independence?

Data independence is the ability to change the schema at one level of
the database system without affecting the schema at the next higher
level.

 Logical data independence: Changes to conceptual schema

(e.g., adding attributes, tables) do not affect external views or
application programs.
 Physical data independence: Changes to internal/physical
storage (e.g., indexing, file organization) do not affect
conceptual schema or queries.

3. List any four characteristics of a database.

1. Persistent storage — Data persists beyond program execution.

2. Reduced redundancy — Centralized control minimizes
duplicate data.
3. Data integrity — Constraints enforce correctness.
4. Concurrent access — Multiple users can safely access data.
(Also: security, backup & recovery, query capability, data
independence.)

4. Who are database users?

 End users — Run queries and applications (casual, naive,

sophisticated).
  Application programmers — Write programs that access the
DB.
 Database designers — Define conceptual schemas.
 Database administrators (DBA) — Manage the DBMS and
operations.
 System analysts and operators may also interact with DBMS.

5. Define data model.

A data model is an abstract formalism for describing data, data
relationships, data semantics and constraints. Examples: relational
model (tables), hierarchical (tree), network (graph), object-based
(objects/attributes/methods).

6. What is the difference between logical and physical schema?

 Logical schema: The conceptual structure of the database —

entities, attributes, tables, relationships — independent of how
data is stored.
 Physical schema: The actual storage structures and file
organization on disk (pages, indices, hashing), describing how
data is physically stored and accessed.

7. Define instance and schema.

 Schema: The overall design/structure of the database (tables,

columns, data types, constraints). Usually stable over time.
 Instance: A snapshot of the data in the database at a particular
moment (the actual rows/records stored now).

4-Mark Questions

1. Explain the 3-tier architecture of DBMS.

Three levels (ANSI/SPARC):

1. External (View) Level — Each user or application sees a

tailored view of the database (subset, formatted). It hides
irrelevant data and provides security.
 2. Conceptual (Logical) Level — A unified, community view of
the entire database: all entities, attributes, relationships, and
constraints. Hides physical details.
3. Internal (Physical) Level — Describes physical storage
structures (files, indexes, record placement).

How it helps: abstraction, multiple views, data independence (logical

& physical), separation of concerns, easier maintenance.

2. Describe the need for a DBMS over file systems.

Problems in file-based systems: data redundancy & inconsistency,
difficulty in data sharing, poor data integrity & security, no
concurrency control, limited recovery support, application-program
dependence on file formats.
DBMS advantages: centralized data management, reduced
redundancy, data integrity, recovery & backup, concurrency control,
access control & security, complex query support (SQL), data
independence. Provide an example: in a file system adding a new
field requires rewriting programs; DBMS isolates such changes.

3. Explain hierarchical and network data models (with diagrams

— describe in text).

 Hierarchical model: Organizes data in a tree structure. Each

record has a single parent (except root) and possibly many
children. Good for 1:N relationships (e.g., organization chart).
Traversal is top-down. Limitations: rigid structure, difficulty
representing many-to-many relationships.
o Diagram (text): Root → Child1 → Grandchild ... (single
parent).
 Network model: Generalizes hierarchical model by allowing a
record to have multiple parents; forms a directed graph. It
supports many-to-many relationships using explicit set types.
More flexible than hierarchical but complex to design and
query.
o Diagram (text): Node A connected to Nodes B and C;
Node B also connects to C — graph-like.
4. Short note on DBA and responsibilities.
DBA (Database Administrator) is responsible for the overall
management of the DBMS and database environment. Key duties:
schema definition and evolution, access control and user accounts,
backup & recovery planning, performance tuning, capacity planning,
installing/updating DBMS software, enforcing integrity/security
policies, and coordinating with developers/operations.

5. Explain the view of data in DBMS.

DBMS presents data at multiple abstraction levels: physical (storage),
logical (conceptual schema/tables), and external (user views). Views
hide complexity and deliver different representations to different
users. Views enforce security and simplify application development.

6-Mark Questions

1. Explain the various types of data models with examples.

a) Relational model: Data represented as relations (tables) with
tuples (rows) and attributes (columns). Integrity via keys and
constraints. Example: SQL databases (MySQL, PostgreSQL).
b) Hierarchical model: Tree-structured records with parent-child
relationships (IBM IMS). Example: file directory trees.
c) Network model: Graph-structured, supports many-to-many via
sets (IDMS). Example: telecommunications routing data.
d) Object-based models: Combine data and behavior (objects with
methods), support inheritance and encapsulation. Example:
OODBMS used in CAD/CAM systems.
e) Entity-Relationship (ER) model: Conceptual modeling used in
design: entities, relationships, attributes; not an implementation model
but used to derive logical schemas.
Comparison/Usage: Relational is general-purpose,
hierarchical/network used in legacy and specialized systems, object-
based useful when complex objects & behavior must be stored.

2. Discuss DBMS architecture in detail with neat diagram.

Components:
  Query Processor: Parses, optimizes, and translates queries
(SQL) into execution plans. Includes DML compiler, query
optimizer, and query execution engine.
 Storage Manager: Manages storage structures, buffer
management, file I/O, pages, and segments.
 Transaction Manager: Provides concurrency control, recovery
and ensures ACID properties.
 Catalog/Metadata: Stores schema definitions and system data.
 Authorization & Security Manager: Controls access.
 Utilities: Backup, import/export, performance monitors.

Three-tier architecture (client → application server → DBMS) or

two-tier (client-server). The diagram typically shows user applications
at top, query processor & transaction manager middle, and storage
manager & files at bottom.

3. Compare relational model with hierarchical and network

models.

 Structure: Relational uses tables (simple, uniform), hierarchical

uses trees, network uses graphs.
 Flexibility: Relational more flexible for ad hoc queries;
hierarchical is rigid; network intermediate.
 Ease of use: Relational is easier due to SQL; hierarchical and
network require procedural navigation.
 Relationship support: Relational supports many relationships
through joins and foreign keys; hierarchical struggles with
many-to-many; network supports many-to-many but complex.
 Redundancy & integrity: Relational supports declarative
constraints (PK, FK); hierarchical/network have limited built-in
declarative integrity.