Section 4 Quiz (Answer all questions in this section)

1.   Business rules are important to data modelers because:  
A. They capture all of the needs, processes, and required functionality of the business. (*)  
B. All Business rules are easily implemented in the ERD diagram.  
C. The data modeler must focus on structural rules, because they are easily represented diagrammatically and eliminate other rules that involve extra procedures or programming.  
D. Both A and C are true.
 
  2.   Why is it important to identify and document business rules?
It allows you to create a complete data model and then check it for accuracy. (*)  
It allows you to improve the client's business.  
It ensures that the data model will automate all manual processes.  
None of the above


  3.   How would you model a business rule that states that girls and boys may not attend classes together?   
Use a supertype  
Make the attribute Gender mandatory  
Supertype STUDENT has two subtypes BOY and GIRL which are related to GENDER, which is related to CLASS (*)  
Make the attribute Gender optional
 
 
  4.   A business rule such as "All accounts must be paid in full within 10 days of billing" is best enforced by:  
Creating a message to be printed on every bill that reminds the customer to pay within ten days.  
Making the relationship between CUSTOMER and PAYMENT fully mandatory and 1:1 on both sides.  
Making the payment attribute mandatory.  
Creating additional programming code to identify and report accounts past due. (*)
 
 
  5.   Can all constraints be modeled on an ER diagram?   
Yes, all constraints must be modeled and shown on the ER diagram  
No, but you just explain them to the users so they can enforce them  
No, in which case you should let the database administrator handle them  
No, and those that cannot be modeled should be listed on a separate document to be handled programmatically (*)


6.   How would you model a business rule that states that on a student's birthday, he does not have to attend his classes?   
You cannot model this. You need to document it (*)  
Use a subtype  
Use a supertype  
Make the attribute Birthdate mandatory
 
 
  7.   How should you handle constraints that cannot be modeled on an ER diagram?  
Explain them to the users so they can enforce them  
All constraints must be modeled and shown on the ER diagram  
List them on a separate document to be handled programmatically (*)  
Always let the network architect handle them
 
 
  8.   Which of the following is true about subtypes?   
Subtypes must not be mutually exclusive.  
One instance of a supertype may belong to two subtypes.  
Subtypes must be mutually exclusive. (*)  
Subtypes should not be exhaustive.

   
  9.   A subtype can have a relationship not shared by the supertype. True or False?  
True (*)  
False
 
 
  10.   All instances of a subtype must be an instance of the supertype. True or False?   
True (*)  
False


11.   All instances of the supertype must be an instance of one of the subtypes. True or False?  
True (*)  
False

 
  12.   A supertype can only have two subtypes and no more. True or False?  
True 
False (*)

 
  13.   A Supertype can have only one subtype. True or False? 
True  
False (*)
 
 
  14.   A subtype is shown on an ERD as an entity with a one to many relationship to the supertype. True or False?  
True  
False (*)
 
 
  15.   All instances of a subtype may be an instance of the supertype but does not have to. True or False?   
True 
False (*)

Lanjutan... Database Design Section 5 Quiz

Download Source Code Program