Section 4 Quiz Database Design Oracle

Section 4 Quiz
(Answer all questions in this section)

1. A business rule such as "All accounts must be paid in full within 10
days of billing" is best enforced by: Mark for Review
(1) Points
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.
Creating additional programming code to identify and report accounts

past due. (*)
Making the payment attribute mandatory.
2. A business rule such as "We only ship goods after customers have
completely paid any outstanding balances on their account" is best enforced by:
Mark for Review
(1) Points
Creating additional programming code to verify no goods are shipped

until the account has been settled in full. (*)
Making the payment attribute null.
We need to trust our customers, and we know they will pay some day.
Making the payment attribute optional.
3. How should you handle constraints that cannot be modeled on an ER diagram? Mark
for Review
(1) Points
Always let the network architect handle them
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 (*)
4. Which of the following is an example of a structural business rule?

Mark for Review
(1) Points
All employees must belong to at least one department. (*)
All products will have a selling price no less than 30 % greater than
wholesale.
All overdue payments will have an added 10 % late fee.
Buildings to be purchased by the business must be current with
earthquake building code.
5. Can all constraints be modeled on an ER diagram? Mark for Review

(1) Points
No, and those that cannot be modeled should be listed on a separate

document to be handled programmatically (*)
No, in which case you should let the database administrator handle them
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
6. Why is it important to identify and document business rules?

Mark for Review
(1) Points
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
7. How would you model a business rule that states that girls and boys may
not attend classes together? Mark for Review
(1) Points
Supertype STUDENT has two subtypes BOY and GIRL which are related to
GENDER, which is related to CLASS (*)
Use a supertype
Make the attribute Gender optional
Make the attribute Gender mandatory
8. A subtype can have a relationship not shared by the supertype. True or

False? Mark for Review
(1) Points
True (*)
False
9. A subtype is drawn on an ERD as an entity inside the "softbox" of the

supertype. True or False? Mark for Review
(1) Points
True (*)
False
10. A subtype is shown on an ERD as an entity with a one to many relationship

to the supertype. True or False? Mark for Review
(1) Points
True
False (*)
11. Which of the following is true about subtypes? Mark for Review
(1) Points
One instance of a supertype may belong to two subtypes.
Subtypes should not be exhaustive.
Subtypes must be mutually exclusive. (*)
Subtypes must not be mutually exclusive.
12. All instances of a subtype must be an instance of the supertype. True or

(1) Points
True (*)
False
13. A supertype can only have two subtypes and no more. True or False?
Mark for Review
(1) Points
True
False (*)
14. You can only create relationships to a Supertype, not to a Subtype. True
or False? Mark for Review
(1) Points
True
False (*)
15. A Supertype can have only one subtype. True or False? Mark for
Review
(1) Points
True
False (*)
1. How would you model a business rule that states that on a student's
birthday, he does not have to attend his classes? Mark for Review
(1) Points
Use a supertype
Make the attribute Birthdate mandatory
You cannot model this. You need to document it (*)
Use a subtype

Mark for Review
(1) Points
accuracy. (*)
None of the above
3.A new system would have a mixture of both Procedural and Structural Business
Rules as part of the documentation of that new system. True or False? Mark for
Review
(1) Points
True (*)
False

(1) Points
past due. (*)

5. How should you handle constraints that cannot be modeled on an ER

diagram? Mark for Review
(1) Points
Always let the network architect handle them
List them on a separate document to be handled programmatically (*)
All constraints must be modeled and shown on the ER diagram
Explain them to the users so they can enforce them
6. Why is it important to identify and document structural rules?
Mark for Review
(1) Points
Ensures we know what data to store and how that data works together.
(*)
Ensures nothing. There are no benefits to be gained from documenting

your Structural Business Rules. We need to concentrate on the Procedural Business
Rules only.
Ensures we know what processes are in place and how to program them.
All of the Above.
(1) Points
Use a supertype
8. A supertype can only have two subtypes and no more. True or False?
Mark for Review
(1) Points
True
False (*)
9. All instances of the supertype must be an instance of one of the

subtypes. True or False? Mark for Review
(1) Points
True (*)
False

(1) Points
True
False (*)
(1) Points
(1) Points
True
False (*)
(1) Points
True (*)
False
Review
(1) Points
True
False (*)
15. All instances of a subtype must be an instance of the supertype. True or

(1) Points
True (*)
False
(1) Points
Use a supertype
2. A business rule such as "We only ship goods after customers have
completely paid any outstanding balances on their account" is best enforced by:
Mark for Review
(1) Points
Making the payment attribute null.
Creating additional programming code to verify no goods are shipped

until the account has been settled in full. (*)
We need to trust our customers, and we know they will pay some day.
Making the payment attribute optional.

(1) Points

past due. (*)
4. Can all constraints be modeled on an ER diagram? Mark for Review

(1) Points
No, and those that cannot be modeled should be listed on a separate

document to be handled programmatically (*)
No, in which case you should let the database administrator handle them
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
5. How would you model a business rule that states that on a student's
birthday, he does not have to attend his classes? Mark for Review
(1) Points
Use a supertype
You cannot model this. You need to document it (*)
Make the attribute Birthdate mandatory
Use a subtype
6. A new system would have a mixture of both Procedural and Structural

Business Rules as part of the documentation of that new system. True or False?
Mark for Review
(1) Points
True (*)
False

Mark for Review
(1) Points
accuracy. (*)
None of the above
8. All instances of a subtype may be an instance of the supertype but does

not have to. True or False? Mark for Review
(1) Points
True
False (*)

(1) Points
True (*)
False

(1) Points
True
False (*)
(1) Points
True
False (*)
12. All ER diagrams must have one of each of the following: (Choose two)
Mark for Review
(1) Points
(Choose all correct answers)
At least one supertype and subtype
One or more Entities (*)
Relationships between entities (*)
Arcs
(1) Points
Review
(1) Points
True
False (*)
15. All instances of the supertype must be an instance of one of the
subtypes. True or False? Mark for Review
(1) Points
True (*)
False

Section 4 Quiz Database Design Oracle

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Section 4 Quiz Database Design Oracle

Uploaded by

Copyright:

Available Formats

Section 4 Quiz

(Answer all questions in this section)

Creating a message to be printed on every bill that reminds the

Making the relationship between CUSTOMER and PAYMENT fully mandatory

Creating additional programming code to identify and report accounts

Making the payment attribute mandatory.

Creating additional programming code to verify no goods are shipped

4. Which of the following is an example of a structural business rule?

5. Can all constraints be modeled on an ER diagram? Mark for Review

No, and those that cannot be modeled should be listed on a separate

6. Why is it important to identify and document business rules?

8. A subtype can have a relationship not shared by the supertype. True or

9. A subtype is drawn on an ERD as an entity inside the "softbox" of the

10. A subtype is shown on an ERD as an entity with a one to many relationship

12. All instances of a subtype must be an instance of the supertype. True or

2. Why is it important to identify and document business rules?

4. A business rule such as "All accounts must be paid in full within 10

Making the relationship between CUSTOMER and PAYMENT fully mandatory

5. How should you handle constraints that cannot be modeled on an ER

Ensures nothing. There are no benefits to be gained from documenting

All of the Above.

9. All instances of the supertype must be an instance of one of the

10. A subtype is shown on an ERD as an entity with a one to many relationship

15. All instances of a subtype must be an instance of the supertype. True or

Creating additional programming code to verify no goods are shipped

Making the payment attribute optional.

3. A business rule such as "All accounts must be paid in full within 10

Making the relationship between CUSTOMER and PAYMENT fully mandatory

4. Can all constraints be modeled on an ER diagram? Mark for Review

No, and those that cannot be modeled should be listed on a separate

6. A new system would have a mixture of both Procedural and Structural

7. Why is it important to identify and document business rules?

8. All instances of a subtype may be an instance of the supertype but does

9. A subtype can have a relationship not shared by the supertype. True or

10. A subtype is shown on an ERD as an entity with a one to many relationship

You might also like