A medical diagnostics company is designing a new cloud-native patient monitoring and analytics platform. The platform must ingest high-velocity streaming telemetry data from wearable medical devices, which represents a write-heavy NoSQL workload. It must also store structured patient metadata requiring transactional consistency in an OLTP database. The platform must meet a recovery time objective (RTO) of less than 1 minute and a recovery point objective (RPO) of near-zero for disaster recovery. Additionally, all database storage must be encrypted using keys that can be audited by a centralized security account in another AWS organization.
Which of the following database and storage configurations should the solutions architect select to meet these requirements? (Select TWO.)
- Implement Amazon DynamoDB to ingest the streaming device telemetry, utilizing customer managed keys (CMKs) in AWS Key Management Service (AWS KMS) for encryption.Cevap
- Deploy Amazon Aurora PostgreSQL with Aurora Global Database across two AWS regions to store the patient metadata, utilizing regional Customer Managed Keys (CMKs) for encryption.Cevap
- CDeploy Amazon RDS for PostgreSQL with Multi-AZ enabled to store the patient metadata, and configure the application to route read-heavy analytical queries to the standby replica in the secondary Availability Zone.
- DStore the patient metadata in Amazon RDS for PostgreSQL, utilizing the default AWS-managed KMS key (aws/rds) for encryption, and configure a cross-account IAM policy to allow the central security account to manage the key.
- EFor the patient metadata database, implement a cross-region pilot light disaster recovery strategy where daily Amazon RDS snapshots are copied to a secondary region to minimize replication costs.