A company uses Amazon Redshift as its data warehouse. A new table has columns that contain sensitive data. The data in the table will eventually be referenced by several existing queries that run…

Question

Options

• ALoad all the data into the new table and grant the auditing group permission to read from the
• BLoad all the data into the new table and grant the auditing group permission to read from the
• CLoad all the data into the new table and grant all users read-only permissions to non-sensitive
• DLoad all the data into the new table and grant the auditing group permission to read from the

• A
  14% (8)
• B
  76% (44)
• C
  3% (2)
• D
  7% (4)

Explanation

Amazon Redshift supports column-level access control, allowing you to GRANT SELECT on specific columns to specific users or groups. The correct approach is to load all 100 billion rows into the table (one operation, lowest overhead), then use column-level GRANT statements to give the auditing group SELECT access to the sensitive columns while restricting other users to non-sensitive columns only. This is a native Redshift security feature that requires no schema duplication, no views for masking, and no ongoing maintenance as queries reference the single table. Other options that involve splitting the data, creating multiple tables, or using views to mask columns all introduce maintenance overhead-especially at scale with many existing queries that will reference the table.

No community discussion yet for this question.