DEA-C01 · Question #227
A company stores sensitive data in an Amazon Redshift table. The company needs to give specific users the ability to access the sensitive data. The company must not create duplication in the data…
The correct answer is A. Create a dynamic data masking policy to allow access based on each user role. Create IAM roles. Amazon Redshift's dynamic data masking lets you define masking policies on sensitive columns without duplicating data. You attach a masking policy that exposes only the last four characters to customer support IAM roles, while audit IAM roles see the full values. This meets the…
Question
A company stores sensitive data in an Amazon Redshift table. The company needs to give specific users the ability to access the sensitive data. The company must not create duplication in the data. Customer support users must be able to see the last four characters of the sensitive data. Audit users must be able to see the full value of the sensitive data. No other users can have the ability to access the sensitive information. Which solution will meet these requirements?
Options
- ACreate a dynamic data masking policy to allow access based on each user role. Create IAM roles
- BEnable metadata security on the Redshift cluster. Create IAM users and IAM roles for the
- CCreate a row-level security policy to allow access based on each user role. Create IAM roles that
- DCreate an AWS Glue job to redact the sensitive data and to load the data into a new Redshift
How the community answered
(54 responses)- A70% (38)
- B6% (3)
- C7% (4)
- D17% (9)
Explanation
Amazon Redshift's dynamic data masking lets you define masking policies on sensitive columns without duplicating data. You attach a masking policy that exposes only the last four characters to customer support IAM roles, while audit IAM roles see the full values. This meets the requirement for role-based column-level access with no data duplication.
Topics
Community Discussion
No community discussion yet for this question.