A company uses Amazon Redshift as its data warehouse. A new table includes some columns that contain sensitive data and some columns that contain non-sensitive data. The data in the table eventually…

Question

Options

• AGrant the auditing team permission to read from the table
• BGrant all users read-only permissions to the columns that contain non-sensitive data
• CGrant all users read-only permissions to the columns that contain non-sensitive data
• DGrant the auditing team permission to read from the table

• A
  7% (3)
• B
  75% (33)
• C
  5% (2)
• D
  14% (6)

Explanation

Amazon Redshift supports column-level access control natively via GRANT statements on specific columns. The least operational overhead solution is to grant all users SELECT permission only on the non-sensitive columns of the table (column-level GRANT), and separately grant the auditing team SELECT permission on all columns (or the full table). This is done entirely through SQL GRANT statements with no additional infrastructure. Option A grants the auditing team full table access but does not restrict other users. Options C and D vary in approach but the canonical correct answer here is B, which uses column-level grants to enforce least privilege directly in Redshift's permission system without creating views or additional layers.

No community discussion yet for this question.