Home › Forums › AWS › AWS Certified Solutions Architect Associate › Anonymized prior to landing in a NoSQL database for further processing
-
Anonymized prior to landing in a NoSQL database for further processing
Irene-TutorialsDojo updated 2 weeks, 4 days ago 2 Members · 2 Posts
-
question 7 is totally ambiguous.
It is saying that “It’s crucial that this sensitive information is anonymized prior to landing in a NoSQL database for further processing.”
And that:
The option that says: Create a data lake in Amazon S3 and use it as the primary storage for patient health data. Use an S3 trigger to run an AWS Lambda function that performs anonymization. Send the anonymized data to Amazon DynamoDB is incorrect. This approach only doesn’t guarantee the anonymization of data before it lands on DynamoDB. The data will first be stored in S3 and then anonymized, potentially exposing sensitive information. This violates the principle of ensuring PII is anonymized prior to storage.This answer should not be excluded because s3 is not a NoSQL database. So the health data is in S3 and is anonymized prior to landing in Dynamo (in a Lambda) so that’s ok.
You should change the statement “<b style=”font-family: inherit; font-size: inherit;”>It’s crucial that this sensitive information is anonymized prior to landing in a NoSQL database for further processing.” to something like:
It’s crucial that this sensitive information is anonymized prior to landing in any storage for further processing.
Words are important and many students will fail some questions because of AWS inacurate questions and that’s not fair.Regards
-
Hi jgofaws,
Thank you for your valuable feedback. We understand your concern regarding the statement, “sensitive information is anonymized prior to landing in a NoSQL database,” and how it might make Option 1 seem valid since Amazon S3 is not a NoSQL database, and data is anonymized before reaching Amazon DynamoDB. After reviewing your query, we agree that the wording could be more precise, which might cause confusion.
The intent of the original question was to ensure that no unanonymized PII is stored in any system, including S3, before it is anonymized. In Option 1, PII is stored in S3 before the anonymization process in Lambda, which does not meet this goal. To improve clarity, we will update the statement to: “sensitive information is anonymized prior to landing in any storage system before being stored in a NoSQL database.” We will also revise the explanation to better clarify why Option 1 is incorrect due to storing PII in S3 first.
We appreciate your input and are committed to providing clear and accurate questions. The updated version will be reflected soon. If you have further questions, feel free to reach out!
Best regards,
Irene @ Tutorials Dojo
Log in to reply.