A municipal finance system needs a relational schema with SQL joins across budgets, vendors, and purchase orders. Which AWS database family fits that pattern?
Select an answer to reveal the explanation.
Short Explanation
If your data looks like spreadsheets that need to join on IDs—budgets to vendors to POs—you want a relational SQL database. On AWS that points to RDS or Aurora, not a cache, a cold object archive, or a suitcase appliance. Caches speed things up; they do not become your finance schema.
Full Explanation
Relational workloads that rely on structured schemas and SQL joins map to managed relational services such as Amazon RDS and Amazon Aurora. Amazon ElastiCache provides in-memory caching, Amazon S3 (including Glacier storage classes) provides object storage, and AWS Snowcone is an edge/data-transfer device—none are the primary relational SQL engine for municipal finance schemas.