DAS-C01 · Question #18
A hospital uses wearable medical sensor devices to collect data from patients. The hospital is architecting a near-real-time solution that can ingest the data securely at scale. The solution should…
The correct answer is D. Ingest the data using Amazon Kinesis Data Firehose to write the data to Amazon S3. Implement. Amazon Kinesis Data Firehose is a fully managed streaming service that requires zero infrastructure management, making it the lowest-operational-overhead option. Firehose natively supports data transformation via AWS Lambda as part of the delivery pipeline - you configure a…
Question
A hospital uses wearable medical sensor devices to collect data from patients. The hospital is architecting a near-real-time solution that can ingest the data securely at scale. The solution should also be able to remove the patient's protected health information (PHI) from the streaming data and store the data in durable storage. Which solution meets these requirements with the least operational overhead?
Options
- AIngest the data using Amazon Kinesis Data Streams, which invokes an AWS Lambda function
- BIngest the data using Amazon Kinesis Data Firehose to write the data to Amazon S3. Have
- CIngest the data using Amazon Kinesis Data Streams to write the data to Amazon S3. Have the
- DIngest the data using Amazon Kinesis Data Firehose to write the data to Amazon S3. Implement
How the community answered
(36 responses)- A3% (1)
- B8% (3)
- C19% (7)
- D69% (25)
Explanation
Amazon Kinesis Data Firehose is a fully managed streaming service that requires zero infrastructure management, making it the lowest-operational-overhead option. Firehose natively supports data transformation via AWS Lambda as part of the delivery pipeline - you configure a Lambda function to process each record (removing PHI) before Firehose writes the sanitized data to Amazon S3. S3 provides durable, highly available storage. This end-to-end solution (Firehose → Lambda transform → S3) requires no servers to manage, no consumer application code, and no scaling configuration. Option A uses Kinesis Data Streams, which requires building and managing a custom consumer application. Option C also uses Kinesis Data Streams, adding more operational burden. Option B uses Firehose but stores untransformed data first, which risks PHI exposure before the downstream process removes it.
Topics
Community Discussion
No community discussion yet for this question.