Mock Quiz Hub

Time: 00:00

Quiz

Navigate through questions using the controls below

Question 1 of 60 Quiz ID: q1

What is the primary purpose of the Entity-Relationship (E-R) Model?

To optimize SQL query performance

To provide a graphical representation of the logical database structure

To define user authorization levels

To handle database transaction concurrency

Question 2 of 60 Quiz ID: q2

An object that exists and is distinguishable from other objects in a database is called a(n):

Attribute

Entity

Entity Set

Relationship

Question 3 of 60 Quiz ID: q3

A set of entities of the same type that share the same properties is known as a(n):

Attribute Group

Entity Collection

Entity Set

Relationship Cluster

Question 4 of 60 Quiz ID: q4

What is an association among several entities called?

Attribute

Entity Set

Relationship

Domain

Question 5 of 60 Quiz ID: q5

A relationship set is a mathematical relation among n entities where:

n must always be 2

n can be 2 or more (n ≥ 2)

n must be an odd number

n is always 1

Question 6 of 60 Quiz ID: q6

Which of the following is TRUE about attributes of a relationship set?

A relationship set cannot have attributes.

Attributes describe the properties of the entities involved, not the relationship itself.

An attribute can be a property of the relationship set itself.

Relationship set attributes must always be composite.

Question 7 of 60 Quiz ID: q7

What is the degree of a relationship set that involves three entity sets?

Binary

Ternary

Quadratic

Primary

Question 8 of 60 Quiz ID: q8

Which of the following best describes a 'derived' attribute?

An attribute that must have multiple values

An attribute whose value can be calculated from other attributes

An attribute that is part of a composite key

An attribute that is the primary key of a weak entity set

Question 9 of 60 Quiz ID: q9

An attribute that can be split into smaller, component attributes is called a:

Multivalued Attribute

Derived Attribute

Composite Attribute

Discriminator Attribute

Question 10 of 60 Quiz ID: q10

Mapping cardinality constraints express:

The number of attributes an entity can have

The number of entities to which another entity can be associated via a relationship set

The order in which entities are stored physically

The data type constraints for primary keys

Question 11 of 60 Quiz ID: q11

In a 'one-to-many' relationship from entity set A to B, an entity in A can be associated with:

At most one entity in B

Many entities in B

Exactly one entity in B

No entities in B

Question 12 of 60 Quiz ID: q12

A minimal super key, meaning no subset of it is a super key, is called a:

Primary Key

Foreign Key

Candidate Key

Partial Key

Question 13 of 60 Quiz ID: q13

The combination of primary keys of the participating entity sets forms a __________ of a relationship set.

Foreign Key

Weak Key

Super Key

Discriminator Key

Question 14 of 60 Quiz ID: q14

Why might an attribute in an entity set be considered redundant?

If it is a composite attribute

If it is a derived attribute

If the information it holds is already represented by a relationship to another entity set

If it is part of the primary key

Question 15 of 60 Quiz ID: q15

In an E-R Diagram, what shape represents a relationship set?

Rectangle

Diamond

Ellipse

Double Rectangle

Question 16 of 60 Quiz ID: q16

How is a multivalued attribute typically represented in an E-R diagram?

With a double ellipse

With a dashed ellipse

With an ellipse inside another ellipse

It is not represented

Question 17 of 60 Quiz ID: q17

What does a directed line (→) drawn between a relationship set and an entity set signify?

Many

One

Total Participation

Partial Participation

Question 18 of 60 Quiz ID: q18

What does a double line connecting an entity set to a relationship set represent?

One-to-one cardinality

Many-to-many cardinality

Total participation

A weak entity set

Question 19 of 60 Quiz ID: q19

An entity set that lacks a primary key and depends on another entity set for its existence is a:

Strong Entity Set

Parent Entity Set

Weak Entity Set

Identifying Entity Set

Question 20 of 60 Quiz ID: q20

The set of attributes that distinguishes among all the entities of a weak entity set is called the:

Super Key

Foreign Key

Discriminator (Partial Key)

Primary Key

Question 21 of 60 Quiz ID: q21

How is the primary key of a weak entity set formed?

It is the same as the primary key of its strong entity set.

It is just its own discriminator.

It is the combination of the primary key of its strong entity set and its own discriminator.

Weak entity sets do not have a primary key.

Question 22 of 60 Quiz ID: q22

In an E-R diagram, how is the identifying relationship for a weak entity set depicted?

With a single diamond

With a double diamond

With a dashed diamond

With a colored diamond

Question 23 of 60 Quiz ID: q23

When converting an entity set with a composite attribute to a relational schema, what happens?

The composite attribute is stored as a single column.

A separate table is created for the composite attribute.

Each component attribute of the composite attribute becomes a separate column in the table.

The composite attribute is ignored as it is not a simple attribute.

Question 24 of 60 Quiz ID: q24

How is a multivalued attribute of an entity set represented in the relational schema?

It is added as a single column in the entity's table, storing all values in a list.

It is ignored and not represented in the schema.

A new separate table is created, containing the primary key of the entity and the multivalued attribute.

It is converted into a derived attribute.

Question 25 of 60 Quiz ID: q25

For a many-to-many relationship set, how is it typically represented in the relational schema?

By adding a foreign key to one of the participating entity tables.

By adding foreign keys to both participating entity tables.

By creating a new separate table that includes the primary keys of the participating entity sets as foreign keys.

It does not require explicit representation if it has no attributes.

Question 26 of 60 Quiz ID: q26

A many-to-one relationship set that is total on the many-side can be represented more efficiently by:

Creating a separate table for the relationship

Adding an extra attribute (foreign key) to the table schema for the 'many' side entity set

Adding an extra attribute to the table schema for the 'one' side entity set

Using a ternary relationship instead

Question 27 of 60 Quiz ID: q27

The process of defining subgroupings within an entity set that are distinctive from other entities is called:

Generalization

Specialization

Aggregation

Normalization

Question 28 of 60 Quiz ID: q28

The process of combining multiple entity sets into a single, higher-level entity set based on common features is called:

Specialization

Generalization

Aggregation

Reduction

Question 29 of 60 Quiz ID: q29

What concept allows a lower-level entity set to inherit all the attributes and relationship participation of a higher-level entity set?

Polymorphism

Encapsulation

Attribute Inheritance

Cardinality Limitation

Question 30 of 60 Quiz ID: q30

A constraint where an entity can belong to only one lower-level entity set within a generalization is known as:

Overlapping

Disjoint

Total

Partial

Question 31 of 60 Quiz ID: q31

A constraint where an entity must belong to at least one lower-level entity set within a generalization is known as:

Overlapping

Disjoint

Total Completeness

Partial Completeness

Question 32 of 60 Quiz ID: q32

What is the main purpose of aggregation in E-R modeling?

To combine attributes into a composite attribute

To treat a relationship set as an entity set for the purpose of participating in another relationship

To create a weak entity set

To enforce total participation constraints

Question 33 of 60 Quiz ID: q33

When converting a specialization to relational schemas using Method 1, what is a potential drawback?

It leads to storage of redundant data for inherited attributes.

Retrieving information about a subclass entity requires accessing both the subclass and superclass tables.

It cannot represent overlapping specializations.

It violates foreign key constraints.

Question 34 of 60 Quiz ID: q34

When converting a specialization to relational schemas using Method 2, what is a potential drawback?

It requires complex SQL queries for insertion.

It cannot represent attribute inheritance.

It may store common attributes redundantly for an entity that belongs to multiple subclasses.

It cannot represent disjoint constraints.

Question 35 of 60 Quiz ID: q35

Which of the following is a key E-R design decision?

Choosing the programming language for the application

Deciding whether a concept is best represented as an entity set or an attribute

Selecting the hardware for the database server

Determining the user interface layout

Question 36 of 60 Quiz ID: q36

In the context of the provided university E-R diagram, what is the likely cardinality of the 'advisor' relationship?

One instructor advises one student

One instructor advises many students, one student has one advisor

One instructor advises many students, one student has many advisors

Many instructors advise many students

Question 37 of 60 Quiz ID: q37

In the 'section' weak entity set, why is 'course_id' not explicitly stored as an attribute according to the ideal design?

It is a derived attribute.

It is redundant because it is implicit in the identifying relationship with the 'course' entity set.

It is a composite attribute.

It is represented as a multivalued attribute instead.

Question 38 of 60 Quiz ID: q38

Looking at the Car Insurance E-R diagram (Ex1), what is the cardinality of the 'owns' relationship?

One customer owns one car

One customer owns many cars, one car is owned by one customer

One customer owns many cars, one car is owned by many customers

Many customers own many cars

Question 39 of 60 Quiz ID: q39

In the SLPL Team E-R diagram (Ex2), the 'season_score' attribute of 'player' is marked with '()'. This most likely indicates it is a:

Multivalued Attribute

Composite Attribute

Derived Attribute

Discriminator Attribute

Question 40 of 60 Quiz ID: q40

According to the summary, which non-structural aspect significantly influences physical database design?

The choice of E-R notation (Chen vs. UML)

The cost of enforcing data constraints

The number of entity sets in the diagram

The number of composite attributes used

Question 41 of 60 Quiz ID: q41

What is the domain of an attribute?

The entity set it belongs to

The set of all possible values that the attribute can have

Its data type in the relational schema (e.g., VARCHAR, INT)

The relationship set it describes

Question 42 of 60 Quiz ID: q42

In a ternary relationship 'proj_guide' between instructor, student, and project, what is the super key for the relationship set?

The primary key of instructor

The primary key of student

The primary key of project

The combination of the primary keys of instructor, student, and project

Question 43 of 60 Quiz ID: q43

Why might a designer choose to model a concept as an entity set (like 'phone') instead of an attribute of another entity set?

To reduce the number of tables

If they need to store additional information about that concept (e.g., 'location' for a phone number)

To make the primary key simpler

Because attributes cannot be multivalued

Question 44 of 60 Quiz ID: q44

The 'roles' in a relationship are necessary when:

The relationship is many-to-many

The relationship set has an attribute

The same entity set participates in a relationship more than once

The relationship is one-to-one

Question 45 of 60 Quiz ID: q45

In the context of reduction to schemas, what is the primary key for the table representing a weak entity set?

The discriminator of the weak entity set

The primary key of the strong entity set it depends on

A new, surrogate key created automatically

The combination of the strong entity's primary key and the weak entity's discriminator

Question 46 of 60 Quiz ID: q46

A relationship from a superclass to another entity set is considered:

Invalid in E-R modeling

Inherited by all subclasses

Applicable only to the superclass, not the subclasses

Represented using aggregation

Question 47 of 60 Quiz ID: q47

The 'discriminator' of a weak entity set is underlined with:

A solid line

A dashed line

A double line

A wavy line

Question 48 of 60 Quiz ID: q48

Which of the following is a key difference between the presented E-R notation and UML class diagram notation?

UML does not support relationships.

The position for depicting cardinality constraints is reversed.

E-R diagrams do not support attributes.

UML uses diamonds for relationships.

Question 49 of 60 Quiz ID: q49

The problem in Ex4 (tracking time for advisor and salary) would likely require modifying the model to:

Make 'student' a weak entity

Change the cardinality to many-to-many

Add effective date attributes to the 'advisor' relationship and the 'instructor' entity

Use aggregation on the 'course' entity

Question 50 of 60 Quiz ID: q50

What is the final step outlined in the lecture notes after designing the E-R model?

Writing application code

Reduction to Relation Schemas

Choosing a DBMS vendor

Designing the user interface

Question 51 of 60 Quiz ID: q51

In the conversion process, a simple attribute of an entity set becomes a:

Separate table

Column in the table representing that entity set

Foreign key in another table

Derived attribute in the schema

Question 52 of 60 Quiz ID: q52

If a relationship set has no attributes, and is many-to-one, the most efficient representation is usually:

A separate table with two foreign keys

A separate table with one foreign key

Adding a foreign key to the table on the 'many' side

Adding a foreign key to the table on the 'one' side

Question 53 of 60 Quiz ID: q53

The 'identifying entity set' for a weak entity set is always a:

Weak Entity Set itself

Strong Entity Set

Relationship Set

Specialized Entity Set

Question 54 of 60 Quiz ID: q54

The ISA hierarchy in specialization/generalization is represented by a:

Double diamond

Triangle component

Dashed line

Double rectangle

Question 55 of 60 Quiz ID: q55

A user-defined constraint on a specialization defines membership in a subclass based on:

A condition evaluated by the database system

An assignment made by the database user

The value of a discriminator attribute

The entity's primary key value

Question 56 of 60 Quiz ID: q56

The main goal of using aggregation is to:

Improve query performance

Avoid redundancy and allow relationships on relationships

Enforce total participation

Create simpler primary keys

Question 57 of 60 Quiz ID: q57

In the relational schema for aggregation, the primary key typically includes:

Only the primary key of the new aggregate entity

The primary key of the associated entity set

The primary key of the original aggregated relationship

A newly generated surrogate key

Question 58 of 60 Quiz ID: q58

Which of these is NOT a typical factor considered during database design according to the 'Other Aspects' slide?

Authorization Requirements

Enterprise workflows and Data Flows

The brand of the computer monitor used by the DBA

Usage requirements (Throughput, Response Time)

Question 59 of 60 Quiz ID: q59

The problem of 'Requirement Changes' highlighted at the end suggests that database design is:

A rigid, one-time process

An iterative and evolving process

Only concerned with current needs

Independent of application development

Question 60 of 60 Quiz ID: q60

The 'Human-oriented nature of DB Design' implies that the final end-user is a human, which influences design towards:

Using the fastest possible algorithms regardless of cost

Creating schemas that are meaningful, understandable, and facilitate useful queries for users

Hiding all data complexity from users

Using only binary relationships

Quiz Summary

Review your answers before submitting

Total Questions

Answered

Remaining

00:00

Time Spent

Quiz

Quiz Summary

Confirm Submission