AWS Certified Database – Specialty — Question 298

A vehicle insurance company needs to choose a highly available database to track vehicle owners and their insurance details. The persisted data should be immutable in the database, including the complete and sequenced history of changes over time with all the owners and insurance transfer details for a vehicle.
The data should be easily verifiable for the data lineage of an insurance claim.
Which approach meets these requirements with MINIMAL effort?

Answer options

• A. Create a blockchain to store the insurance details. Validate the data using a hash function to verify the data lineage of an insurance claim.
• B. Create an Amazon DynamoDB table to store the insurance details. Validate the data using AWS DMS validation by moving the data to Amazon S3 to verify the data lineage of an insurance claim.
• C. Create an Amazon QLDB ledger to store the insurance details. Validate the data by choosing the ledger name in the digest request to verify the data lineage of an insurance claim.
• D. Create an Amazon Aurora database to store the insurance details. Validate the data using AWS DMS validation by moving the data to Amazon S3 to verify the data lineage of an insurance claim.

Correct answer: C

Explanation

Amazon QLDB is a fully managed ledger database that inherently provides a transparent, immutable, and cryptographically verifiable transaction log, making it the ideal fit for tracking sequenced history and verifying data lineage with minimal effort. Other database solutions like Amazon Aurora and Amazon DynamoDB do not offer built-in cryptographic immutability, requiring complex custom architectures to achieve the same result. Building a custom blockchain network would introduce significant administrative and development overhead compared to using a fully managed service like Amazon QLDB.