Update payment records across multiple tables while preserving ACID transactions and existing SQL.
Use managed patching and backups for the database engine.
Which data store is most appropriate?
Use Amazon RDS or Aurora for a managed relational database with transactions and SQL compatibility.
Detailed explanation
Kinesis transports events and is not a relational transaction database.
Kinesis transports events and is not a relational transaction database.
OpenSearch is for search and analytics, not normalized payment transactions.
OpenSearch is for search and analytics, not normalized payment transactions.
These managed relational databases support SQL transactions, backups, and patching.
These managed relational databases support SQL transactions, backups, and patching.
S3 stores objects but does not provide multi-table row updates and ACID transactions.
S3 stores objects but does not provide multi-table row updates and ACID transactions.
Check official documentation
Compare the following points with the official documentation.
Amazon RDS・AuroraのACID、バックアップ、Multi-AZ、読み取りレプリカの公式説明を確認する。
What to confirm
オブジェクト、ストリーム、検索ストアとトランザクションDBを区別できる。
Key points
- RDS
- Aurora
- ACID
- Relational database
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Transaction boundary
Confirm whether multiple rows and tables must commit atomically.
Operational responsibility
Backups, patches, recovery time, and read scaling remain design requirements even in a managed service.