DEA-C01 · Question #202
A company stores customer data in an Amazon S3 bucket. Multiple teams in the company want to use the customer data for downstream analysis. The company needs to ensure that the teams do not have…
The correct answer is B. Use S3 Object Lambda to access the data, and use Amazon Comprehend to detect and remove. To ensure downstream analysis teams do not access personally identifiable information (PII) from customer data stored in Amazon S3, with the least operational overhead, the best solution is to use S3 Object Lambda with a Lambda function to dynamically detect and redact PII on…
Question
A company stores customer data in an Amazon S3 bucket. Multiple teams in the company want to use the customer data for downstream analysis. The company needs to ensure that the teams do not have access to personally identifiable information (PII) about the customers. Which solution will meet this requirement with LEAST operational overhead?
Options
- AUse Amazon Macie to create and run a sensitive data discovery job to detect and remove PII.
- BUse S3 Object Lambda to access the data, and use Amazon Comprehend to detect and remove
- CUse Amazon Data Firehose and Amazon Comprehend to detect and remove PII.
- DUse an AWS Glue DataBrew job to store the PII data in a second S3 bucket. Perform analysis on
How the community answered
(30 responses)- A17% (5)
- B70% (21)
- C3% (1)
- D10% (3)
Why each option
To ensure downstream analysis teams do not access personally identifiable information (PII) from customer data stored in Amazon S3, with the least operational overhead, the best solution is to use S3 Object Lambda with a Lambda function to dynamically detect and redact PII on access.
Amazon Macie is a data security and privacy service that discovers and reports on sensitive data, but it does not remove or redact PII from data files, thus failing to prevent access to PII for analysis teams.
S3 Object Lambda allows a Lambda function to process data retrieved from S3 on the fly, transforming it (e.g., redacting PII using Amazon Comprehend) before it reaches the requesting application, providing sanitized data without altering the original S3 objects or incurring overhead for pre-processed copies.
Amazon Data Firehose is designed for delivering streaming data to destinations and is not typically used for on-demand processing and redaction of existing data at rest in S3; it would involve re-ingesting data, which adds operational overhead.
Using AWS Glue DataBrew to store PII data in a second S3 bucket implies creating and managing a separate, potentially redacted, copy of the dataset, which increases storage, data duplication, and synchronization overhead compared to dynamic, on-access redaction.
Concept tested: S3 Object Lambda for dynamic data redaction
Source: https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lambda.html
Topics
Community Discussion
No community discussion yet for this question.