A column contains data that only a small compliance team may see, while the rest of the table is widely useful. What is the appropriate control?
Select an answer to reveal the explanation.
Short Explanation
You should apply a column-level policy that masks or restricts just the sensitive column. That keeps the table useful for everyone else while protecting the compliance-only field. Locking the whole table away solves the problem by destroying its value.
Full Explanation
The appropriate control is the policy that restricts or masks that column for other users, so the table remains usable while the sensitive attribute stays protected. Fine-grained control targets the sensitive attribute specifically, so general users keep the table's useful columns while the restricted one is masked or withheld and the control is enforced on every access path. The dashboard-level hiding approach is incorrect because it protects one presentation path; direct queries return the column unchanged. The approach that moves the whole table into a restricted schema so only compliance can query it is incorrect because restricting the entire table sacrifices legitimate broad use to protect one field - a heavy blunt instrument. The approach that adds a note in the table's description asking users not to select that column is incorrect because a request in a description is not enforced and produces no audit evidence. For the exam, match the granularity of the control to the granularity of the sensitivity.