Skip to content Skip to sidebar Skip to footer

Oracle Database Quiz Section 8 Quiz Answer

Image Source : dqindia.com


1.      Which of the following scenarios should be modeled so that historical data is kept? (Choose two)
BABY and AGE
CUSTOMER and ORDERS (*)
TEACHER and AGE
CUSTOMER and PAYMENTS (*)

2.      When modeling historical data the unique identifier is always made up of a barred relationship from the original two entities. True or False?
True
False (*)

3.      Which of the following scenarios should be modeled so that historical data is kept? (Choose two)
LIBRARY and BOOK (*)
STUDENT and GRADE (*)
STUDENT and AGE
LIBRARY and NUMBER OF BOOKS

4.      Which of the following statements are true for ERD's to enhance their readability.
You must ensure that you have every single entity--even if hundreds of them exist--on one single, big diagram.
The crows feet (many ends) can point whichever way is the easiest to draw.
Avoid crossing one relationship line with another. (*)
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. (*)

5.      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?
True (*)
False

6.      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
False (*)

7.      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?
True
False (*)

8.      All systems must include functionality to provide logging or journaling in conceptual data models. True or False?
True
False (*)

9.      Which of the following is a logical constraint that could result from considering how time impacts an example of data storage?
End Date must be before the Start Date.
EMPLOYEE periods can overlap causing the database to crash.
Dates must be stored with Time.
An ASSIGNMENT may only refer to an EMPLOYEE with a valid employee record at the Start Date of the ASSIGNMENT. (*)

10.    What is the function of logging or journaling in conceptual data models?
Represents entities as time in the data model.
Creates a fixed time for all events in a data model.
Gives a timestamp to all entities.
Allows you to track the history of attribute values, relationships, and/or entire entities (*)

11.    How do you know when to use the different types of time in your design?
It depends on the functional needs of the system . (*)
Always model time; you can take it out later if it is not needed.
You would first determine the existence of the concept of time and map it against the Greenwich Mean Time.
The rules are fixed and should be followed.

12.    Which of the following would be a logical constraint when modeling time for a country entity?
If you are doing a system for France or Germany, you would need security clearance.
Daily traffic patterns must be monitored to determine which countries are overcrowded.
Countries may change their names and/or borders over a period of time. (*)
People have births and deaths in their countries that must be tracked by the system.

13.    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?
True (*)
False

14.    Modeling historical data is optional. True or False?
True (*)
False

15.    When a relationship may or may not be transferable, depending on time, this is know as a/an:
Transferable Relationship
Non-transferable Relationship.
Conditional Non-transferable Relationship. (*)
Arc.


1.     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?
True
False (*)

2.     Which of the following statements are true for ERD's to enhance their readability. (Choose Two)
You must ensure that you have every single entity--even if hundreds of them exist--on one single, big diagram.
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. (*)
The crows feet (many ends) can point whichever way is the easiest to draw.
Avoid crossing one relationship line with another. (*)

3.     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?
True (*)
False

4.     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?
True
False (*)

5.     Which of the following scenarios should be modeled so that historical data is kept? (Choose two)
CUSTOMER and ORDERS (*)
CUSTOMER and PAYMENTS (*)
TEACHER and AGE
BABY and AGE

6.     Which of the following scenarios should be modeled so that historical data is kept? (Choose two)
LIBRARY and NUMBER OF BOOKS
STUDENT and GRADE (*)
LIBRARY and BOOK (*)
STUDENT and AGE

7.     Modeling historical data can produce a unique identifier that includes a date. True or False?
True (*)
False

8.     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?
True (*)
False

9.     Which of the following would be a logical constraint when modeling time for a City entity?
If you are doing a system for any French City, you would need security clearance.
People are born in the city and people die in the city.
Daily traffic patterns must be monitored to determine how many law enforcement officers are needed.
Cites may change their names and/or country association if the borders of a country change. (*)

10.  When you add the concept of time to your data model, your model becomes more complex. True or False?
True (*)
False

11.  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?
True (*)
False

12.  There are no circumstances where you would create a DAY entity. True or False?
True
False (*)

13.  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?
Email current prices to all employees whenever a price changes.
Update the prices in the system, print out the current prices when they change, and pin them on the company noticeboard.
Allow them to enter whatever delivery charge they want.
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. (*)

14.  Why would you want to model a time component when designing a system that lets people buy bars of gold?
The Government of your country might want to be notified of this transaction.
You would not want to model this; it is not important.
The price of gold fluctuates and, to determine the current price, you need to know the time of purchase. (*)
Sales people must determine where the gold is coming from.
15.  All systems must include functionality to provide logging or journaling in conceptual data models. True or False?
True
False (*)


1.     Which of the following scenarios should be modeled so that historical data is kept? (Choose two)
LIBRARY and BOOK (*)
STUDENT and AGE
LIBRARY and NUMBER OF BOOKS
STUDENT and GRADE (*)

2.     When modeling historical data the unique identifier is always made up of a barred relationship from the original two entities. True or False?
True
False (*)

3.     Which of the following scenarios should be modeled so that historical data is kept? (Choose two)
CUSTOMER and PAYMENTS (*)
CUSTOMER and ORDERS (*)
BABY and AGE
TEACHER and AGE

4.     When a relationship may or may not be transferable, depending on time, this is know as a/an:
Transferable Relationship
Non-transferable Relationship.
Conditional Non-transferable Relationship. (*)
Arc.

5.     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?
True

False (*)

6.     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?
True (*)
False

7.     When you add the concept of time to your data model, your model becomes more complex. True or False?
True (*)
False

8.     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?
True (*)
False

9.     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?
True (*)
False

10.  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?
True
False (*)

11.  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?
True (*)
False

12.  In an ERD, High Volume Entities usually have very few relationships to other entities. True or False?
True
False (*)

13.  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?
Email current prices to all employees whenever a price changes.
Update the prices in the system, print out the current prices when they change, and pin them on the company noticeboard.
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. (*)
Allow them to enter whatever delivery charge they want.

14.  Which of the following is a logical constraint that could result from considering how time impacts an example of data storage?
EMPLOYEE periods can overlap causing the database to crash.
Dates must be stored with Time.
End Date must be before the Start Date.
An ASSIGNMENT may only refer to an EMPLOYEE with a valid employee record at the Start Date of the ASSIGNMENT. (*)

15.  Why would you want to model a time component when designing a system that lets people buy bars of gold?
You would not want to model this; it is not important.
The Government of your country might want to be notified of this transaction.
The price of gold fluctuates and, to determine the current price, you need to know the time of purchase. (*)
Sales people must determine where the gold is coming from.


1.     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?
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.
B. Create a new item and a new price every day.
C. Use a price entity with a start and end date
D. Allow them to delete the item and enter a new one.
E. Both A and C (*)

2.     Which of the following is a logical constraint that could result from considering how time impacts an example of data storage?
An ASSIGNMENT may only refer to an EMPLOYEE with a valid employee record at the Start Date of the ASSIGNMENT. (*)
Dates must be stored with Time.
End Date must be before the Start Date.
EMPLOYEE periods can overlap causing the database to crash.
3.     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?
Update the prices in the system, print out the current prices when they change, and pin them on the company noticeboard.
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. (*)
Email current prices to all employees whenever a price changes.
Allow them to enter whatever delivery charge they want.

4.     Historical data must never be kept. True or False?
True
False (*)

5.     Modeling historical data can produce a unique identifier that includes a date. True or False?
True (*)
False

6.     Which of the following scenarios should be modeled so that historical data is kept? (Choose two)
BABY and AGE
TEACHER and AGE
CUSTOMER and ORDERS (*)
CUSTOMER and PAYMENTS (*)

7.     In an ERD, High Volume Entities usually have very few relationships to other entities.
True
False (*)

8.     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?
True (*)
False

9.     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?
True
False (*)

10.  Which of the following statements are true to enhance the readability of ERDs? (Choose Two)
Crossing relationship lines help the readability of the diagram.
Crows feet (the many-ends of relationships) should consistently point the same direction where possible, either South & East or North & West (*)
Relationship lines should not cross. (*)
It does not matter which way the crows feet (many ends of a relationship) point.

11.  Modeling historical data is optional. True or False?
True (*)
False

12.  When a relationship may or may not be transferable, depending on time, this is know as a/an:
Conditional Non-transferable Relationship. (*)
Arc.
Transferable Relationship
Non-transferable Relationship.

13.  When you add the concept of time to your data model, your model becomes more complex. True or False?
True (*)
False

14.  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?
True
False (*)

15.  How do you know when to use the different types of time in your design?
You would first determine the existence of the concept of time and map it against the Greenwich Mean Time.
The rules are fixed and should be followed.
Always model time; you can take it out later if it is not needed.
It depends on the functional needs of the system . (*)


1.     Which of the following scenarios should be modeled so that historical data is kept?
STUDENT and GRADE (*)
STUDENT and AGE
LIBRARY and BOOK (*)
LIBRARY and NUMBER OF BOOKS

2.     When modeling historical data the unique identifier is always made up of a barred relationship from the original two entities. True or False?
True
False (*)

3.     Modeling historical data can produce a unique identifier that includes a date. True or False?
True (*)
False

4.     All systems must include functionality to provide logging or journaling in conceptual data models. True or False?
True
False (*)

5.     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?
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.
B. Create a new item and a new price every day.
C. Use a price entity with a start and end date
D. Allow them to delete the item and enter a new one.
E. Both A and C (*)

6.     Which of the following is a logical constraint that could result from considering how time impacts an example of data storage?
End Date must be before the Start Date.
EMPLOYEE periods can overlap causing the database to crash.
An ASSIGNMENT may only refer to an EMPLOYEE with a valid employee record at the Start Date of the ASSIGNMENT. (*)
Dates must be stored with Time.

7.     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?
True
False (*)
8.     In an ERD, High Volume Entities usually have very few relationships to other entities. True or False?
True
False (*)

9.     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?
True (*)
False

10.  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?
True (*)
False

11.  How do you know when to use the different types of time in your design?
You would first determine the existence of the concept of time and map it against the Greenwich Mean Time.
Always model time; you can take it out later if it is not needed.
The rules are fixed and should be followed.
It depends on the functional needs of the system . (*)

12.  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?
True
False (*)

13.  When a relationship may or may not be transferable, depending on time, this is know as a/an:
Conditional Non-transferable Relationship. (*)
Transferable Relationship
Non-transferable Relationship.
Arc.

14.  Which of the following would be a logical constraint when modeling time for a country entity?
Daily traffic patterns must be monitored to determine which countries are overcrowded.
Countries may change their names and/or borders over a period of time. (*)
People have births and deaths in their countries that must be tracked by the system.
If you are doing a system for France or Germany, you would need security clearance.

15.  Which of the following would be a logical constraint when modeling time for a City entity?
Cites may change their names and/or country association if the borders of a country change. (*)
Daily traffic patterns must be monitored to determine how many law enforcement officers are needed.
People are born in the city and people die in the city.
If you are doing a system for any French City, you would need security clearance.

Post a Comment for "Oracle Database Quiz Section 8 Quiz Answer"