SAP-C02 · Question #153
A company runs an IoT platform on AWS. IoT sensors in various locations send data to the company's Node.js API servers on Amazon EC2 instances running behind an Application Load Balancer. The data…
The correct answer is C. Leverage Amazon Kinesis Data Streams and AWS Lambda to ingest and process the raw data E. Re-architect the database tier to use Amazon DynamoDB instead of an RDS MySQL DB instance. A: 6TB will not resolve the issue permanently. B: the issue in the question is writing issue. So why we need read replica! C: Kinesis is always best for IoT and load. D: does not make sense. E: the question does not say anything about keeping the same DB architect! Dynamo is so…
Question
A company runs an IoT platform on AWS. IoT sensors in various locations send data to the company's Node.js API servers on Amazon EC2 instances running behind an Application Load Balancer. The data is stored in an Amazon RDS MySQL DB instance that uses a 4 TB General Purpose SSD volume. The number of sensors the company has deployed in the field has increased over time, and is expected to grow significantly. The API servers are consistently overloaded and RDS metrics show high write latency. Which of the following steps together will resolve the issues permanently and enable growth as new sensors are provisioned, while keeping this platform cost-efficient? (Choose two.)
Options
- AResize the MySQL General Purpose SSD storage to 6 TB to improve the volume's IOPS
- BRe-architect the database tier to use Amazon Aurora instead of an RDS MySQL DB instance and
- CLeverage Amazon Kinesis Data Streams and AWS Lambda to ingest and process the raw data
- DUse AWS-X-Ray to analyze and debug application issues and add more API servers to match the
- ERe-architect the database tier to use Amazon DynamoDB instead of an RDS MySQL DB instance
How the community answered
(38 responses)- A8% (3)
- B32% (12)
- C45% (17)
- D16% (6)
Explanation
A: 6TB will not resolve the issue permanently. B: the issue in the question is writing issue. So why we need read replica! C: Kinesis is always best for IoT and load. D: does not make sense. E: the question does not say anything about keeping the same DB architect! Dynamo is so scalable, for indefinitely solution.
Community Discussion
No community discussion yet for this question.