Week 1 Graded Quiz :Managing Big Data with MySQL (Excel to MySQL: Analytic Techniques for Business Specialization) Answers 2025
Answer Key
-
Relational databases are based on
✔ Set theory
❌ Matrix algebra, ❌ Probability theory, ❌ Information theory -
YearsInBusiness in ER diagram is
✔ Derived attribute
❌ Unique, ❌ Candidate key, ❌ Composite attribute -
Cardinality constraints Doctor ↔ Outpatient Location
✔ A doctor can work at many outpatient locations, but does not have to work at any
❌ Other options -
Unique identification of doctors
✔ LicenseNo
❌ State, ❌ Either, ❌ Both -
Doctor_ID and OL_ID are called
✔ Primary keys
❌ Unique attributes, ❌ Foreign keys, ❌ Composite attributes/keys -
Most likely information stored in relational DB
✔ Metadata (file name, location, creation time)
❌ Pictures, ❌ Tweets, ❌ Texts -
Inference from relational schema
✔ A doctor can work at many outpatient locations, and an outpatient location can have many doctors working at it
❌ Other options -
Attributes to identify unique books
✔ BookName and BookPubDate
❌ BookName only, ❌ BookName + EditorID, ❌ BookName + WriterID -
True statements about foreign keys
✔ Foreign keys allow info in different tables to be linked
✔ Foreign keys refer to columns with unique values for every row in other tables
❌ Foreign keys always have the same name as primary key
❌ Foreign keys have unique values in their own table -
Tables needed to determine outpatient locations for Karen Smith
✔ 2 or 3, depending on strategy
❌ 1, ❌ 2, ❌ 3 -
Cardinality constraints Doctor ↔ Outpatient Location (repeat of Q3)
✔ An outpatient location must have at least 1 doctor working, can have many doctors
❌ Other options -
Technical terms for relational schema
✔ Entities → tables, ✔ Fields → columns, ✔ Tuples → rows -
Unique identifier for shows
✔ ShowDate and ShowVenue
❌ Other options -
Columns to combine transactions and departinfo
✔ “sku” → skuinfo, then “deptID” → deptinfo
❌ Other options -
Requirements for efficiency (set theory)
✔ Each row represents a unique instance
✔ Each column represents a unique category of information
✔ Single tables represent smallest logical parts
❌ No NULL values required
Summary Table: Relational Databases & ER Diagrams Quiz
| Q# | Topic | Answer / Key Insight |
|---|---|---|
| 1 | Mathematical basis | Set theory |
| 2 | Attribute type | Derived attribute |
| 3 | Cardinality Doctor ↔ Outpatient | Doctor can work at many; outpatient can have many |
| 4 | Unique doctor identifier | LicenseNo |
| 5 | Doctor_ID / OL_ID | Primary keys |
| 6 | Info for relational DB | Metadata |
| 7 | Data inference from schema | Many-to-many doctor ↔ outpatient |
| 8 | Unique book identification | BookName + BookPubDate |
| 9 | Foreign keys | Link tables, refer to unique columns in other tables |
| 10 | Tables for Karen Smith | 2 or 3 depending on strategy |
| 11 | Cardinality constraints | Outpatient must have ≥1 doctor, can have many |
| 12 | Technical terms | Entities → tables, Fields → columns, Tuples → rows |
| 13 | Unique identifier for shows | ShowDate + ShowVenue |
| 14 | Combine transactions → departinfo | sku → skuinfo → deptID → deptinfo |
| 15 | Set theory requirements | Unique rows, unique columns, smallest tables |