County payroll requires ACID transactions, normalized employee and deduction tables, and strict foreign-key relationships. Which database approach best fits?
Select an answer to reveal the explanation.
Short Explanation
Payroll is like a careful ledger where every line has to balance and every employee row ties cleanly to deductions. Relational databases give you that strict table structure, ACID safety, and foreign keys. Caches, graphs-for-fun, and raw CSV dumps are the wrong tool for paycheck accuracy.
Full Explanation
Relational databases model structured data with schemas, normalization, and transactional integrity (ACID), which payroll and similar financial systems typically require. Key-value caches, specialty graph stores for social links, and unstructured object files do not provide the relational constraints and transactional guarantees described. Cloud+ emphasizes matching data model to workload needs.