Reference no: EM13338925
1. In a relational database, entities are events. persons. things. All of the above
2. Physical design refers to developing a database model that will support company operations. purchasing your hardware components. selecting the specific hardware characteristics based on data storage and data access requirements. the process of converting your ERD into tables and defining your rows and columns based your entities and attributes.
3. All of the following explain index usage EXCEPT a primary field uses an index. adding an index to a table might decrease overall database performance slightly. an index can reduce the amount of time it takes for Access to run queries and reports. indexes are created using the Index property type.
4. All of the following should be considered in designing a relational database EXCEPT compliance with PNPI regulations. design for safety with redundant data. design your database for 100-year usage. store data in its smallest parts.
5. The term cardinality refers to a count of the total records in a table. a field which is a candidate for a primary key. the number of records in a relationship. the most important field in a table.
6. A primary key can be computer generated. consists of one field only that uniquely identifies each record in a table. is a relationship between two or more tables. All of the above.
7. Which does NOT apply to the following relationship image? A one-to-many relationship is shown between Orders and Order Details. The display is showing the Design View of relationships. Order Details has a composite primary key. Within the Orders Details table, the ProductID field will contain unique values only.
8. What Access data type would you use to store $23.58? Calculated Currency Money Number.
9. Validation text changes the way text data is formatted. determines the maximum length of a Text field. requires correct text data input. specifies the error message when a rule is violated.
10. Which question is part of a requirements analysis? What is the organization's structure and core business? What are the existing problems with the current database? Will the database interface with other systems? All of the above.