Scribd
Upload
14 views

Database Engineering Detailed Answers Fixed

The document is a detailed question bank on Database Engineering covering key concepts such as types of keys, file-based systems, data abstraction levels, and the purpose of database systems. It includes topics on database design, ER models, normalization, and anomalies in databases, providing definitions, examples, and explanations for each concept. Additionally, it outlines the functions of a Database Administrator and the importance of normalization in maintaining data integrity.

Uploaded by

34Audumbar Sawant
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
14 views

Database Engineering Detailed Answers Fixed

The document is a detailed question bank on Database Engineering covering key concepts such as types of keys, file-based systems, data abstraction levels, and the purpose of database systems. It includes topics on database design, ER models, normalization, and anomalies in databases, providing definitions, examples, and explanations for each concept. Additionally, it outlines the functions of a Database Administrator and the importance of normalization in maintaining data integrity.

Uploaded by

34Audumbar Sawant
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Database Engineering - Detailed Question Bank with Answers

Unit 1: Introduction to Databases

1. List and explain the different types of keys.


- Primary Key: Uniquely identifies each record (Example: Student_ID).
- Candidate Key: A set of attributes that can act as a primary key.
- Super Key: A superset of a candidate key.
- Foreign Key: Links a table to another table's primary key.
- Composite Key: Combines two or more columns as a key.

2. What is a File-Based System? List its limitations.


- A file-based system stores data in multiple separate files.
- Limitations:
- Data Redundancy: Data duplication across files.
- Inconsistency: No single control over updates.
- Difficult Data Retrieval: Searching is slow.
- No Concurrent Access: Cannot support multiple users efficiently.

3. Explain the levels of data abstraction and differentiate schema and instance.
- Physical Level: Lowest level, defines physical storage.
- Logical Level: Defines relationships between tables.
- View Level: How users see the data.
- Schema: Defines database structure.
- Instance: The actual stored data at a given time.

4. Schema Diagram for a University Database (Example)


- Entities: Student, Course, Professor.
- Relationships: Enrolled, Teaches.
- Primary Keys: Student_ID, Course_ID.

5. Purpose of a Database System


- Organizes, manages, and retrieves data efficiently.
- Reduces redundancy and ensures data consistency.

6. Functions of a Database Administrator (DBA)


- Designing the database.
- Managing security and access control.
- Performance monitoring.
- Backup and recovery.

7. Relational Algebra and Operations


- A mathematical way of handling queries in databases.
- Operations:
- Selection (sigma)
- Projection (pi)
- Union
- Cartesian Product
- Join

8. Types of Keys with Examples


- Primary Key: Student_ID (ensures uniqueness).
- Candidate Key: Student_ID, Email (both can be primary keys).
- Super Key: (Student_ID, Name) (Includes more attributes).
- Foreign Key: Course_ID in the Enrollment table (references Course table).

Unit 2: Database Design (E-R Model and Normalization)

1. ER Diagrams for Bank, Insurance, and University Databases.


- Bank: Entities - Customer, Account, Loan.
- Insurance: Entities - Policyholder, Agent, Policy.
- University: Entities - Student, Course, Professor.

2. Normalization and 1NF


- Normalization: Organizing tables to remove redundancy.
- 1NF (First Normal Form): No duplicate rows, all columns contain atomic values.

3. Reduction of ER Diagram to Relational Schema


- Convert entities to tables.
- Convert relationships using foreign keys.

4. ER Diagram Notations
- Rectangle: Entity.
- Oval: Attribute.
- Diamond: Relationship.
- Line: Relationship connection.

5. Types of Attributes
- Simple: Atomic values (Example: Name, Age).
- Composite: Divided into sub-parts (Example: Full Name -> First Name, Last Name).
- Derived: Computed from another attribute (Example: Age from DOB).
- Multivalued: Can have multiple values (Example: Phone Numbers).

6. Mapping Cardinalities in ER Diagrams


- One-to-One (1:1): One entity relates to one other.
- One-to-Many (1:M): One entity relates to multiple.
- Many-to-Many (M:N): Multiple entities relate to multiple.

7. 2NF, 3NF and BCNF with Examples


- 2NF: Removes partial dependency.
- 3NF: Removes transitive dependency.
- BCNF: Stricter version of 3NF, ensuring no partial dependency.

8. Anomalies in Databases
- Insertion Anomaly: Cannot add data without unnecessary fields.
- Deletion Anomaly: Removing one record affects other important data.
- Update Anomaly: Changing a value requires multiple updates.
9. Armstrong's Axioms
- Rules used to derive functional dependencies.

10. Participation Constraints


- Total Participation: Every entity must participate in the relationship.
- Partial Participation: Some entities may not participate.

11. Functional Dependencies and Normalization


- Helps identify redundant data and guides normalization.

12. How Normalization Improves Consistency


- Reduces redundancy.
- Maintains data integrity.

You might also like