A municipal asset registry must keep device rows consistent with site and owner tables, enforce foreign keys, and support ad-hoc joins under transactions. Which database type best fits that stated need?
Select an answer to reveal the explanation.
Short Explanation
City property records need ledgers that refuse orphan rows—the classic relational job. When joins, foreign keys, and transactions are the requirement, pick relational. Flattening into schemaless documents drops the integrity you asked for.
Full Explanation
Official DEVCOR database-type evaluation maps constraints, joins, and transactional integrity to relational stores. Document or time-series engines optimize other access patterns and do not replace relational integrity when that is the stated need. Topology diagrams alone do not mandate a graph database.