Chapter 40 — Quiz
12 questions. Answers at the bottom.
Multiple choice
Q1. Which best describes a Database Administrator's focus? - A) Designing application UIs - B) Keeping databases running (config, backups, tuning, security, HA) - C) Writing only frontend code - D) Marketing
Q2. A Data Engineer primarily: - A) Designs logos - B) Builds pipelines that move/transform data (ETL/ELT, warehouses) - C) Only administers backups - D) Avoids SQL
Q3. The cloud's effect on the DBA role was to: - A) Eliminate it entirely - B) Evolve it (automate some toil; shift toward architecture/performance/scale) - C) Make SQL obsolete - D) Remove the need for databases
Q4. Why are database skills described as durable? - A) They change every year - B) The relational model/SQL have endured 50+ years and the need is permanent - C) Only DBAs use them - D) They're rarely needed
Q5. The most-tested skill in database interviews is: - A) Memorizing trivia - B) SQL fluency (joins, aggregation, window functions, CTEs) - C) Drawing logos - D) NoSQL only
Q6. Certifications are best understood as: - A) The deciding factor in hiring - B) A modest signal; demonstrated skill (a capstone, interview reasoning) matters more - C) Useless always - D) A replacement for skill
Q7. The strongest thing to show an employer is: - A) A list of buzzwords - B) A capstone project you can reason about and defend - C) A certificate alone - D) A long résumé
Q8. In an interview, "which database would you choose?" is best answered with: - A) "The newest one" - B) The decision framework (data model, workload, scale, consistency, ...) — trade-offs - C) "Whatever's trendy" - D) "I don't know"
Q9. "Talk in trade-offs, not absolutes" signals: - A) Indecision - B) The judgment of someone who understands, not just memorizes - C) Lack of knowledge - D) Arrogance
Q10. A senior role built on years of these skills, designing org-wide data strategy, is the: - A) Junior developer - B) Data Architect - C) Intern - D) Frontend developer
True/False
Q11. Demand for database/data skills is strong and durable across the industry. (True / False)
Q12. Once you finish this book, there's nothing left to learn about databases. (True / False)
Short answer
Q13. Name three things you can now do with databases that you couldn't before this book, and how you'd demonstrate each to an employer.
---
Answer key
Q1 — B. Keeping databases running and reliable.
Q2 — B. Building data pipelines/warehouses (SQL-heavy).
Q3 — B. Evolved the role; didn't eliminate it.
Q4 — B. The relational model/SQL endure; the need is permanent.
Q5 — B. SQL fluency.
Q6 — B. A modest signal; demonstrated skill matters more.
Q7 — B. A capstone you can reason about.
Q8 — B. The decision framework, in trade-offs.
Q9 — B. Judgment, not memorization.
Q10 — B. Data Architect.
Q11 — True. Every app/analytics/AI system needs a database; SQL is consistently in-demand.
Q12 — False. The foundation is permanent, but the field evolves (versions, vector/AI, cloud, distributed) — keep learning.
Q13. (Examples) Design a normalized schema — show your capstone's ER diagram + DDL and explain the normalization decisions. Fix a slow query — walk through an EXPLAIN-driven diagnosis and an index that took a query from seconds to milliseconds. Choose the right database — apply the decision framework to a scenario and justify the choice in trade-offs. Each is demonstrated by doing it (in the capstone or live in the interview), not by claiming it.
Scoring: any score — this quiz is a launchpad, not a gate. You finished the book; now go build.