QQbUkXcT

1Section 6 Quiz Database Design Oracle
2Section 6 Quiz
3            (Answer all questions in this section)
4
51.         Examine the following Entity and decide which rule of Normal Form is being violated:
6ENTITY: CLIENT
7ATTRIBUTES:
8    # CLIENT ID
9    FIRST NAME
10    LAST NAME
11    STREET
12    CITY
13    ZIP CODE
14 Mark for Review
15(1) Points
16            1st Normal Form.
17            2nd Normal Form.
18            3rd Normal Form.
19            None of the above, the entity is fully normalised. (*)
20
212.         A transitive dependency exists when any attribute in an entity is dependent on any other non-UID attribute in that entity.            Mark for Review
22(1) Points
23            True (*)
24            False
25
263.         When any attribute in an entity is dependent on any other non-UID attribute in that entity, this is known as:        Mark for Review
27(1) Points
28            Functional dependency
29            Dependency
30            Transitive dependency (*)
31            Non-dependency
32
334.         The Rule of 3rd Normal Form states that No Non-UID attribute can be dependent on another non-UID attribute. True or False?  Mark for Review
34(1) Points
35            True (*)
36            False
37
385.         Normalizing an Entity to 1st Normal Form is done by removing any attributes that contain muliple values. True or False?  Mark for Review
39(1) Points
40            True (*)
41            False
42
436.         When all attributes are single-valued, the database model is said to conform to:      Mark for Review
44(1) Points
45            2nd Normal Form
46            4th Normal Form
47            1st Normal Form (*)
48            3rd Normal Form
49
507.         If an entity has a multi-valued attribute, to conform to the rule of 1st Normal Form we:     Mark for Review
51(1) Points
52
53            Create an additional entity and relate it to the original entity with a 1:M relationship. (*)
54
55            Make the attribute optional
56            Create an additional entity and relate it to the original entity with a M:M relationship.
57            Do nothing, an entity does not have to be in 1st Normal Form
58
598.         When data is only stored in one place in a database, the database conforms to the rules of ___________. Mark for Review
60(1) Points
61            Reduction
62            Normality
63            Multiplication
64            Normalization (*)
65
669. There is no limit to how many columns can make up an entity's UID. True or False?       Mark for Review
67(1) Points
68            True (*)
69            False
70
7110.       If an entity has no attribute suitable to be a Primary UID, we can create an artificial one. True or False?            Mark for Review
72(1) Points
73            True (*)
74            False
75
7611.       A unique identifier can only be made up of one attribute. True or False?     Mark for Review
77(1) Points
78            True
79            False (*)
80
8112.       An entity can only have one Primary UID. True or False?     Mark for Review
82(1) Points
83            True (*)
84            False
85
8613.       To resolve a 2nd Normal Form violation, we: Mark for Review
87(1) Points
88
89            Move the attribute that violates 2nd Normal Form to a new entity with a relationship to the original entity. (*)
90
91            Move the attribute that violates 2nd Normal Form to a new ERD.
92            Do nothing, an entity does not need to be in 2nd Normal Form.
93            Delete the attribute that was causing the violation.
94
9514.       Examine the following entity and decide how to make it conform to the rule of 2nd Normal Form:
96ENTITY: RECEIPT
97ATTRIBUTES:
98   #CUSTOMER ID
99   #STORE ID
100   STORE LOCATION
101   DATE
102 Mark for Review
103(1) Points
104            Do nothing, it is already in 2nd Normal Form.
105            Delete the attribute STORE ID
106
107            Move the attribute STORE LOCATION to a new entity, STORE, with a UID of STORE ID, and create a relationship to the original entity. (*)
108
109            Move the attribute STORE LOCATION to a new entity, STORE, with a UID of STORE LOCATION, and create a relationship to the original entity.
110
11115.       Any Non-UID attribute must be dependent upon the entire UID. True or False?    Mark for Review
112(1) Points
113            True (*)
114            False
115
1161.         Which of the following would be suitable UIDs for the entity EMPLOYEE: (Choose Two)          Mark for Review
117(1) Points
118                                    (Choose all correct answers)  
119            Social Security Number (*)
120            Last Name
121            Employee ID (*)
122            Address
123
1242.         There is no limit to how many columns can make up an entity's UID. True or False?           Mark for Review
125(1) Points
126            True (*)
127            False
128
1293.         A unique identifier can only be made up of one attribute. True or False?     Mark for Review
130(1) Points
131            True
132            False (*)
133
1344.         If an entity has no attribute suitable to be a Primary UID, we can create an artificial one. True or False?            Mark for Review
135(1) Points
136            True (*)
137            False
138
1395.         Examine the following Entity and decide which rule of Normal Form is being violated:
140ENTITY: CLIENT
141ATTRIBUTES:
142    # CLIENT ID
143    FIRST NAME
144    LAST NAME
145    ORDER ID
146    STREET
147    ZIP CODE
148 Mark for Review
149(1) Points
150            1st Normal Form. (*)
151            2nd Normal Form.
152            3rd Normal Form.
153            None of the above, the entity is fully normalised.
154
1556.         A transitive dependency exists when any attribute in an entity is dependent on any other non-UID attribute in that entity.            Mark for Review
156(1) Points
157            True (*)
158            False
159
1607.         Examine the following Entity and decide which rule of Normal Form is being violated:
161ENTITY: CLIENT
162ATTRIBUTES:
163    # CLIENT ID
164    FIRST NAME
165    LAST NAME
166    STREET
167    CITY
168    ZIP CODE
169 Mark for Review
170(1) Points
171            1st Normal Form.
172            2nd Normal Form.
173            3rd Normal Form.
174            None of the above, the entity is fully normalised. (*)
175
1768.         Examine the following Entity and decide which rule of Normal Form is being violated:
177ENTITY: CLIENT ORDER
178ATTRIBUTES:
179    # CLIENT ID
180    # ORDER ID
181    FIRST NAME
182    LAST NAME
183    ORDER DATE
184    CITY
185    ZIP CODE
186 Mark for Review
187(1) Points
188            1st Normal Form.
189            2nd Normal Form. (*)
190            3rd Normal Form.
191            None of the above, the entity is fully normalised.
192
1939.         Normalizing an Entity to 1st Normal Form is done by removing any attributes that contain muliple values. True or False?  Mark for Review
194(1) Points
195            True (*)
196            False
197
19810.       If an entity has a multi-valued attribute, to conform to the rule of 1st Normal Form we:     Mark for Review
199(1) Points
200            Do nothing, an entity does not have to be in 1st Normal Form
201            Create an additional entity and relate it to the original entity with a M:M relationship.
202            Make the attribute optional
203            Create an additional entity and relate it to the original entity with a 1:M relationship. (*)
204
20511.       An entity can have repeated values and still be in 1st Normal Form. True or False? Mark for Review
206(1) Points
207            True
208            False (*)
209
21012.       When data is only stored in one place in a database, the database conforms to the rules of ___________. Mark for Review
211(1) Points
212            Reduction
213            Multiplication
214            Normalization (*)
215            Normality
216
21713.       To resolve a 2nd Normal Form violation, we: Mark for Review
218(1) Points
219            Do nothing, an entity does not need to be in 2nd Normal Form.
220            Delete the attribute that was causing the violation.
221            Move the attribute that violates 2nd Normal Form to a new ERD.
222            Move the attribute that violates 2nd Normal Form to a new entity with a relationship to the original entity. (*)
223
22414.       Examine the following entity and decide how to make it conform to the rule of 2nd Normal Form:
225ENTITY: RECEIPT
226ATTRIBUTES:
227   #CUSTOMER ID
228   #STORE ID
229   STORE LOCATION
230   DATE
231 Mark for Review
232(1) Points
233
234            Move the attribute STORE LOCATION to a new entity, STORE, with a UID of STORE ID, and create a relationship to the original entity. (*)
235
236            Do nothing, it is already in 2nd Normal Form.
237            Delete the attribute STORE ID
238
239            Move the attribute STORE LOCATION to a new entity, STORE, with a UID of STORE LOCATION, and create a relationship to the original entity.
240
24115.       Any Non-UID attribute must be dependent upon the entire UID. True or False?   
242Mark for Review
243(1) Points
244            True (*)
245            False
246
2471.         As a database designer, you do not need to worry about where in the datamodel you store a particular attribute; as long as you get it onto the ERD, your job is done. True or False?         Mark for Review
248(1) Points
249            True
250            False (*)
251
2522.         Examine the following Entity and decide which rule of Normal Form is being violated:
253ENTITY: CLIENT
254ATTRIBUTES:
255    # CLIENT ID
256    FIRST NAME
257    LAST NAME
258    STREET
259    CITY
260    ZIP CODE
261 Mark for Review
262(1) Points
263            1st Normal Form.
264            2nd Normal Form.
265            3rd Normal Form.
266            None of the above, the entity is fully normalised. (*)
267
2683.         When any attribute in an entity is dependent on any other non-UID attribute in that entity, this is known as:        Mark for Review
269(1) Points
270            Transitive dependency (*)
271            Functional dependency
272            Dependency
273            Non-dependency
274
2754.         A transitive dependency exists when any attribute in an entity is dependent on any other non-UID attribute in that entity.            Mark for Review
276(1) Points
277            True (*)
278            False
279
2805.         An entity can only have one Primary UID. True or False?     Mark for Review
281(1) Points
282            True (*)
283            False
284
2856.         The candidate UID that is chosen to identify an entity is called the Primary UID; other candidate UIDs are called Secondary UIDs.      Mark for Review
286(1) Points
287            Yes, this is the way UID's are named. (*)
288            No, each Entity can only have one UID, the secondary one.
289            No, it is not possible to have more than one UID for an Entity.
290            No, after UIDs are first sorted, the first one is called the Primary UID, the second is the Secondary UID, etc.
291
2927.         Where an entity has more than one attribute suitable to be the Primary UID, these are known as _____________ UIDs.           Mark for Review
293(1) Points
294            Composite
295            Simple
296            Secondary
297            Candidate (*)
298
2998.         Which of the following would be suitable UIDs for the entity EMPLOYEE: (Choose Two)          Mark for Review
300(1) Points
301                                    (Choose all correct answers)  
302            Address
303            Employee ID (*)
304            Social Security Number (*)
305            Last Name
306
3079.         Any Non-UID attribute must be dependent upon the entire UID. True or False?    Mark for Review
308(1) Points
309            True (*)
310            False
311
31210. What is the rule of Second Normal Form?           Mark for Review
313(1) Points
314            No non-UID attributes can be dependent on any part of the UID.
315            Some non-UID attributes can be dependent on the entire UID.
316            All non-UID attributes must be dependent upon the entire UID. (*)
317            None of the above
318
31911.       Examine the following entity and decide how to make it conform to the rule of 2nd Normal Form:
320ENTITY: RECEIPT
321ATTRIBUTES:
322   #CUSTOMER ID
323   #STORE ID
324   STORE LOCATION
325   DATE
326 Mark for Review
327(1) Points
328            Delete the attribute STORE ID
329
330            Move the attribute STORE LOCATION to a new entity, STORE, with a UID of STORE LOCATION, and create a relationship to the original entity.
331
332            Do nothing, it is already in 2nd Normal Form.
333
334            Move the attribute STORE LOCATION to a new entity, STORE, with a UID of STORE ID, and create a relationship to the original entity. (*)
335
33612.       To convert an entity with a multi valued attribute to 1st Normal Form, we create an additional entity and relate it to the original entity with a 1:1 relationship. True or False?       Mark for Review
337(1) Points
338            True
339            False (*)
340
34113.       An entity ORDER has the attributes Order ID, Order Date, Product id, Customer ID. This entity is in 1st Normal Form. True or False?        Mark for Review
342(1) Points
343            True
344            False (*)
345
34614.       An entity can have repeated values and still be in 1st Normal Form. True or False? Mark for Review
347(1) Points
348            True
349            False (*)
350
35115.       Normalizing an Entity to 1st Normal Form is done by removing any attributes that contain muliple values. True or False?  Mark for Review
352(1) Points
353            True (*)
354            False
355
3561.         The candidate UID that is chosen to identify an entity is called the Primary UID; other candidate UIDs are called Secondary UIDs.      Mark for Review
357(1) Points
358            No, it is not possible to have more than one UID for an Entity.
359            No, after UIDs are first sorted, the first one is called the Primary UID, the second is the Secondary UID, etc.
360            No, each Entity can only have one UID, the secondary one.
361            Yes, this is the way UID's are named. (*)
362
3632.         Where an entity has more than one attribute suitable to be the Primary UID, these are known as _____________ UIDs.           Mark for Review
364(1) Points
365            Secondary
366            Composite
367            Candidate (*)
368            Simple
369
3703.         If an entity has no attribute suitable to be a Primary UID, we can create an artificial one. True or False?            Mark for Review
371(1) Points
372            True (*)
373            False
374
3754.         A candidate UID that is not chosen to be the Primary UID is called:           Mark for Review
376(1) Points
377            Composite
378            Secondary (*)
379            Simple
380            Artificial
381
3825.         What is the rule of Second Normal Form?     Mark for Review
383(1) Points
384            No non-UID attributes can be dependent on any part of the UID.
385            Some non-UID attributes can be dependent on the entire UID.
386            All non-UID attributes must be dependent upon the entire UID. (*)
387            None of the above
388
3896.         Examine the following entity and decide which attribute breaks the 2nd Normal Form rule:
390ENTITY: RECEIPT
391ATTRIBUTES:
392   #CUSTOMER ID
393   #STORE ID
394   STORE LOCATION
395   DATE
396 Mark for Review
397(1) Points
398            STORE LOCATION (*)
399            CUSTOMER ID
400            DATE
401            STORE ID
402
4037.         When is an entity in 2nd Normal Form?         Mark for Review
404(1) Points
405            When all non-UID attributes are dependent upon the entire UID. (*)
406            When attributes with repeating or multi-values are present.
407            When no attritibutes are mutually independent and all are fully dependent on the primary key.
408            None of the Above.
409
4108.         When any attribute in an entity is dependent on any other non-UID attribute in that entity, this is known as:        Mark for Review
411(1) Points
412            Non-dependency
413            Functional dependency
414            Dependency
415            Transitive dependency (*)
416
4179.         Examine the following Entity and decide which rule of Normal Form is being violated:
418ENTITY: CLIENT
419ATTRIBUTES:
420    # CLIENT ID
421    FIRST NAME
422    LAST NAME
423    ORDER ID
424    STREET
425    ZIP CODE
426 Mark for Review
427(1) Points
428            1st Normal Form. (*)
429            2nd Normal Form.
430            3rd Normal Form.
431            None of the above, the entity is fully normalised.
432
43310.       Examine the following Entity and decide which rule of Normal Form is being violated:
434ENTITY: CLIENT
435ATTRIBUTES:
436    # CLIENT ID
437    FIRST NAME
438    LAST NAME
439    STREET
440    CITY
441    ZIP CODE
442 Mark for Review
443(1) Points
444            1st Normal Form.
445            2nd Normal Form.
446            3rd Normal Form.
447            None of the above, the entity is fully normalised. (*)
448
44911.       A transitive dependency exists when any attribute in an entity is dependent on any other non-UID attribute in that entity.            Mark for Review
450(1) Points
451            True (*)
452            False
453
45412.       Normalizing an Entity to 1st Normal Form is done by removing any attributes that contain muliple values. True or False?  Mark for Review
455(1) Points
456            True (*)
457            False
458
45913.       If an entity has a multi-valued attribute, to conform to the rule of 1st Normal Form we:     Mark for Review
460(1) Points
461            Make the attribute optional
462            Do nothing, an entity does not have to be in 1st Normal Form
463            Create an additional entity and relate it to the original entity with a M:M relationship.
464            Create an additional entity and relate it to the original entity with a 1:M relationship. (*)
465
46614.       When data is only stored in one place in a database, the database conforms to the rules of ___________. Mark for Review
467(1) Points
468            Multiplication
469            Normality
470            Reduction
471            Normalization (*)
472
47315.       An entity ORDER has the attributes Order ID, Order Date, Product id, Customer ID. This entity is in 1st Normal Form. True or False?        Mark for Review
474(1) Points
475            True
476
477            False (*)
478
479Section 7 Quiz Database Design Oracle
480Section 7 Quiz
481                (Answer all questions in this section)
482
4831.            Which of the following would best be represented by an arc?    Mark for Review
484(1) Points
485                STUDENT (senior, male)
486                STUDENT (Grade A student, Average Student)
487                STUDENT (graduating, female)
488                STUDENT ( University, Technical College) (*)
489
4902.            Arcs are Mandatory in Data modeling. All ERD's must have at least one Arc. True or False?            Mark for Review
491(1) Points
492                True
493                False (*)
494
4953.            To visually represent exclusivity between two or more relationships in an ERD you would most likely use an ________.         Mark for Review
496(1) Points
497                Arc (*)
498                Relationship
499                Attribute
500                UID
501
5024.            An arc can often be modeled as Supertype and Subtypes. True or False?              Mark for Review
503(1) Points
504                True (*)
505                False
506
5075.            Which of the following would best be represented by an arc?    Mark for Review
508(1) Points
509                TEACHER (Female, Bob)
510                PARENT (Girl, Bob)
511                DELIVERY ADDRESS (Home, Office) (*)
512                STUDENT (Grade A student, Average Student)
513
5146.            All relationships participating in an arc must be mandatory. True or False?             Mark for Review
515(1) Points
516                True
517                False (*)
518
5197.            Every business has restrictions on which attribute values and which relationships are allowed. These are known as:           Mark for Review
520(1) Points
521                Constraints. (*)
522                Relationships
523                Entities.
524                Attributes
525
5268.            Arcs are used to visually represent _________ between two or more relationships in an ERD.   Mark for Review
527(1) Points
528                Differences
529                Inheritance
530                Sameness
531                Exclusivity (*)
532
5339.            Cascading UIDs are a feature often found in what type of Relationship? Mark for Review
534(1) Points
535                Invalid Relationship
536                Recursive Relationship
537                General Relationship
538                Heirarchical Relationship (*)
539
54010.          A relationship between an entity and itself is called a/an:             Mark for Review
541(1) Points
542                Recursive Relationship (*)
543                Invalid Relationship
544                Heirarchical Relationship
545                General Relationship
546
54711.          A Recursive Relationship is represented on an ERD by a/an:         Mark for Review
548(1) Points
549                Single Toe
550                Pig's Ear (*)
551                Crow's Foot
552                Dog's Tail
553
55412.          A single relationship can be both Recursive and Hierarchical at the same time. True or False?       Mark for Review
555(1) Points
556                True
557                False (*)
558
55913.          Business organizational charts are often modeled as a Hierarchical relationship. True or False?    Mark for Review
560(1) Points
561                True (*)
562                False
563
56414.          A recursive relationship must be Mandatory at both ends. True or False?              Mark for Review
565(1) Points
566                True
567                False (*)
568
56915.          A Hierarchical relationship is a series of relationships that reflect entities organized into successive levels. True or False?    Mark for Review
570(1) Points
571                True (*)
572                False
573
5741.            A particular problem may be solved using either a Recursive Relationship or a Hierarchical Relationship, though not at the same time. True or False?       Mark for Review
575(1) Points
576                True (*)
577                False
578
5792.            A single relationship can be both Recursive and Hierarchical at the same time. True or False?       Mark for Review
580(1) Points
581                True
582                False (*)
583
5843.            A Recursive Relationship is represented on an ERD by a/an:         Mark for Review
585(1) Points
586                Single Toe
587                Dog's Tail
588                Pig's Ear (*)
589                Crow's Foot
590
5914.            Business organizational charts are often modeled as a Hierarchical relationship. True or False?    Mark for Review
592(1) Points
593                True (*)
594                False
595
5965.            A relationship between an entity and itself is called a/an:             Mark for Review
597(1) Points
598                General Relationship
599                Recursive Relationship (*)
600                Heirarchical Relationship
601                Invalid Relationship
602
6036.            A Hierarchical relationship is a series of relationships that reflect entities organized into successive levels. True or False?    Mark for Review
604(1) Points
605                True (*)
606                False
607
6087.            Cascading UIDs are a feature often found in what type of Relationship? Mark for Review
609(1) Points
610                Recursive Relationship
611                General Relationship
612                Invalid Relationship
613                Heirarchical Relationship (*)
614
6158. Which of the following would best be represented by an arc?                Mark for Review
616(1) Points
617                STUDENT (senior, male)
618                STUDENT ( University, Technical College) (*)
619                STUDENT (Grade A student, Average Student)
620                STUDENT (graduating, female)
621
6229.            To visually represent exclusivity between two or more relationships in an ERD you would most likely use an ________.         Mark for Review
623(1) Points
624                Relationship
625                Arc (*)
626                UID
627                Attribute
628
62910.          All relationships participating in an arc must be mandatory. True or False?             Mark for Review
630(1) Points
631                True
632                False (*)
633
63411.          An arc can often be modeled as Supertype and Subtypes. True or False?              Mark for Review
635(1) Points
636                True (*)
637                False
638
63912.          Arcs are used to visually represent _________ between two or more relationships in an ERD.   Mark for Review
640(1) Points
641                Sameness
642                Differences
643                Exclusivity (*)
644                Inheritance
645
64613.          Which of the following can be added to a relationship?  Mark for Review
647(1) Points
648                An optional attribute can be created
649                A composite attribute
650                An attribute
651                An arc can be assigned (*)
652
65314.          Which of the following would best be represented by an arc?    Mark for Review
654(1) Points
655                TEACHER (Female, Bob)
656                STUDENT (Grade A student, Average Student)
657                DELIVERY ADDRESS (Home, Office) (*)
658                PARENT (Girl, Bob)
659
66015.          Arcs are Mandatory in Data modeling. All ERD's must have at least one Arc. True or False?            Mark for Review
661(1) Points
662                True
663                False (*)
664
6651.            A relationship between an entity and itself is called a/an:             Mark for Review
666(1) Points
667                Invalid Relationship
668                Recursive Relationship (*)
669                General Relationship
670                Heirarchical Relationship
671
6722.            A recursive relationship must be Mandatory at both ends. True or False?              Mark for Review
673(1) Points
674                True
675                False (*)
676
6773.            A Hierarchical relationship is a series of relationships that reflect entities organized into successive levels. True or False?    Mark for Review
678(1) Points
679                True (*)
680                False
681
6824.            A single relationship can be both Recursive and Hierarchical at the same time. True or False?       Mark for Review
683(1) Points
684                True
685                False (*)
686
6875.            A particular problem may be solved using either a Recursive Relationship or a Hierarchical Relationship, though not at the same time. True or False?       Mark for Review
688(1) Points
689                True (*)
690                False
691
6926.            Business organizational charts are often modeled as a Hierarchical relationship. True or False?    Mark for Review
693(1) Points
694                True (*)
695                False
696
6977.            A Recursive Relationship is represented on an ERD by a/an:         Mark for Review
698(1) Points
699                Single Toe
700                Pig's Ear (*)
701                Crow's Foot
702                Dog's Tail
703
7048.            Which of the following can be added to a relationship?  Mark for Review
705(1) Points
706                An arc can be assigned (*)
707                An optional attribute can be created
708                An attribute
709                A composite attribute
710
7119.            Every business has restrictions on which attribute values and which relationships are allowed. These are known as:           Mark for Review
712(1) Points
713                Attributes
714                Constraints. (*)
715                Entities.
716                Relationships
717
71810.          Which of the following would best be represented by an arc?    Mark for Review
719(1) Points
720                TEACHER (Female, Bob)
721                DELIVERY ADDRESS (Home, Office) (*)
722                PARENT (Girl, Bob)
723                STUDENT (Grade A student, Average Student)
724
72511.          An arc can often be modeled as Supertype and Subtypes. True or False?              Mark for Review
726(1) Points
727                True (*)
728                False
729
73012.          Arcs are Mandatory in Data modeling. All ERD's must have at least one Arc. True or False?            Mark for Review
731(1) Points
732                True
733                False (*)
734
73513.          To visually represent exclusivity between two or more relationships in an ERD you would most likely use an ________.         Mark for Review
736(1) Points
737                Attribute
738                Relationship
739                UID
740                Arc (*)
741
74214.          Arcs model an Exclusive OR constraint. True or False?     Mark for Review
743(1) Points
744                True (*)
745                False
746
74715.          Arcs are used to visually represent _________ between two or more relationships in an ERD.   Mark for Review
748(1) Points
749                Differences
750                Sameness
751                Exclusivity (*)
752                Inheritance
753
7541.            All relationships participating in an arc must be mandatory. True or False?             Mark for Review
755(1) Points
756                True
757                False (*)
758
7592.            Arcs model an Exclusive OR constraint. True or False?     Mark for Review
760(1) Points
761                True (*)
762                False
763
7643.            An arc can often be modeled as Supertype and Subtypes. True or False?              Mark for Review
765(1) Points
766                True (*)
767                False
768
7694.            Which of the following would best be represented by an arc?    Mark for Review
770(1) Points
771                STUDENT (Grade A student, Average Student)
772                TEACHER (Female, Bob)
773                DELIVERY ADDRESS (Home, Office) (*)
774                PARENT (Girl, Bob)
775
7765.            To visually represent exclusivity between two or more relationships in an ERD you would most likely use an ________.         Mark for Review
777(1) Points
778                UID
779                Arc (*)
780                Attribute
781                Relationship
782
7836.            Which of the following would best be represented by an arc?    Mark for Review
784(1) Points
785                STUDENT (graduating, female)
786                STUDENT ( University, Technical College) (*)
787                STUDENT (Grade A student, Average Student)
788                STUDENT (senior, male)
789
7907.            Arcs are used to visually represent _________ between two or more relationships in an ERD.   Mark for Review
791(1) Points
792                Exclusivity (*)
793                Differences
794                Inheritance
795                Sameness
796
7978.            Every business has restrictions on which attribute values and which relationships are allowed. These are known as:           Mark for Review
798(1) Points
799                Entities.
800                Relationships
801                Constraints. (*)
802                Attributes
803
8049.            A single relationship can be both Recursive and Hierarchical at the same time. True or False?       Mark for Review
805(1) Points
806                True
807                False (*)
808
80910.          A recursive relationship must be Mandatory at both ends. True or False?              Mark for Review
810(1) Points
811                True
812                False (*)
813
81411.          Cascading UIDs are a feature often found in what type of Relationship? Mark for Review
815(1) Points
816                Recursive Relationship
817                General Relationship
818                Heirarchical Relationship (*)
819                Invalid Relationship
820
82112.          A Hierarchical relationship is a series of relationships that reflect entities organized into successive levels. True or False?    Mark for Review
822(1) Points
823                True (*)
824                False
825
82613.          A Recursive Relationship is represented on an ERD by a/an:         Mark for Review
827(1) Points
828                Crow's Foot
829                Single Toe
830                Pig's Ear (*)
831                Dog's Tail
832
83314.          A particular problem may be solved using either a Recursive Relationship or a Hierarchical Relationship, though not at the same time. True or False?       Mark for Review
834(1) Points
835                True (*)
836                False
837
83815.          Business organizational charts are often modeled as a Hierarchical relationship. True or False?    Mark for Review
839(1) Points
840                True (*)
841
842                False
843
844Section 8 Quiz
845                (Answer all questions in this section)
846
8471.            Which of the following scenarios should be modeled so that historical data is kept? (Choose two)             Mark for Review
848(1) Points
849                                                (Choose all correct answers)      
850                BABY and AGE
851                CUSTOMER and ORDERS (*)
852                TEACHER and AGE
853                CUSTOMER and PAYMENTS (*)
854
8552.            When modeling historical data the unique identifier is always made up of a barred relationship from the original two entities. True or False?         Mark for Review
856(1) Points
857                True
858                False (*)
859
8603.            Which of the following scenarios should be modeled so that historical data is kept? (Choose two)             Mark for Review
861(1) Points
862                                                (Choose all correct answers)      
863                LIBRARY and BOOK (*)
864                STUDENT and GRADE (*)
865                STUDENT and AGE
866                LIBRARY and NUMBER OF BOOKS
867
8684.            Which of the following statements are true for ERD's to enhance their readability. (Choose Two)              Mark for Review
869(1) Points
870                                                (Choose all correct answers)      
871
872                You must ensure that you have every single entity--even if hundreds of them exist--on one single, big diagram.
873
874                The crows feet (many ends) can point whichever way is the easiest to draw.
875
876                Avoid crossing one relationship line with another. (*)
877
878                It is OK to break down a large ERD into subsets of the overall picture. By doing so, you end up with more than one ERD that, taken together, documents the entire system. (*)
879
8805.            No formal rules exist for drawing ERD's. The most important thing is to make sure that all entities, attributes, and relationships are documented on the diagram, and the diagram is clear and readable. True or False?              Mark for Review
881(1) Points
882                True (*)
883                False
884
8856.            You must make sure all entities of a proposed system can fit onto one diagram. It is not allowed to break up a data model into more than one diagram. True or False?             Mark for Review
886(1) Points
887                True
888                False (*)
889
8907. Formal rules exist for drawing ERD's. You must always follow them, even if it results in an ERD that is difficult to read. True or False?        Mark for Review
891(1) Points
892                True
893                False (*)
894
8958.            All systems must include functionality to provide logging or journaling in conceptual data models. True or False?   Mark for Review
896(1) Points
897                True
898                False (*)
899
9009.            Which of the following is a logical constraint that could result from considering how time impacts an example of data storage?               Mark for Review
901(1) Points
902                End Date must be before the Start Date.
903                EMPLOYEE periods can overlap causing the database to crash.
904                Dates must be stored with Time.
905
906                An ASSIGNMENT may only refer to an EMPLOYEE with a valid employee record at the Start Date of the ASSIGNMENT. (*)
907
90810.          What is the function of logging or journaling in conceptual data models?               Mark for Review
909(1) Points
910                Represents entities as time in the data model.
911                Creates a fixed time for all events in a data model.
912                Gives a timestamp to all entities.
913                Allows you to track the history of attribute values, relationships, and/or entire entities (*)
914
91511.          How do you know when to use the different types of time in your design?          Mark for Review
916(1) Points
917                It depends on the functional needs of the system . (*)
918                Always model time; you can take it out later if it is not needed.
919                You would first determine the existence of the concept of time and map it against the Greenwich Mean Time.
920                The rules are fixed and should be followed.
921
92212.          Which of the following would be a logical constraint when modeling time for a country entity?   Mark for Review
923(1) Points
924                If you are doing a system for France or Germany, you would need security clearance.
925                Daily traffic patterns must be monitored to determine which countries are overcrowded.
926                Countries may change their names and/or borders over a period of time. (*)
927                People have births and deaths in their countries that must be tracked by the system.
928
92913.          In a payroll system, it is desirable to have an entity called DAY with a holiday attribute when you want to track special holiday dates. True or False?             Mark for Review
930(1) Points
931                True (*)
932                False
933
93414.          Modeling historical data is optional. True or False?           Mark for Review
935(1) Points
936                True (*)
937                False
938
93915.          When a relationship may or may not be transferable, depending on time, this is know as a/an:  Mark for Review
940(1) Points
941                Transferable Relationship
942                Non-transferable Relationship.
943                Conditional Non-transferable Relationship. (*)
944                Arc.
945
9461.            You must make sure all entities of a proposed system can fit onto one diagram. It is not allowed to break up a data model into more than one diagram. True or False?             Mark for Review
947(1) Points
948                True
949                False (*)
950
9512.            Which of the following statements are true for ERD's to enhance their readability. (Choose Two)              Mark for Review
952(1) Points
953                                                (Choose all correct answers)      
954                You must ensure that you have every single entity--even if hundreds of them exist--on one single, big diagram.
955
956                It is OK to break down a large ERD into subsets of the overall picture. By doing so, you end up with more than one ERD that, taken together, documents the entire system. (*)
957
958                The crows feet (many ends) can point whichever way is the easiest to draw.
959
960                Avoid crossing one relationship line with another. (*)
961
9623.            In an ERD, it is a good idea to group your entities according to the expected volumes. By grouping high volume entities together, the diagrams could become easier to read. True or False?       Mark for Review
963(1) Points
964                True (*)
965                False
966
9674.            There is no point in trying to group your entities together on your diagram according to volume, and making a diagram look nice is a waste of time. True or False?      Mark for Review
968(1) Points
969                True
970                False (*)
971
9725.            Which of the following scenarios should be modeled so that historical data is kept? (Choose two)             Mark for Review
973(1) Points
974                                                (Choose all correct answers)      
975                CUSTOMER and ORDERS (*)
976                CUSTOMER and PAYMENTS (*)
977                TEACHER and AGE
978                BABY and AGE
979
9806.            Which of the following scenarios should be modeled so that historical data is kept? (Choose two)             Mark for Review
981(1) Points
982                                                (Choose all correct answers)      
983                LIBRARY and NUMBER OF BOOKS
984                STUDENT and GRADE (*)
985                LIBRARY and BOOK (*)
986                STUDENT and AGE
987
9887.            Modeling historical data can produce a unique identifier that includes a date. True or False?        Mark for Review
989(1) Points
990                True (*)
991                False
992
9938.            In a payroll system, it is desirable to have an entity called DAY with a holiday attribute when you want to track special holiday dates. True or False?             Mark for Review
994(1) Points
995                True (*)
996                False
997
9989.            Which of the following would be a logical constraint when modeling time for a City entity?           Mark for Review
999(1) Points
1000                If you are doing a system for any French City, you would need security clearance.
1001                People are born in the city and people die in the city.
1002
1003                Daily traffic patterns must be monitored to determine how many law enforcement officers are needed.
1004
1005                Cites may change their names and/or country association if the borders of a country change. (*)
1006
100710.          When you add the concept of time to your data model, your model becomes more complex. True or False?                Mark for Review
1008(1) Points
1009                True (*)
1010                False
1011
101211.          If you have an entity with a DATE attribute, in addition to other attributes that track date characteristics, you should create a DAY entity. True or False?            Mark for Review
1013(1) Points
1014                True (*)
1015                False
1016
101712.          There are no circumstances where you would create a DAY entity. True or False?             Mark for Review
1018(1) Points
1019                True
1020                False (*)
1021
102213.          You are doing a data model for a computer sales company where the price of postage depends upon the day of the week that goods are shipped. So shipping is more expensive if the customer wants a delivery to take place on a Saturday or Sunday. What would be the best way to model this?           Mark for Review
1023(1) Points
1024
1025                Email current prices to all employees whenever a price changes.
1026
1027                Update the prices in the system, print out the current prices when they change, and pin them on the company noticeboard.
1028
1029                Allow them to enter whatever delivery charge they want.
1030
1031                Use a Delivery Day entity, which holds prices against week days, and ensure the we also have an attribute for the Requested Delivery Day in the Order Entity. (*)
1032
103314.          Why would you want to model a time component when designing a system that lets people buy bars of gold?     Mark for Review
1034(1) Points
1035                The Government of your country might want to be notified of this transaction.
1036                You would not want to model this; it is not important.
1037
1038                The price of gold fluctuates and, to determine the current price, you need to know the time of purchase. (*)
1039
1040                Sales people must determine where the gold is coming from.
1041
104215.          All systems must include functionality to provide logging or journaling in conceptual data models. True or False?   Mark for Review
1043(1) Points
1044                True
1045                False (*)
1046
10471.            Which of the following scenarios should be modeled so that historical data is kept? (Choose two)             Mark for Review
1048(1) Points
1049                                                (Choose all correct answers)      
1050                LIBRARY and BOOK (*)
1051                STUDENT and AGE
1052                LIBRARY and NUMBER OF BOOKS
1053                STUDENT and GRADE (*)
1054
10552.            When modeling historical data the unique identifier is always made up of a barred relationship from the original two entities. True or False?         Mark for Review
1056(1) Points
1057                True
1058                False (*)
1059
10603.            Which of the following scenarios should be modeled so that historical data is kept? (Choose two)             Mark for Review
1061(1) Points
1062                                                (Choose all correct answers)      
1063                CUSTOMER and PAYMENTS (*)
1064                CUSTOMER and ORDERS (*)
1065                BABY and AGE
1066                TEACHER and AGE
1067
10684.            When a relationship may or may not be transferable, depending on time, this is know as a/an:  Mark for Review
1069(1) Points
1070                Transferable Relationship
1071                Non-transferable Relationship.
1072                Conditional Non-transferable Relationship. (*)
1073                Arc.
1074
10755.            All systems must have an entity called WEEK with a holiday attribute, so you know when to give your employees a holiday. True or False?        Mark for Review
1076(1) Points
1077                True
1078                False (*)
1079
10806.            In a payroll system, it is desirable to have an entity called DAY with a holiday attribute when you want to track special holiday dates. True or False?             Mark for Review
1081(1) Points
1082                True (*)
1083                False
1084
10857.            When you add the concept of time to your data model, your model becomes more complex. True or False?                Mark for Review
1086(1) Points
1087                True (*)
1088                False
1089
10908.            If you have an entity that a DATE attribute, and other attributes that track characteristics of the date, you should create a DAY entity. True or False?            Mark for Review
1091(1) Points
1092                True (*)
1093                False
1094
10959.            In an ERD, it is a good idea to group your entities according to the expected volumes. By grouping high volume entities together, the diagrams could become easier to read. True or False?       Mark for Review
1096(1) Points
1097                True (*)
1098                False
1099
110010.          There is no point in trying to group your entities together on your diagram according to volume, and making a diagram look nice is a waste of time. True or False?      Mark for Review
1101(1) Points
1102                True
1103                False (*)
1104
110511.          No formal rules exist for drawing ERD's. The most important thing is to make sure that all entities, attributes, and relationships are documented on the diagram, and the diagram is clear and readable. True or False?              Mark for Review
1106(1) Points
1107                True (*)
1108                False
1109
111012.          In an ERD, High Volume Entities usually have very few relationships to other entities. True or False?        Mark for Review
1111(1) Points
1112                True
1113                False (*)
1114
111513.          You are doing a data model for a computer sales company where the price of postage depends upon the day of the week that goods are shipped. So shipping is more expensive if the customer wants a delivery to take place on a Saturday or Sunday. What would be the best way to model this?           Mark for Review
1116(1) Points
1117                Email current prices to all employees whenever a price changes.
1118
1119                Update the prices in the system, print out the current prices when they change, and pin them on the company noticeboard.
1120
1121                Use a Delivery Day entity, which holds prices against week days, and ensure the we also have an attribute for the Requested Delivery Day in the Order Entity. (*)
1122
1123                Allow them to enter whatever delivery charge they want.
1124
112514.          Which of the following is a logical constraint that could result from considering how time impacts an example of data storage?               Mark for Review
1126(1) Points
1127                EMPLOYEE periods can overlap causing the database to crash.
1128                Dates must be stored with Time.
1129                End Date must be before the Start Date.
1130
1131                An ASSIGNMENT may only refer to an EMPLOYEE with a valid employee record at the Start Date of the ASSIGNMENT. (*)
1132
113315.          Why would you want to model a time component when designing a system that lets people buy bars of gold?     Mark for Review
1134(1) Points
1135                You would not want to model this; it is not important.
1136                The Government of your country might want to be notified of this transaction.
1137
1138                The price of gold fluctuates and, to determine the current price, you need to know the time of purchase. (*)
1139
1140                Sales people must determine where the gold is coming from.
1141
11421.            You are doing a data model for a computer sales company where the price fluctuates on a regular basis. If you want to allow the company to modify the price and keep track of the changes, what is the best way to model this?      Mark for Review
1143(1) Points
1144
1145                A. Create a product entity and a related price entity with start and end dates, and then let the users enter the new price whenever required.
1146                B. Create a new item and a new price every day.
1147                C. Use a price entity with a start and end date
1148                D. Allow them to delete the item and enter a new one.
1149                E. Both A and C (*)
1150
11512.            Which of the following is a logical constraint that could result from considering how time impacts an example of data storage?               Mark for Review
1152(1) Points
1153
1154                An ASSIGNMENT may only refer to an EMPLOYEE with a valid employee record at the Start Date of the ASSIGNMENT. (*)
1155
1156                Dates must be stored with Time.
1157                End Date must be before the Start Date.
1158                EMPLOYEE periods can overlap causing the database to crash.
1159
11603.            You are doing a data model for a computer sales company where the price of postage depends upon the day of the week that goods are shipped. So shipping is more expensive if the customer wants a delivery to take place on a Saturday or Sunday. What would be the best way to model this?           Mark for Review
1161(1) Points
1162
1163                Update the prices in the system, print out the current prices when they change, and pin them on the company noticeboard.
1164
1165                Use a Delivery Day entity, which holds prices against week days, and ensure the we also have an attribute for the Requested Delivery Day in the Order Entity. (*)
1166
1167                Email current prices to all employees whenever a price changes.
1168                Allow them to enter whatever delivery charge they want.
1169
11704. Historical data must never be kept. True or False?       Mark for Review
1171(1) Points
1172                True
1173                False (*)
1174
11755.            Modeling historical data can produce a unique identifier that includes a date. True or False?        Mark for Review
1176(1) Points
1177                True (*)
1178                False
1179
11806.            Which of the following scenarios should be modeled so that historical data is kept? (Choose two)             Mark for Review
1181(1) Points
1182                                                (Choose all correct answers)      
1183                BABY and AGE
1184                TEACHER and AGE
1185                CUSTOMER and ORDERS (*)
1186                CUSTOMER and PAYMENTS (*)
1187
11887.            In an ERD, High Volume Entities usually have very few relationships to other entities. True or False?        Mark for Review
1189(1) Points
1190                True
1191                False (*)
1192
11938.            No formal rules exist for drawing ERD's. The most important thing is to make sure that all entities, attributes, and relationships are documented on the diagram, and the diagram is clear and readable. True or False?              Mark for Review
1194(1) Points
1195                True (*)
1196                False
1197
11989.            Formal rules exist for drawing ERD's. You must always follow them, even if it results in an ERD that is difficult to read. True or False?   Mark for Review
1199(1) Points
1200                True
1201                False (*)
1202
120310.          Which of the following statements are true to enhance the readability of ERDs? (Choose Two)  Mark for Review
1204(1) Points
1205                                                (Choose all correct answers)      
1206                Crossing relationship lines help the readability of the diagram.
1207
1208                Crows feet (the many-ends of relationships) should consistently point the same direction where possible, either South & East or North & West (*)
1209
1210                Relationship lines should not cross. (*)
1211
1212                It does not matter which way the crows feet (many ends of a relationship) point.
1213
121411.          Modeling historical data is optional. True or False?           Mark for Review
1215(1) Points
1216                True (*)
1217                False
1218
121912.          When a relationship may or may not be transferable, depending on time, this is know as a/an:  Mark for Review
1220(1) Points
1221                Conditional Non-transferable Relationship. (*)
1222                Arc.
1223                Transferable Relationship
1224                Non-transferable Relationship.
1225
122613.          When you add the concept of time to your data model, your model becomes more complex. True or False?                Mark for Review
1227(1) Points
1228                True (*)
1229                False
1230
123114.          All systems must have an entity called WEEK with a holiday attribute so that you know when to give employees a holiday. True or False?        Mark for Review
1232(1) Points
1233                True
1234                False (*)
1235
123615.          How do you know when to use the different types of time in your design?          Mark for Review
1237(1) Points
1238
1239                You would first determine the existence of the concept of time and map it against the Greenwich Mean Time.
1240
1241                The rules are fixed and should be followed.
1242                Always model time; you can take it out later if it is not needed.
1243                It depends on the functional needs of the system . (*)
1244
12451.            Which of the following scenarios should be modeled so that historical data is kept? (Choose two)             Mark for Review
1246(1) Points
1247                                                (Choose all correct answers)      
1248                STUDENT and GRADE (*)
1249                STUDENT and AGE
1250                LIBRARY and BOOK (*)
1251                LIBRARY and NUMBER OF BOOKS
1252
12532.            When modeling historical data the unique identifier is always made up of a barred relationship from the original two entities. True or False?         Mark for Review
1254(1) Points
1255                True
1256                False (*)
1257
12583.            Modeling historical data can produce a unique identifier that includes a date. True or False?        Mark for Review
1259(1) Points
1260                True (*)
1261                False
1262
12634.            All systems must include functionality to provide logging or journaling in conceptual data models. True or False?   Mark for Review
1264(1) Points
1265                True
1266                False (*)
1267
12685.            You are doing a data model for a computer sales company where the price fluctuates on a regular basis. If you want to allow the company to modify the price and keep track of the changes, what is the best way to model this?      Mark for Review
1269(1) Points
1270
1271                A. Create a product entity and a related price entity with start and end dates, and then let the users enter the new price whenever required.
1272                B. Create a new item and a new price every day.
1273                C. Use a price entity with a start and end date
1274                D. Allow them to delete the item and enter a new one.
1275                E. Both A and C (*)
1276
12776.            Which of the following is a logical constraint that could result from considering how time impacts an example of data storage?               Mark for Review
1278(1) Points
1279                End Date must be before the Start Date.
1280                EMPLOYEE periods can overlap causing the database to crash.
1281                An ASSIGNMENT may only refer to an EMPLOYEE with a valid employee record at the Start Date of the ASSIGNMENT. (*)
1282                Dates must be stored with Time.
1283
12847.            Formal rules exist for drawing ERD's. You must always follow them, even if it results in an ERD that is difficult to read. True or False?   Mark for Review
1285(1) Points
1286                True
1287                False (*)
1288
12898.            In an ERD, High Volume Entities usually have very few relationships to other entities. True or False?        Mark for Review
1290(1) Points
1291                True
1292                False (*)
1293
12949.            In an ERD, it is a good idea to group your entities according to the expected volumes. By grouping high volume entities together, the diagrams could become easier to read. True or False?       Mark for Review
1295(1) Points
1296                True (*)
1297                False
1298
129910.          No formal rules exist for drawing ERD's. The most important thing is to make sure that all entities, attributes, and relationships are documented on the diagram, and the diagram is clear and readable. True or False?              Mark for Review
1300(1) Points
1301                True (*)
1302                False
1303
130411.          How do you know when to use the different types of time in your design?          Mark for Review
1305(1) Points
1306
1307                You would first determine the existence of the concept of time and map it against the Greenwich Mean Time.
1308                Always model time; you can take it out later if it is not needed.
1309                The rules are fixed and should be followed.
1310                It depends on the functional needs of the system . (*)
1311
131212.          All systems must have an entity called WEEK with a holiday attribute so that you know when to give employees a holiday. True or False?        Mark for Review
1313(1) Points
1314                True
1315                False (*)
1316
131713.          When a relationship may or may not be transferable, depending on time, this is know as a/an:  Mark for Review
1318(1) Points
1319                Conditional Non-transferable Relationship. (*)
1320                Transferable Relationship
1321                Non-transferable Relationship.
1322                Arc.
1323
132414.          Which of the following would be a logical constraint when modeling time for a country entity?   Mark for Review
1325(1) Points
1326                Daily traffic patterns must be monitored to determine which countries are overcrowded.
1327                Countries may change their names and/or borders over a period of time. (*)
1328                People have births and deaths in their countries that must be tracked by the system.
1329                If you are doing a system for France or Germany, you would need security clearance.
1330
133115.          Which of the following would be a logical constraint when modeling time for a City entity?           Mark for Review
1332(1) Points
1333
1334                Cites may change their names and/or country association if the borders of a country change. (*)
1335
1336                Daily traffic patterns must be monitored to determine how many law enforcement officers are needed.
1337
1338                People are born in the city and people die in the city.
1339
1340
1341                If you are doing a system for any French City, you would need security clearance.
1342
1343Section 9 Quiz
1344            (Answer all questions in this section)
13451.         When translating an arc relationship to a physical design, you must turn the arc relationships into foreign keys. What additional step must you take with the created foreign keys to ensure the exclusivity principle of arc relationships? (Assume that you are implementing an Exclusive Design) (Choose Two)     Mark for Review
1346(1) Points
1347                                    (Choose all correct answers)  
1348            Make all relationships mandatory
1349            Make all relationships optional (*)
1350
1351            Create an additional check constraint to verify that one foreign key is populated and the others are not (*)
1352
1353            All the above
1354
1355
13562.         Which of the following is a valid reason for considering a Subtype Implementation?          Mark for Review
1357(1) Points
1358            The common access paths for the supertypes are different.
1359            The resulting table will reside in a single database and be used by just ONE user.
1360
1361            Business functionality, business rules, access paths, and frequency of access are all very different between the subtypes. (*)
1362
1363            Most of the relationships are at the supertype level.
1364
13653.         When mapping supertypes, relationships at the supertype level transform as usual. Relationships at subtype level are implemented as foreign keys, but the foreign key columns all become mandatory. True or False?  Mark for Review
1366(1) Points
1367            True
1368            False (*)
1369
13704.         In an Oracle database, why would 1_TABLE not work as a table name?     Mark for Review
1371(1) Points
1372            The database does not understand all capital letters.
1373            TABLE is a reserved word.
1374            There is no problem here. You can create a table called 1_TABLE.
1375            Object names must not start with a number. They must begin with a letter. (*)
1376
13775.         In an Oracle database, why would the following table name not be allowed 'EMPLOYEE JOBS'?            Mark for Review
1378(1) Points
1379            The database does not understand all capital letters
1380            JOBS is a reserved word
1381            EMPLOYEE is a reserved word
1382            You cannot have spaces between words in a table name (*)
1383
13846.         Why would this table name NOT work in an Oracle database? this_year_end+next_year   Mark for Review
1385(1) Points
1386            Table names must begin with an alphabetic character.
1387            It is too long.
1388            The Plus sign + is not allowed in object names. (*)
1389            None of the above.
1390
13917.         In a physical data model, an attribute becomes a _____________.   Mark for Review
1392(1) Points
1393            Constraint
1394            Table
1395            Foreign Key
1396            Column (*)
1397
13988.         To resolve a many to many relationship in a physical model you create a(n) ___________________?            Mark for Review
1399(1) Points
1400            Unique key constraints
1401            Intersection entity
1402            Intersection table (*)
1403            Two tables with Foreign key constraints between them
1404
14059.         When an Arc is transformed to the physical model every relationship in the Arc becomes a mandatory Foreign Key. True or False?    Mark for Review
1406(1) Points
1407            True
1408            False (*)
1409
141010.       The Oracle Database can implement a many to many relationship. You simply create two foreign keys between the two tables. True or False?           Mark for Review
1411(1) Points
1412            True
1413            False (*)
1414
141511.       A barrred Relationship will result in a Foreign Key column that also is part of:        Mark for Review
1416(1) Points
1417            The Primary Key (*)
1418            The Column Name
1419            The Check Constraint
1420            The Table Name
1421
142212.       Column integrity refers to       Mark for Review
1423(1) Points
1424            Columns always containing positive numbers
1425            Columns always containing values consistent with the defined data format (*)
1426            Columns always containing text data less than 255 characters
1427            Columns always having values
1428
142913. The explanation below is an example of which constraint type?
1430A column must contain only values consistent with the defined data format of the column            Mark for Review
1431(1) Points
1432            Column integrity (*)
1433            User-defined integrity
1434            Referential integrity
1435            Entity integrity
1436
143714.       Identify all of the incorrect statements that complete this sentence: A primary key is...(Choose three)            Mark for Review
1438(1) Points
1439                                    (Choose all correct answers)  
1440            Only one column that must be null. (*)
1441            A single column that uniquely identifies each column in a table. (*)
1442            One or more columns in a table that uniquely identifies each row in that table.
1443            A set of columns in one table that uniquely identifies each row in another table. (*)
1444
144515.       Identify all of the correct statements that complete this sentence: A primary key is: (Choose Three)            Mark for Review
1446(1) Points
1447                                    (Choose all correct answers)  
1448            Only one column that cannot be null
1449
1450            A set of columns and keys in a single table that uniquely identifies each row in a single table (*)
1451
1452            A single column that uniquely identifies each row in a table (*)
1453            A set of columns that uniquely identifies each row in a table (*)
1454
14551.         The explanation below is an example of which constraint type?
1456A column must contain only values consistent with the defined data format of the column            Mark for Review
1457(1) Points
1458            User-defined integrity
1459            Column integrity (*)
1460            Referential integrity
1461            Entity integrity
1462
14632.         Identify all of the correct statements that complete this sentence: A primary key is: (Choose Three)            Mark for Review
1464(1) Points
1465                                    (Choose all correct answers)  
1466
1467            A set of columns and keys in a single table that uniquely identifies each row in a single table (*)
1468            Only one column that cannot be null
1469            A single column that uniquely identifies each row in a table (*)
1470            A set of columns that uniquely identifies each row in a table (*)
1471
14723.         Identify all of the incorrect statements that complete this sentence: A primary key is...(Choose three)            Mark for Review
1473(1) Points
1474                                    (Choose all correct answers)  
1475            A single column that uniquely identifies each column in a table. (*)
1476            One or more columns in a table that uniquely identifies each row in that table.
1477            Only one column that must be null. (*)
1478            A set of columns in one table that uniquely identifies each row in another table. (*)
1479
14804. Foreign keys cannot be null when  Mark for Review
1481(1) Points
1482            It refers to another table
1483            It is part of a primary key (*)
1484            It contains three or more columns
1485            It refers to the same table
1486
14875.         When mapping supertypes, relationships at the supertype level transform as usual. Relationships at subtype level are implemented as foreign keys, but the foreign key columns all become mandatory. True or False?  Mark for Review
1488(1) Points
1489            True
1490            False (*)
1491
14926.         When mapping supertypes, relationships at the supertype level transform as usual. Relationships at the subtype level are implemented as foreign keys, but the foreign key columns all become optional. True or False?            Mark for Review
1493(1) Points
1494            True (*)
1495            False
1496
14977.         The "Arc Implementation" is a synonym for what type of implementation? Mark for Review
1498(1) Points
1499            Supertype and Subtype Implementation (*)
1500            Cascade Implementation
1501            Supertype Implementation
1502            Subtype Implementation
1503
15048.         The Physical model is created by transforming which of the following models?      Mark for Review
1505(1) Points
1506            Constraint
1507            Table
1508            Physical
1509            Conceptual (*)
1510
15119.         Why would this table name NOT work in an Oracle database? this_year_end+next_year   Mark for Review
1512(1) Points
1513            Table names must begin with an alphabetic character.
1514            It is too long.
1515            The Plus sign + is not allowed in object names. (*)
1516            None of the above.
1517
151810.       In an Oracle database, why would 1_TABLE not work as a table name?     Mark for Review
1519(1) Points
1520            There is no problem here. You can create a table called 1_TABLE.
1521            The database does not understand all capital letters.
1522            TABLE is a reserved word.
1523            Object names must not start with a number. They must begin with a letter. (*)
1524
152511.       Attributes become columns in a database table. True or False?         Mark for Review
1526(1) Points
1527            True (*)
1528            False
1529
153012.       Relationships on an ERD can only be transformed into UIDs in the physical model? True or False?            Mark for Review
1531(1) Points
1532            True
1533            False (*)
1534
153513.       An Arc is transformed to the physical model by adding a foeign Key for every relationship in the Arc. True or False?  Mark for Review
1536(1) Points
1537            True (*)
1538            False
1539
154014.       One-to-One relationships are transformed into Check Constraints in the tables created at either end of that relationship. True or False?          Mark for Review
1541(1) Points
1542            True
1543            False (*)
1544
154515.       One-to-One relationships are transformed into Foreign Keys in the tables created at either end of that relationship. True or False?     Mark for Review
1546(1) Points
1547            True
1548            False (*)
1549
15501.         When mapping supertypes, relationships at the supertype level transform as usual. Relationships at subtype level are implemented as foreign keys, but the foreign key columns all become mandatory. True or False?  Mark for Review
1551(1) Points
1552            True
1553            False (*)
1554
15552.         Which of the following is a valid reason for considering a Subtype Implementation?          Mark for Review
1556(1) Points
1557            The common access paths for the supertypes are different.
1558
1559            Business functionality, business rules, access paths, and frequency of access are all very different between the subtypes. (*)
1560
1561            Most of the relationships are at the supertype level.
1562            The resulting table will reside in a single database and be used by just ONE user.
1563
15643.         The "Arc Implementation" is a synonym for what type of implementation? Mark for Review
1565(1) Points
1566            Supertype and Subtype Implementation (*)
1567            Supertype Implementation
1568            Cascade Implementation
1569            Subtype Implementation
1570
15714.         In a physical data model, an attribute becomes a _____________.   Mark for Review
1572(1) Points
1573            Constraint
1574            Column (*)
1575            Table
1576            Foreign Key
1577                                                           
15785.The conceptual model is transformed into a physical model. The physical implementation will be a relational database. True or False?          Mark for Review
1579(1) Points
1580            True (*)
1581            False
1582
15836.         In an Oracle database, why would the following table name not be allowed 'EMPLOYEE JOBS'?            Mark for Review
1584(1) Points
1585            The database does not understand all capital letters
1586            JOBS is a reserved word
1587            You cannot have spaces between words in a table name (*)
1588            EMPLOYEE is a reserved word
1589
15907. In an Oracle database, why would 1_TABLE not work as a table name? Mark for Review
1591(1) Points
1592            There is no problem here. You can create a table called 1_TABLE.
1593            Object names must not start with a number. They must begin with a letter. (*)
1594            The database does not understand all capital letters.
1595            TABLE is a reserved word.
1596
15978.         When an Arc is transformed to the physical model every relationship in the Arc becomes a mandatory Foreign Key. True or False?    Mark for Review
1598(1) Points
1599            True
1600            False (*)
1601
16029.         One-to-Many Optional to Mandatory becomes a _______________ on the Master table.   Mark for Review
1603(1) Points
1604            Optional Foreign Key (*)
1605            Unique Key
1606            Primary Key
1607            Mandatory Foreign Key
1608
160910.       An Arc is transformed to the physical model by adding a foeign Key for every relationship in the Arc. True or False?  Mark for Review
1610(1) Points
1611            True (*)
1612            False
1613
161411.       A barrred Relationship will result in a Foreign Key column that also is part of:        Mark for Review
1615(1) Points
1616            The Check Constraint
1617            The Column Name
1618            The Table Name
1619            The Primary Key (*)
1620
162112.       Foreign keys must be null. True or False?       Mark for Review
1622(1) Points
1623            True
1624            False (*)
1625
162613.       The explanation below is an example of which constraint type?
1627A primary key must be unique, and no part of the primary key can be null.  Mark for Review
1628(1) Points
1629            Column integrity
1630            User-defined integrity
1631            Referential integrity
1632            Entity integrity (*)
1633
163414.       Identify all of the incorrect statements that complete this sentence: A primary key is...(Choose three)            Mark for Review
1635(1) Points
1636                                    (Choose all correct answers)  
1637            A set of columns in one table that uniquely identifies each row in another table. (*)
1638            One or more columns in a table that uniquely identifies each row in that table.
1639            Only one column that must be null. (*)
1640            A single column that uniquely identifies each column in a table. (*)
1641
164215.       A foreign key always refers to a primary key in the same table. True or False?         Mark for Review
1643(1) Points
1644            True
1645            False (*)
1646
16471.         The conceptual model is transformed into a physical model. The physical implementation will be a relational database. True or False?      Mark for Review
1648(1) Points
1649            True (*)
1650            False
1651
16522. In an Oracle database, why would the following table name not be allowed 'EMPLOYEE JOBS'?       Mark for Review
1653(1) Points
1654            You cannot have spaces between words in a table name (*)
1655            The database does not understand all capital letters
1656            EMPLOYEE is a reserved word
1657            JOBS is a reserved word
1658
16593.         Attributes become columns in a database table. True or False?         Mark for Review
1660(1) Points
1661            True (*)
1662            False
1663
16644. The transformation from an ER diagram to a physical design involves changing terminology. Entities in the ER diagram become __________ :     Mark for Review
1665(1) Points
1666            Unique Keys
1667            Tables (*)
1668            Columns
1669            Foreign Keys
1670
16715.         Foreign keys must be null. True or False?       Mark for Review
1672(1) Points
1673            True
1674            False (*)
1675
16766.         A table does not have to have a primary key. True or False? Mark for Review
1677(1) Points
1678            True (*)
1679            False
1680
16817.         The explanation below is an example of which constraint type?
1682If the value in the balance column of the ACCOUNTS table is below 100, we must send a letter to the account owner which will require extra programming to enforce.     Mark for Review
1683(1) Points
1684            Column integrity
1685            Referential integrity
1686            Entity integrity
1687            User-defined integrity (*)
1688
16898.         Column integrity refers to       Mark for Review
1690(1) Points
1691            Columns always containing text data less than 255 characters
1692            Columns always containing positive numbers
1693            Columns always containing values consistent with the defined data format (*)
1694            Columns always having values
1695
16969.         Which of the following is a valid reason for considering a Subtype Implementation?          Mark for Review
1697(1) Points
1698            The resulting table will reside in a single database and be used by just ONE user.
1699            The common access paths for the supertypes are different.
1700            Most of the relationships are at the supertype level.
1701
1702            Business functionality, business rules, access paths, and frequency of access are all very different between the subtypes. (*)
1703
170410.       An "Arc Implementation" can be done just like any other Relationship - you simply add the required Foreign Keys. True or False?  Mark for Review
1705(1) Points
1706            True
1707            False (*)
1708
170911.       When mapping supertypes, relationships at the supertype level transform as usual. Relationships at the subtype level are implemented as foreign keys, but the foreign key columns all become optional. True or False?            Mark for Review
1710(1) Points
1711            True (*)
1712            False
1713
171412.       To resolve a many to many relationship in a physical model you create a(n) ___________________?            Mark for Review
1715(1) Points
1716            Two tables with Foreign key constraints between them
1717            Intersection table (*)
1718            Unique key constraints
1719            Intersection entity
1720
172113.       Relationships on an ERD can only be transformed into UIDs in the physical model? True or False?            Mark for Review
1722(1) Points
1723            True
1724            False (*)
1725
172614.       The Oracle Database can implement a many to many relationship. You simply create two foreign keys between the two tables. True or False?           Mark for Review
1727(1) Points
1728            True
1729            False (*)
1730
173115.       One-to-One relationships are transformed into Check Constraints in the tables created at either end of that relationship. True or False?          Mark for Review
1732(1) Points
1733            True
1734            False (*)
1735
17361.         When mapping supertypes, relationships at the supertype level transform as usual. Relationships at the subtype level are implemented as foreign keys, but the foreign key columns all become optional. True or False?            Mark for Review
1737(1) Points
1738            True (*)
1739            False
1740
17412.         When mapping supertypes, relationships at the supertype level transform as usual. Relationships at subtype level are implemented as foreign keys, but the foreign key columns all become mandatory. True or False?  Mark for Review
1742(1) Points
1743            True
1744            False (*)
1745
17463.         Which of the following is a valid reason for considering a Subtype Implementation?          Mark for Review
1747(1) Points
1748
1749            Business functionality, business rules, access paths, and frequency of access are all very different between the subtypes. (*)
1750
1751            Most of the relationships are at the supertype level.
1752            The common access paths for the supertypes are different.
1753            The resulting table will reside in a single database and be used by just ONE user.
1754
17554.         The explanation below is an example of which constraint type?
1756A column must contain only values consistent with the defined data format of the column            Mark for Review
1757(1) Points
1758            Column integrity (*)
1759            User-defined integrity
1760            Entity integrity
1761            Referential integrity
1762
17635.         A table must have a primary key. True or False?        Mark for Review
1764(1) Points
1765            True
1766            False (*)
1767
17686.         Identify all of the incorrect statements that complete this sentence: A primary key is...(Choose three)            Mark for Review
1769(1) Points
1770                                    (Choose all correct answers)  
1771            A single column that uniquely identifies each column in a table. (*)
1772            A set of columns in one table that uniquely identifies each row in another table. (*)
1773            Only one column that must be null. (*)
1774            One or more columns in a table that uniquely identifies each row in that table.
1775
17767.         The explanation below is an example of which constraint type?
1777The value in the dept_no column of the EMPLOYEES table must match a value in the dept_no column in the DEPARTMENTS table.         Mark for Review
1778(1) Points
1779            Referential integrity (*)
1780            Column integrity
1781            User-defined integrity
1782            Entity integrity
1783
17848.         In a physical model, many to many relationships are resolved via a structure called a(n): ________________    Mark for Review
1785(1) Points
1786            Intersection Entity
1787            Intersection Table (*)
1788            Subtype
1789            Supertype
1790
17919.         To resolve a many to many relationship in a physical model you create a(n) ___________________?            Mark for Review
1792(1) Points
1793            Two tables with Foreign key constraints between them
1794            Intersection entity
1795            Intersection table (*)
1796            Unique key constraints
1797
179810.       A barrred Relationship will result in a Foreign Key column that also is part of:        Mark for Review
1799(1) Points
1800            The Check Constraint
1801            The Column Name
1802            The Primary Key (*)
1803            The Table Name
1804
180511.       Relationships on an ERD can only be transformed into UIDs in the physical model? True or False?            Mark for Review
1806(1) Points
1807            True
1808            False (*)
1809
181012.       Attributes become columns in a database table. True or False?         Mark for Review
1811(1) Points
1812            True (*)
1813            False
1814
181513.       Why would this table name NOT work in an Oracle database? this_year_end+next_year   Mark for Review
1816(1) Points
1817            Table names must begin with an alphabetic character.
1818            It is too long.
1819            The Plus sign + is not allowed in object names. (*)
1820            None of the above.
1821
182214.       In an Oracle database, why would 1_TABLE not work as a table name?     Mark for Review
1823(1) Points
1824            TABLE is a reserved word.
1825            There is no problem here. You can create a table called 1_TABLE.
1826            The database does not understand all capital letters.
1827            Object names must not start with a number. They must begin with a letter. (*)
1828
182915.       In a physical data model, an attribute becomes a _____________.   Mark for Review
1830(1) Points
1831            Constraint
1832            Table
1833            Foreign Key
1834
1835            Column (*)