Soru

Zorluk: ZorDatabase and Storage Strategy

A utility enterprise is designing a new cloud-based smart-grid monitoring platform. The system handles two primary data workloads. First, a time-series telemetry ingest workload receives smart meter readings at a rate of 100,000100,000 writes/second with sub-millisecond latency. Second, an online transaction processing (OLTP) workload manages customer billing and subscription metadata. The billing metadata requires a disaster recovery strategy with a Recovery Time Objective (RTO) of less than 1515 minutes and a Recovery Point Objective (RPO) of less than 55 seconds across AWS regions. Additionally, weekly billing reports must be saved to object storage and securely shared with a third-party auditing AWS account. Encryption-at-rest is mandatory for these reports, and the primary account must maintain full control over the encryption key policy. Which database and storage architecture should a solutions architect design to satisfy these requirements with the lowest operational overhead?

  1. A
    Deploy Amazon DynamoDB with auto-scaling to ingest the smart meter telemetry. Deploy Amazon Aurora PostgreSQL in the primary region for billing metadata, and configure automated hourly snapshots copied to a secondary region. In a disaster recovery event, restore the database from the latest snapshot in the secondary region using AWS CloudFormation. Store the weekly reports in an Amazon S3 bucket encrypted with a KMS Customer Managed Key (CMK) and share them with the auditing account.
  2. B
    Deploy Amazon DynamoDB with auto-scaling to ingest the smart meter telemetry. Use a Multi-AZ deployment of Amazon RDS for PostgreSQL for the billing metadata, and configure the billing application to read from the standby database instance in the secondary Availability Zone to scale read capacity during report generation. Store the weekly reports in Amazon S3 encrypted with a KMS Customer Managed Key (CMK) and grant cross-account permissions via the key policy.
  3. Deploy Amazon DynamoDB with auto-scaling to ingest the smart meter telemetry. Deploy Amazon Aurora Global Database for the transactional billing metadata, utilizing cross-region replicas to achieve the target RPO. Store the weekly reports in an Amazon S3 bucket encrypted with a KMS Customer Managed Key (CMK), and configure both the KMS key policy and the S3 bucket policy to allow access to the auditing account.Cevap
  4. D
    Deploy Amazon DynamoDB with auto-scaling to ingest the smart meter telemetry. Deploy Amazon Aurora Global Database for the billing metadata to meet the cross-region disaster recovery requirements. Store the weekly reports in an Amazon S3 bucket encrypted with the default AWS-managed KMS key (aws/s3), and configure an S3 bucket policy that permits read access to the external auditing account.

Cevap

Deploy Amazon DynamoDB with auto-scaling for the telemetry data. Deploy Amazon Aurora Global Database for the transactional billing metadata, utilizing cross-region replicas. Store the weekly reports in an Amazon S3 bucket encrypted with a KMS Customer Managed Key (CMK), and configure both the KMS key policy and the S3 bucket policy to allow access to the auditing account.
The correct answer recommends using Amazon DynamoDB with auto-scaling to absorb the high-throughput write workload. For the OLTP workload, Amazon Aurora Global Database satisfies the strict disaster recovery constraints with a cross-region replication lag of less than 11 second and a rapid cross-region failover time. To share encrypted reports cross-account, a Customer Managed Key (CMK) is used because its key policy can be updated to trust the external auditing account principal alongside the S3 bucket policy.

Adım Adım Çözüm

1
Select storage for the high-volume NoSQL telemetry data.
Amazon DynamoDB with auto-scaling is selected.
DynamoDB is a fully managed NoSQL database that can natively scale to handle 100,000100,000 writes/second with sub-millisecond latency.
2
Determine the OLTP database replication configuration to satisfy RPO and RTO constraints.
Amazon Aurora Global Database is selected.
Aurora Global Database utilizes fast storage-level cross-region replication, offering an RPO of less than 11 second and an RTO of less than 11 minute via managed global failover.
3
Establish cross-account sharing and encryption configuration for the S3-hosted reports.
Use Amazon S3 with a Customer Managed Key (CMK), configuring both S3 bucket and KMS key policies.
Default AWS-managed keys (aws/s3) do not allow modification of their key policies, making them incompatible with cross-account access delegation. A Customer Managed Key (CMK) allows configuring key policy permissions for the external auditing account.

Anahtar Kavram

Selecting and configuring database engines and key management solutions based on performance, RTO/RPO, and security sharing requirements.
Tahmini Süre:3m 0s
Bu soruyu puanla