View the Exhibit to see the data in the emp table. You created a PRIMARY KEY constraint on the empno column of the emp table, and the constraint is not deferred. Which two statements are true in…

This is incorrect because Oracle always creates a unique index to support the enforcement of a PRIMARY KEY constraint.

Oracle automatically creates a unique B-tree index on the PRIMARY KEY column to enforce uniqueness efficiently; this index is created implicitly when the constraint is added.

A CHECK constraint is a separate, distinct constraint type used to enforce a condition on column values; PRIMARY KEY does not imply or create a CHECK constraint.

A PRIMARY KEY constraint implicitly enforces NOT NULL on the constrained column because a primary key value must uniquely identify each row and cannot be null.

Oracle creates a standard B-tree unique index for PRIMARY KEY constraints, not a bitmap unique index; bitmap indexes are used in data warehouse environments for low-cardinality columns.