Can You Draw One Subtype to One Supertype
 |
| Image Source : dqindia.com |
1.
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.
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 :
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?
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?
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?
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?
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?
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?
True (*)
False
9.
A subtype is drawn on an ERD as an entity inside the "softbox" of the supertype. True or False?
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?
True
False (*)
11.
Which of the following is true about subtypes?
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 (*)
False
13.
A supertype can only have two subtypes and no more. True or False?
True
False (*)
14.
You can only create relationships to a Supertype, not to a Subtype. True or False?
True
False (*)
15.
A Supertype can have only one subtype.
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?
Use a supertype
Make the attribute Birthdate mandatory
You cannot model this. You need to document it (*)
Use a subtype
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.
A new system would have a mixture of both Procedural and Structural Business Rules as part of the documentation of that new system.
True (*)
False
4.
A business rule such as "All accounts must be paid in full within 10 days of billing" is best enforced by:
Creating additional programming code to identify and report accounts past due. (*)
Making the relationship between CUSTOMER and PAYMENT fully mandatory and 1:1 on both sides.
Making the payment attribute mandatory.
Creating a message to be printed on every bill that reminds the customer to pay within ten days.
5.
How should you handle constraints that cannot be modeled on an ER diagram?
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?
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.
7.
How would you model a business rule that states that girls and boys may not attend classes together?
Supertype STUDENT has two subtypes BOY and GIRL which are related to GENDER, which is related to CLASS (*)
Make the attribute Gender mandatory
Make the attribute Gender optional
Use a supertype
8.
A supertype can only have two subtypes and no more. True or False?
True
False (*)
9.
All instances of the supertype must be an instance of one of the subtypes. True or False?
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?
True
False (*)
11.
Which of the following is true about subtypes?
Subtypes should not be exhaustive.
Subtypes must not be mutually exclusive.
Subtypes must be mutually exclusive. (*)
One instance of a supertype may belong to two subtypes.
12.
You can only create relationships to a Supertype, not to a Subtype. True or False?
True
False (*)
13.
A subtype can have a relationship not shared by the supertype. True or False?
True (*)
False
14.
A Supertype can have only one subtype. True or False?
True
False (*)
15.
All instances of a subtype must be an instance of the supertype. True or False?
True (*)
False
1.
How would you model a business rule that states that girls and boys may not attend classes together?
Use a supertype
Supertype STUDENT has two subtypes BOY and GIRL which are related to GENDER, which is related to CLASS (*)
Make the attribute Gender optional
Make the attribute Gender 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:
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.
3.
A business rule such as "All accounts must be paid in full within 10 days of billing" is best enforced by:
Making the relationship between CUSTOMER and PAYMENT fully mandatory and 1:1 on both sides.
Making the payment attribute mandatory.
Creating a message to be printed on every bill that reminds the customer to pay within ten days.
Creating additional programming code to identify and report accounts past due. (*)
4.
Can all constraints be modeled on an ER diagram?
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?
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?
True (*)
False
7.
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
8.
All instances of a subtype may be an instance of the supertype but does not have to. True or False?
True
False (*)
9.
A subtype can have a relationship not shared by the supertype. True or False?
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?
True
False (*)
11.
You can only create relationships to a Supertype, not to a Subtype. True or False?
True
False (*)
12.
All ER diagrams must have one of each of the following: (Choose two)
At least one supertype and subtype
One or more Entities (*)
Relationships between entities (*)
Arcs
13.
Which of the following is true about subtypes?
Subtypes should not be exhaustive.
Subtypes must be mutually exclusive. (*)
Subtypes must not be mutually exclusive.
One instance of a supertype may belong to two subtypes.
14.
A Supertype can have only one subtype. True or False?
True
False (*)
15.
All instances of the supertype must be an instance of one of the subtypes. True or False?
True (*)
False
1.
A ______________ in Oracle SQL Developer Data Modeler is a set of accepted terms that can be used in the design.
Template
Glossary (*)
Validation Rule
Table
2.
An Entity Relationship model does not highlight the physical and database constraints. It is essential to transform the ER model into a relational model which can serve as the basis for defining the physical implementation of the database.
True (*)
False
3.
You can define naming standards in Oracle SQL Developer Data Modeler using _______________.
Glossary
Naming Templates
Design Rule Validations
All of the above can be used to define naming standards in Oracle SQL Data Modeler. (*)
4.
A ___________ model is the blue print to the actual database implementation and can be used as the basis for implementing any type of Database Management System (DBMS).
Database
Conceptual
Logical
Relational (*)
5.
The steps to convert a Logical model to a Relational model using the Oracle SQL Developer Data Modeler are :
Select the Logical model, Click the Engineer to Relational Model icon, Accept defaults, Click Engineer (*)
Click the Engineer to Relational Model icon, Select the Logical model, Click
Engineer, Accept defaults.
Select the Logical model, Accept defaults, Click the Engineer to Relational Model icon, Click Engineer
None of the above.
6.
When creating a database based on extracting metadata from an existing database or using the DDL code obtained from an implementation of an existing database, which data modeling approach would you choose?
Target Modeling
You cannot model this.
Bottom-Up Modeling (*)
Top-Down Modelling
7.
_______ Engineering is the process of creating a conceptual or logical model by extracting the information from an existing data source.
Target
Reverse (*)
Forward
Top-Down
8.
Converting a Relational model to a Logical model is called reverse engineering.
True (*)
False
9.
In Oracle SQL Data Modeler, the attribute that you assign as primary UID is automatically set to a mandatory attribute and will be engineered to a primary key in the relational model.
True (*)
False
10.
The Oracle SQL Data Modeler enables you to do all of the following except:
Store application data (*)
Create process, logical, relational and physical model
Capture business rules and information
Store metadata information
11.
Which of the following cannot be modeled using the Oracle SQL Data Modeler ?
Entities, attributes, UIDs
Supertype and subtype entities
Recursive Relationships
Arc relationships
All can be modeled. (*)
12.
In Oracle SQL Developer Data Modeler you can select select how you want to map your subtypes.
True (*)
False
13.
We can apply naming abbreviations using the .csv file containing the abbreviations
True (*)
False
14.
Primary key constraints should have a suffix of PKEY.
True
False (*)
15.
Constraints should be given meaningful names to make them easier to reference.
True (*)
False
Can You Draw One Subtype to One Supertype
Source: https://www.projectflakes.com/2019/03/oracle-database-quiz-section-4-answer.html