WorksheetsIT12 (Finals) - Quiz 2
Total questions: 15
Worksheet time: 8mins
What is the primary goal of creating an Entity-Relationship Diagram (ERD)?
To specify user interface designs.
To manage project timelines and resources.
To model the logical structure of a database.
To define software development methodologies.
According to the systematic approach, what is the initial step in creating an ERD?
Establishing relationships between entities.
Identifying the main objects or concepts as entities.
Defining attributes for each entity.
Specifying cardinality and optionality.
After identifying entities, what is the next logical step in ERD creation?
Determining the cardinality of relationships.
Reviewing and refining the diagram.
Defining attributes, which are properties for each entity.
Translating the ERD into a relational schema.
What is the purpose of "Establishing Relationships" in the ERD creation process?
To assign primary keys to entities.
To define the data types of attributes.
To normalize the database tables.
To identify how different entities interact with each other.
When creating an ERD, "Specify Cardinality and Optionality" involves detailing what aspect of relationships?
The performance metrics of database queries.
The security permissions for data access.
The nature and constraints of how entities relate.
The physical storage requirements.
What is the final step in the brief overview of creating an ERD?
Defining foreign keys.
Populating the database with initial data.
Reviewing and refining for accuracy and completeness.
Translating to logical schema.
Cardinality in an ERD answers which fundamental question about entity instances in a relationship?
"What is the data type of this instance?"
"How many attributes does an instance have?"
"At most, how many instances can be related?"
"Is it necessary for an instance to exist?"
What does optionality (participation) in a database relationship primarily refer to?
The maximum number of instances allowed in an entity.
Whether a relationship between two entities is mandatory or optional.
The number of attributes an entity can have.
The order in which entities are created.
Which of the following scenarios best represents a One-to-One (1:1) relationship?
A Student can register for many Courses.
A Department employs many Employees.
A Person has exactly one Passport.
A Course has many Students.
In a One-to-Many (1:M) relationship, how is an instance of Entity B related to an instance of Entity A?
An instance of Entity B can be related to one or more instances of Entity A.
An instance of Entity B has no direct relation to Entity A.
An instance of Entity B is related to at most one instance of Entity A.
An instance of Entity B must be related to exactly one instance of Entity A.
If a Student can register for many Courses, and a Course has many Students, what type of cardinality exists between Student and Course?
One-to-One (1:1)
Many-to-Many (M:N)
One-to-Many (1:M)
Zero-to-Many (0:M)
In Crow's Foot notation, what symbol represents a mandatory (required) participation for an entity in a relationship?
(>)
(O)
(|)
(<)
What does the 'O' symbol in Crow's Foot notation signify regarding an entity's participation in a relationship?
It indicates a one-to-one relationship.
It represents an attribute.
It means the entity's participation is optional (minimum of 0).
It denotes a primary key.
When translating an ERD into a relational database schema, what do entities and attributes become?
Entities become stored procedures, and attributes become triggers.
Entities become views, and attributes become indexes.
Entities become schemas, and attributes become databases.
Entities become tables, and attributes become columns.
How are Many-to-Many relationships typically handled when translating an ERD into a logical relational database schema?
They are converted into one-to-one relationships.
They are ignored as they cannot be implemented in relational databases.
They require the creation of a junction (associative) table.
They are directly represented by foreign keys in one of the related tables.
