Which two privileges can be restricted at the column level?

The correct answer is B. INSERT D. UPDATE. In SQL (particularly Oracle), INSERT and UPDATE are the only DML privileges that can be granted or restricted at the column level. This makes logical sense: both operations involve writing specific column values, so it's meaningful to say "you can insert into column X but not…

Implementing Basic Database Security

Question

Options

ASELECT
BINSERT
CREVOKE
DUPDATE
EGRANT
FDELETE

How the community answered

(25 responses)

B
92% (23)
C
4% (1)
E
4% (1)

Explanation

In SQL (particularly Oracle), INSERT and UPDATE are the only DML privileges that can be granted or restricted at the column level. This makes logical sense: both operations involve writing specific column values, so it's meaningful to say "you can insert into column X but not column Y," or "you can update salary but not employee_id."

Why the distractors are wrong:

A. SELECT - Cannot be column-restricted in Oracle; use a view instead to limit which columns a user can query.
C. REVOKE - Not a privilege at all; it's a DDL command used to remove privileges.
E. GRANT - Also not a privilege; it's the DDL command used to assign privileges.
F. DELETE - Deletes entire rows, so restricting it by column makes no semantic sense - it is always table-level only.

Memory tip: Think "I UPDATE columns" - the two privileges you can write to individual columns are Insert and Update. Anything that reads (SELECT), removes rows (DELETE), or is a command rather than a privilege (GRANT/REVOKE) cannot be scoped to a column.

Topics

#column-level privileges#Oracle privilege model#privilege restriction#user security

Community Discussion

No community discussion yet for this question.

Full 1Z0-116 Practice