SET 1 : PART-A
1. Best Description of a Database System:
c) Organized collection of data with software to manage it
2. Data vs Information:
b) Processed data with meaning
3. File System Approach:
b) Encourages redundancy
4. Major Problem with File Systems:
a) Low data security
5. Business Rules are used to:
b) Define data constraints and relationships
6. In Relational Database Models, data is organized in:
c) Tables consisting of rows and columns
7. Degrees of Data Abstraction does NOT include:
d) Operating System Level
8. Data about data:
Metadata
9. Entity is represented by:
Rectangle (In ER Diagrams)
PART-B
10. Components of Database:
Hardware: Storage devices, servers
Software: DBMS software, OS
Data: Actual stored data
Users: DBA, End-users
Procedures: Instructions for using the database
11. Data vs Information:
Data: Raw facts, unprocessed (e.g., numbers, names)
Information: Processed data with meaning (e.g., Reports, summaries)
12. File System with Example & Advantages:
Example: Storing files in directories (e.g., text files, spreadsheets)
Advantages: Simple to use, Suitable for small applications
Disadvantages: Redundancy Poor data security
13. Relational Database Model:
Data organized in Tables (Relations)
Rows = Records/Tuples
Columns = Attributes/Fields
Uses Primary Key, Foreign Key for relationships
14. Evaluation of Data Model & Degree of Data Abstraction:
Data Models: Hierarchical, Network, Relational, Object-oriented
Degrees of Abstraction:
Physical Level (Storage details)
Logical Level (What data is stored, relationships)
View Level (User interaction layer)
PART-C
15. What is a Database? Types with Examples:
Database: Organized data collection for easy access, management
Types:
Relational (e.g., MySQL, Oracle)
Hierarchical (e.g., IBM's IMS)
Network
Object-Oriented
Distributed model
Graph
Centralized
Personal
Enduser
16. Entity-Relationship (ER) Model:
Entities: Real-world objects (e.g., Student, Course)
Relationships: Associations between entities (e.g., Enrolls)
Attributes: Properties of entities (e.g., Student_Name)
ER Diagram Example:
Student —— Enrolls —— Course
17. Keys and Types with Examples:
Primary Key: Unique identifier (e.g., Student_ID)
Foreign Key: Links two tables (e.g., Student_ID in Enrollment table)
Candidate Key: All possible unique identifiers
Composite Key: Combination of fields to uniquely identify
Super Key: Superset of candidate key
Alternate key
SET 2 : PART - A
1. Difference between Data and Information:
b) Data is raw facts; information is processed, meaningful output
2. Database System primarily helps in:
c) Storing, managing, and organizing data efficiently
3. Represents entities in ER model:
c) Rectangle
4. Major problem with File Systems:
a) Low data security
5. In Relational Database Models, data is organized in:
c) Tables consisting of rows and columns
6. Degrees of Data Abstraction does NOT include:
d) Operating System Level
7. Data about data:
Metadata
8. A Primary Key must be:
Unique and Not Null
9. Entity is represented by:
Rectangle (In ER Diagram)
PART - B
10. DBMS Structure and Components:
Components:
Hardware (Physical devices)
Software (DBMS software)
Data (Stored data)
Users (DBA, End-users)
Procedures (Guidelines for database operations)
Structure:
Layers of abstraction: Physical, Logical, View
11. Integrity Rules and Types with Examples:
Entity Integrity: Primary key cannot be NULL
Referential Integrity: Foreign key must refer to valid primary key
Domain Integrity
User defined integity
Example:
Student Table (Student_ID as PK)
Enrollment Table (Student_ID as FK referring to Student Table)
12. File System with Example & Advantages:
Example: Files stored in directories, like .txt files, .csv files
Advantages:
Simple to implement
Easy for small datasets
Disadvantages:
Data redundancy
Poor data security
Difficult to manage relationships
13. Evolution of Data Models (Examples):
Hierarchical Model:
Data arranged in tree structure
Example: IBM's IMS system
Network Model:
More complex with many-to-many relationships
Example: CODASYL Database
Relational Model:
Data stored in tables (rows & columns)
Example: MySQL, Oracle, SQL Server
Object oriented Model
14. Codd's Rules for Relational Databases:
Proposed by E.F. Codd (12 rules to define a true RDBMS)
Examples of Rules:
Data must be stored in tables
Data independence
Integrity rules must be enforced
Logical data must be accessible via relational means
PART-C
15. What is a Database? Types with Examples:
Database: Organized data collection for easy access, management
Types:
Relational (e.g., MySQL, Oracle)
Hierarchical (e.g., IBM's IMS)
Network
Object-Oriented
Distributed model
Graph
Centralized
Personal
Enduser
16. Entity-Relationship (ER) Model:
Entities: Real-world objects (e.g., Student, Course)
Relationships: Associations between entities (e.g., Enrolls)
Attributes: Properties of entities (e.g., Student_Name)
ER Diagram Example:
Student —— Enrolls —— Course
17. Keys and Types with Examples:
Primary Key: Unique identifier (e.g., Student_ID)
Foreign Key: Links two tables (e.g., Student_ID in Enrollment table)
Candidate Key: All possible unique identifiers
Composite Key: Combination of fields to uniquely identify
Super Key: Superset of candidate key
Alternate key
