Using SQL it is possible to create
-
Column Constraint
-
Table Constraint
-
Both A. and B
-
None of the Above
SQL allows defining constraints at both column level (like NOT NULL or CHECK on a single column) and table level (like PRIMARY KEY, FOREIGN KEY, or UNIQUE that may involve multiple columns). Column constraints apply to individual columns, while table constraints can span multiple columns and enforce relationships.
SQL's CREATE TABLE/ALTER TABLE syntax supports constraints defined at the column level (inline with a column definition, e.g. NOT NULL, CHECK) as well as at the table level (declared separately, useful for multi-column constraints like composite primary keys or foreign keys). Since both forms are valid SQL constructs, the correct choice is that both are possible.