DEA-C01 · Question #274
A company needs a solution to automatically ingest data from an Amazon S3 bucket to an Amazon Redshift table every day. The company must obfuscate sensitive data in Amazon Redshift. Users must not…
The correct answer is D. Configure an AWS Glue job to load the data into Amazon Redshift. Use Amazon Redshift to. Schedule an AWS Glue job to load S3 data into Amazon Redshift, then use Redshift’s built-in sensitive data discovery and dynamic data masking to identify sensitive columns and enforce masking at query time. This meets the daily ingest and non-plaintext visibility requirements…
Question
A company needs a solution to automatically ingest data from an Amazon S3 bucket to an Amazon Redshift table every day. The company must obfuscate sensitive data in Amazon Redshift. Users must not be able to view the sensitive data as plaintext. Which solution will meet these requirements with the LEAST operational overhead?
Options
- AEnable Amazon Macie for the company's AWS account. Configure a sensitive data discovery job
- BEnable Amazon Macie for the company's AWS account. Configure an AWS Glue job to flag and
- CConfigure an AWS Glue job to read the data from the S3 bucket, detect and obfuscate sensitive
- DConfigure an AWS Glue job to load the data into Amazon Redshift. Use Amazon Redshift to
How the community answered
(27 responses)- A7% (2)
- B33% (9)
- C15% (4)
- D44% (12)
Explanation
Schedule an AWS Glue job to load S3 data into Amazon Redshift, then use Redshift’s built-in sensitive data discovery and dynamic data masking to identify sensitive columns and enforce masking at query time. This meets the daily ingest and non-plaintext visibility requirements with the least operational overhead, since masking is managed natively in Redshift without custom obfuscation pipelines or Macie-based preprocessing.
Topics
Community Discussion
No community discussion yet for this question.