You need to meet the design requirement for the ProductTypes table in the Product database. Which of the following would be the best solution?

A PRIMARY KEY constraint ensures that each row in the ProductTypes table is uniquely identified and prevents NULL values in the key column(s), but it does not enforce specific domain rules on the values themselves beyond uniqueness and non-nullability.

A CHECK constraint directly enforces domain integrity by limiting the range of values that can be entered into a column within the ProductTypes table. This allows the database designer to ensure that data conforms to specific business rules or predefined criteria, such as a value being within a certain range or matching a specific pattern.

A UNIQUE constraint ensures that all values in a specified column or set of columns in the ProductTypes table are distinct, but it does not enforce specific data value criteria or ranges.

A Data Definition Language (DDL) trigger responds to DDL events (e.g., CREATE TABLE, ALTER TABLE) and is used for auditing or controlling schema changes, not for enforcing data integrity rules on values inserted or updated within a table.

A FOREIGN KEY constraint enforces referential integrity by linking columns in the ProductTypes table to a primary or unique key in another table, ensuring consistency between related tables, but it does not define the valid range or format for values within ProductTypes columns independently.