A financial technology company is designing a new global payment settlement platform. The solution requires a highly available transactional metadata database (OLTP) to process high-throughput transaction records, alongside a high-volume NoSQL database for real-time audit logs. The OLTP database must support a cross-region disaster recovery strategy with a Recovery Point Objective (RPO) of less than 1 second and a Recovery Time Objective (RTO) of less than 1 minute. Additionally, during peak trading hours, the OLTP database must dynamically scale to support sudden read traffic spikes. All data stored in both database engines must be encrypted using customer-managed keys (CMKs) in AWS KMS, allowing a centralized security account to manage and rotate the keys. Which two database and storage configurations should the solutions architect choose to meet these requirements?
- Configure an Amazon Aurora Global Database with Aurora PostgreSQL. Set up Aurora Auto Scaling for the Aurora Replicas in both the primary and secondary regions to handle dynamic read scaling.Cevap
- Provision an Amazon DynamoDB table for audit logs with encryption enabled using Customer Managed Keys (CMKs), and update the KMS key policy in the security account to grant cross-account permissions.Cevap
- CConfigure Amazon RDS for PostgreSQL with a Multi-AZ deployment, and configure the application to direct read traffic to the standby instance to handle peak trading spikes.
- DSet up hourly cross-region copying of Amazon Aurora DB cluster snapshots to a secondary region, and write a script to restore the cluster if the primary region fails.
- EProvision an Amazon DynamoDB table for audit logs, encrypting the data with an AWS managed KMS key, and configure cross-account IAM roles to allow key administration from the centralized security account.