Scribd
Upload
157 views6 pages

Section 9

This document contains 15 multiple choice questions about database modeling concepts such as resolving many-to-many relationships, transforming ER diagrams to physical designs, and different types of constraints. Key points covered include that a many-to-many relationship is resolved using an intersection table, attributes become columns in database tables, and entities become tables when transforming to a physical design. The questions cover topics like referential integrity, column integrity, and that foreign keys can refer to primary keys in other tables.

Uploaded by

Ancuta Daniela
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
157 views6 pages

Section 9

This document contains 15 multiple choice questions about database modeling concepts such as resolving many-to-many relationships, transforming ER diagrams to physical designs, and different types of constraints. Key points covered include that a many-to-many relationship is resolved using an intersection table, attributes become columns in database tables, and entities become tables when transforming to a physical design. The questions cover topics like referential integrity, column integrity, and that foreign keys can refer to primary keys in other tables.

Uploaded by

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

Section 9

(Answer all questions in this section)

1.To resolve a many to many relationship in a physical model you create a(n)
Mark for Review 
___________________?
(1) Points

Unique key constraints

Two tables with Foreign key constraints between them

Intersection table (*)

Intersection entity

Correct

2.An Arc is transformed to the physical model by adding a foeign Key for
Mark for Review 
every relationship in the Arc. True or False?
(1) Points

True (*)

False

Incorrect. Refer to Section 9 Lesson 3.

3.A barrred Relationship will result in a Foreign Key column that also is part
Mark for Review 
of:
(1) Points

The Table Name

The Primary Key (*)

The Check Constraint

The Column Name


Correct

4.One-to-Many Optional to Mandatory becomes a _______________ on the


Mark for Review 
Master table.
(1) Points

Optional Foreign Key

Mandatory Foreign Key (*)

Primary Key

Unique Key

Correct

5.In an Oracle database, why would the following table name not be allowed
Mark for Review 
'EMPLOYEE JOBS'?
(1) Points

EMPLOYEE is a reserved word

The database does not understand all capital letters

You cannot have spaces between words in a table name (*)

JOBS is a reserved word

Correct

Section 9

(Answer all questions in this section)

6. Why would this table name NOT work in an Oracle database?


Mark for Review 
this_year_end+next_year
(1) Points

Table names must begin with an alphabetic character.

It is too long.
The Plus sign + is not allowed in object names. (*)

None of the above.

Correct

7. Attributes become columns in a database table. True or False?


Mark for Review 
(1) Points

True (*)

False

Incorrect. Refer to Section 9 Lesson 2.

8. The transformation from an ER diagram to a physical design involves


Mark for Review 
changing terminology. Entities in the ER diagram become __________ :
(1) Points

Columns

Unique Keys

Foreign Keys

Tables (*)

Incorrect. Refer to Section 9 Lesson 2.

9. When mapping supertypes, relationships at the supertype level


Mark for Review 
transform as usual. Relationships at the subtype level are implemented
(1) Points
as foreign keys, but the foreign key columns all become optional. True or
False?

True (*)

False
Incorrect. Refer to Section 9 Lesson 4.

10.An "Arc Implementation" can be done just like any other Relationship -
Mark for Review 
you simply add the required Foreign Keys. True or False?
(1) Points

True

False (*)

Correct

Section 9

(Answer all questions in this section)

11.Which of the following is a valid reason for considering a Subtype


Mark for Review 
Implementation?
(1) Points

The resulting table will reside in a single database and be used by


just ONE user.

The common access paths for the supertypes are different.

Business functionality, business rules, access paths, and frequency of


access are all very different between the subtypes. (*)

Most of the relationships are at the supertype level.

Correct

12.The explanation below is an example of which constraint type?


Mark for Review 
If the value in the balance column of the ACCOUNTS table is below 100,
(1) Points
we must send a letter to the account owner which will require extra
programming to enforce.

User-defined integrity (*)


Entity integrity

Referential integrity

Column integrity

Correct

13.Column integrity refers to


Mark for Review 
(1) Points

Columns always having values

Columns always containing positive numbers

Columns always containing values consistent with the defined data


format (*)

Columns always containing text data less than 255 characters

Correct

14.The explanation below is an example of which constraint type?


Mark for Review 
A column must contain only values consistent with the defined data
(1) Points
format of the column

Column integrity (*)

Referential integrity

User-defined integrity

Entity integrity

Correct

15.A foreign key always refers to a primary key in the same table. True or
Mark for Review 
False?
(1) Points
True

False (*)

Correct

You might also like