1. In a physical data model, an entity becomes a/an _____________.
- Table (*)
- Constraint
- Column
- Attribute
2. In a physical data model, a relationship is represented as a:
- Primary Key
- Unique Identifier
- Column
- Foreign Key (*)
3. Attributes become columns in a database table. True or False?
- True (*)
- False
4. Why would this table name NOT work in an Oracle database?
2007_EMPLOYEES
- Numbers cannot be incorporated into table names
- Table names must start with an alphabetic character (*)
- Underscores "_" are not allowed in table names
- None of the above
5. In an Oracle database, why would the following table name not be allowed 'EMPLOYEE JOBS'?
- The database does not understand all capital letters
- JOBS is a reserved word
- EMPLOYEE is a reserved word
- You cannot have spaces between words in a table name (*)
6. The transformation from an ER diagram to a physical design involves changing terminology. Entities in the ER diagram become __________ , and attributes become ____________.
- Foreign Keys, Columns
- Tables, Foreign Keys
- Columns, Tables
- Tables, Columns (*)
7. The transformation from an ER diagram to a physical design involves changing terminology. Relationships in the ER diagram become __________ , and primary unique identifiers become ____________.
- Foreign keys, Optional business rules
- Foreign keys, Primary keys (*)
- Primary keys, Foreign keys
- Foreign keys, Mandatory business rules