Question 1
1. Given the basic ER and relational models, which of the following is INCORRECT?
Question 2
2. Which of the following relational query languages have the same expressive power?
1. Relational algebra
2. Tuple relational calculus restricted to safe expressions
3. Domain relational calculus restricted to safe expressions
1. Relational algebra
2. Tuple relational calculus restricted to safe expressions
3. Domain relational calculus restricted to safe expressions
Answer: (4)
Relational algebra is a procedural query language where we input - relations and it yields relations as output. It provides method to get the result. It is performed recursively on a relation and the in between results are relations(output). Basic set of operations for the relational model. Relational calculus is a non - procedural query language. It provides the query to get result. Higher level declarative language for specifying relational queries. Tupple Relational Calculus operates on each tupple. Domain Relational Calculus operates on each column or attribute. Safe expression means fixed no. of tupple or column or attribute as a result But all of them has same expressive power. Just different ways to do so
Relational algebra is a procedural query language where we input - relations and it yields relations as output. It provides method to get the result. It is performed recursively on a relation and the in between results are relations(output). Basic set of operations for the relational model. Relational calculus is a non - procedural query language. It provides the query to get result. Higher level declarative language for specifying relational queries. Tupple Relational Calculus operates on each tupple. Domain Relational Calculus operates on each column or attribute. Safe expression means fixed no. of tupple or column or attribute as a result But all of them has same expressive power. Just different ways to do so
Question 3
3. What is the min and max number of tables required to convert an ER diagram with 2 entities and 1 relationship between them with partial participation constraints of both entities?
Answer: (3)
Maximum number of tables required is 3 in case of many to many relationships between entities. Minimum number of tables is 1 in case of unary relationship and total participation of atleast one entity. But in case of partial participation of both entities, minimum number of tables required is 2.
Maximum number of tables required is 3 in case of many to many relationships between entities. Minimum number of tables is 1 in case of unary relationship and total participation of atleast one entity. But in case of partial participation of both entities, minimum number of tables required is 2.
Question 4
4. Consider the join of a relation R with a relation S. If K has m tuples and S has n tuples, then the maximum and minimum sizes of the join respectively are:
Answer: (2)
When there is no foreign key constraint between two tables then the max and min number of tuples in their join is mn and 0 respectively
When there is no foreign key constraint between two tables then the max and min number of tuples in their join is mn and 0 respectively
Question 5
5. In RDBMS, different classes of relations are created using ___ technique to prevent modification anomalies
Answer: (4)
Functional dependency is a constraint that describes the relationship between attributes in a relation. Data integrity refers to the accuracy and consistency of data stored in a database, data warehouse, data mart or other construct. Referential integrity is a relational database concept, which states that table relationships must always be consistent. Normalization is a process of organizing the data in database to avoid data redundancy, insertion anomaly, update anomaly & deletion anomaly. 1NF, 2NF, 3NF and BCNF are types of normal forms
Functional dependency is a constraint that describes the relationship between attributes in a relation. Data integrity refers to the accuracy and consistency of data stored in a database, data warehouse, data mart or other construct. Referential integrity is a relational database concept, which states that table relationships must always be consistent. Normalization is a process of organizing the data in database to avoid data redundancy, insertion anomaly, update anomaly & deletion anomaly. 1NF, 2NF, 3NF and BCNF are types of normal forms
Question 6
6. Which symbol denote derived attributes in ER Model?
Answer: (2)
Question 7
7. Goals for the design of the logical scheme include
Answer: (4)
Question 8
8. Which one is correct w.r.t. RDBMS ?
1. primary key ⊆ super key ⊆ candidate key
2. primary key ⊆ candidate key ⊆ super key
3. super key ⊆ candidate key ⊆ primary key
4. super key ⊆ primary key ⊆ candidate key
1. primary key ⊆ super key ⊆ candidate key
2. primary key ⊆ candidate key ⊆ super key
3. super key ⊆ candidate key ⊆ primary key
4. super key ⊆ primary key ⊆ candidate key
Answer: (2)
primary key ⊆ candidate key ⊆ super key in RDBMS For more information Refer:DBMS | Keys in Relational Model (Candidate, Super, Primary, Alternate and Foreign)
primary key ⊆ candidate key ⊆ super key in RDBMS For more information Refer:DBMS | Keys in Relational Model (Candidate, Super, Primary, Alternate and Foreign)
Question 9
9. Let pk(R) denotes primary key of relation R. A many-to-one relationship that exists between two relations R1 and R2 can be expressed as follows :
1. pk(R2) → pk(R1)
2. pk(R1) → pk(R2)
3. pk(R2) → R1 ∩ R2
4. pk(R1) → R1 ∩ R2
1. pk(R2) → pk(R1)
2. pk(R1) → pk(R2)
3. pk(R2) → R1 ∩ R2
4. pk(R1) → R1 ∩ R2
Answer: (2)
Question 10
10. Relational database schema normalization is NOT for:
Answer: (1)
Relational database schema normalization is NOT for reducing the number of joins required to satisfy a query
Relational database schema normalization is for eliminating uncontrolled redundancy of data stored in the database
Relational database schema normalization is for eliminating number of anomalies that could otherwise occur with inserts and deletes
Relational database schema normalization is for ensuring that functional dependencies are enforced
Relational database schema normalization is NOT for reducing the number of joins required to satisfy a query
Relational database schema normalization is for eliminating uncontrolled redundancy of data stored in the database
Relational database schema normalization is for eliminating number of anomalies that could otherwise occur with inserts and deletes
Relational database schema normalization is for ensuring that functional dependencies are enforced
The term 'entity' belongs to ER model and the term 'relational table' belongs to relational model. A and B both are true. ER model supports both multivalued and composite attributes. (C) is false and (D) is true. In Relation model, an entry in relational table can can have exactly one value or a NULL