For optimum performance when applying data filters for data security, where should the data filter be placed?

For optimum performance when applying data filters for data security, where should the data filter be placed?

• A. Column level
• B. Row level
• C. Database level
• D. Table level

Answer: (D)

Focus on how a security rule is enforced in the data path. Putting the data filter at the table level lets the database engine apply the restriction as part of every query against that table, enabling the optimizer to push the predicate down, use existing indexes, and prune data early. This centralized enforcement keeps performance high because the filter is evaluated only once per access path and can leverage the table’s statistics and indexes. Column-level filtering tends to mask or hide specific columns rather than restrict which rows are visible, so it doesn’t provide comprehensive row-level access control. Row-level filtering is effective for per-user access but can add complexity and overhead across many tables if managed separately. Database-wide filtering is too broad and inflexible, potentially harming performance and control.

Focus on how a security rule is enforced in the data path. Putting the data filter at the table level lets the database engine apply the restriction as part of every query against that table, enabling the optimizer to push the predicate down, use existing indexes, and prune data early. This centralized enforcement keeps performance high because the filter is evaluated only once per access path and can leverage the table’s statistics and indexes.

Column-level filtering tends to mask or hide specific columns rather than restrict which rows are visible, so it doesn’t provide comprehensive row-level access control. Row-level filtering is effective for per-user access but can add complexity and overhead across many tables if managed separately. Database-wide filtering is too broad and inflexible, potentially harming performance and control.