Scribd
Upload
13 views4 pages

Database Engineering Complete Answers Fixed

The document is a question bank on database engineering covering key concepts such as types of keys, file-based systems, data abstraction levels, database system purposes, and the role of a Database Administrator. It also includes topics on database design, E-R models, normalization, and anomalies. Additionally, it discusses functional dependencies and their importance in maintaining database consistency.

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
13 views4 pages

Database Engineering Complete Answers Fixed

The document is a question bank on database engineering covering key concepts such as types of keys, file-based systems, data abstraction levels, database system purposes, and the role of a Database Administrator. It also includes topics on database design, E-R models, normalization, and anomalies. Additionally, it discusses functional dependencies and their importance in maintaining database consistency.

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 - Question Bank with Answers

Unit 1: Introduction to Databases

1. List & explain the different types of keys.


- Primary Key: Uniquely identifies a record in a table.
- Candidate Key: A set of attributes that can uniquely identify a record.
- Super Key: A superset of a candidate key.
- Foreign Key: Refers to a primary key in another table.
- Composite Key: A combination of two or more columns used as a key.

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


- A file-based system stores data in separate files without a central database.
- Limitations:
- Data redundancy: Same data is stored in multiple places.
- Lack of consistency: No single control over data updates.
- Difficult data retrieval: Searching is inefficient.
- No concurrent access: Multiple users cannot access files simultaneously.

3. Explain the levels of data abstraction and differentiate schema & instance.
- Physical Level: How data is physically stored.
- Logical Level: Structure and relationships of data.
- View Level: Different ways data is viewed by users.
- Schema: Defines the database structure.
- Instance: The actual data present in the database.

4. What is the purpose of a database system?


- Stores, manages, and retrieves data efficiently.
- Eliminates redundancy and maintains data integrity.

5. Functions of a Database Administrator (DBA).


- Database design, security, performance monitoring, backup & recovery.
6. What is Relational Algebra? Discuss its operations.
- A formal system for database queries.
- Operations: Selection, Projection, Union, Cartesian Product, Join.

7. Discuss different types of keys with examples.


- Primary Key: Ensures uniqueness (e.g., Student_ID in Student table).
- Candidate Key: Possible choices for the primary key.
- Super Key: A set including a candidate key.
- Foreign Key: References another table.

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

1. Draw ER Diagrams for Bank, Insurance, and University databases.


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

2. Define Normalization & discuss 1NF.


- Normalization: Organizes data to reduce redundancy.
- 1NF (First Normal Form): Removes repeating groups and ensures atomic values.

3. Explain Reduction of ER Diagram to Relational Schema.


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

4. Notations Used in ER Diagrams.


- Rectangle: Entity.
- Oval: Attribute.
- Diamond: Relationship.
- Line: Connection between entities and relationships.

5. Types of Attributes in a Database.


- Simple: Single atomic value.
- Composite: Divided into sub-parts.
- Derived: Computed from another attribute.
- Multivalued: Can have multiple values.

6. Mapping Cardinalities in ER Diagrams.


- One-to-One (1:1): One entity related 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 & BCNF with Examples.


- 2NF: Removes partial dependency.
- 3NF: Removes transitive dependency.
- BCNF: Stronger version of 3NF.

8. What is Anomaly? Explain Insertion, Deletion & Update Anomalies.


- Insertion Anomaly: Cannot insert data without unnecessary fields.
- Deletion Anomaly: Deleting a record removes other important data.
- Update Anomaly: Changing data requires multiple updates.

9. Explain Armstrong's Axioms.


- Rules used to derive functional dependencies.

10. State & Describe Participation Constraints.


- Total Participation: All entities participate in the relationship.
- Partial Participation: Some entities may not participate.

11. What are Functional Dependencies? How do they relate to Normalization?


- A functional dependency shows the relationship between attributes.
- Helps in decomposing tables during normalization.

12. How does Normalization Improve Database Consistency?


- Eliminates redundancy.
- Maintains data integrity and consistency.

You might also like