A healthcare provider is designing a new digital medical imaging archive and diagnostic report system. The system must store structured patient metadata logs (OLTP workload) and unstructured medical images in DICOM format (Object storage). The metadata database must support high-volume write transactions and scale read traffic to handle sudden spikes from hospital clients. The disaster recovery requirements demand a Recovery Time Objective (RTO) of minutes and a Recovery Point Objective (RPO) of minute. Additionally, for regulatory compliance, the medical images must be securely archived and replicated to a destination bucket in a secondary, isolated AWS account in a different AWS region, encrypted at rest using AWS KMS. Which of the following database and storage configurations should the solutions architect choose to meet these requirements? (Select TWO.)
- Deploy an Amazon Aurora global database with the primary cluster in the active region and a secondary cluster in the disaster recovery region, utilizing Aurora Replicas in both regions to handle database operations.Cevap
- BDeploy a Multi-AZ Amazon RDS PostgreSQL database in the primary region, and route read queries directly to the standby instance in the secondary Availability Zone to scale database performance during peak read hours.
- CConfigure hourly database snapshots in the primary region, and schedule an AWS Lambda function to copy these snapshots to the disaster recovery region every hours to reconstruct the database during a regional disaster.
- Store the medical images in Amazon S3, and configure S3 Cross-Region Replication (CRR) to a destination bucket in the disaster recovery region using a Customer Managed Key (CMK) in AWS KMS with appropriate cross-account key policies.Cevap
- EStore the medical images in Amazon S3, and configure S3 Cross-Region Replication (CRR) to a destination bucket in a secondary AWS account using the default AWS-managed KMS key (aws/s3) to simplify cross-account encryption configuration.