Identify common constraints beyond PK and FK that you would apply in Clarity.

Identify common constraints beyond PK and FK that you would apply in Clarity.

• A. Only PK/FK
• B. Not Null constraints only
• C. Default values and domain constraints only
• D. Unique constraints, check constraints, not null, default values, domain constraints, and referential actions

Answer: (D)

When modeling data in Clarity, you enforce data integrity by applying a range of constraints beyond just primary keys and foreign keys. Not Null constraints ensure that mandatory fields always contain a value, preventing incomplete records. Default values provide sensible, automatic values when data isn’t supplied, promoting consistency across records. Unique constraints extend beyond the primary key to enforce business rules that require certain fields to be distinct, such as codes or identifiers that must be unique within a domain. Domain constraints define what kinds of values are acceptable for a field—data type, length, allowed ranges, or specific enumerations—so data stays within the defined business rules. Check constraints let you express precise conditions that values must satisfy (for example, a date range or a value being non-negative). Referential actions control what happens to related data when a parent record changes or is deleted, ensuring consistency across relationships (such as cascading deletes or setting child references to null). Together, these constraints cover data validity, consistency, and business rules in ways that primary and foreign keys alone cannot. The other options miss important pieces: focusing only on PK/FK ignores data-value rules; limiting to Not Null ignores uniqueness, ranges, and pattern checks; and truncating to only defaults and domain constraints leaves out necessary checks, unique constraints, and the behaviors specified by referential actions.

When modeling data in Clarity, you enforce data integrity by applying a range of constraints beyond just primary keys and foreign keys. Not Null constraints ensure that mandatory fields always contain a value, preventing incomplete records. Default values provide sensible, automatic values when data isn’t supplied, promoting consistency across records. Unique constraints extend beyond the primary key to enforce business rules that require certain fields to be distinct, such as codes or identifiers that must be unique within a domain. Domain constraints define what kinds of values are acceptable for a field—data type, length, allowed ranges, or specific enumerations—so data stays within the defined business rules. Check constraints let you express precise conditions that values must satisfy (for example, a date range or a value being non-negative). Referential actions control what happens to related data when a parent record changes or is deleted, ensuring consistency across relationships (such as cascading deletes or setting child references to null). Together, these constraints cover data validity, consistency, and business rules in ways that primary and foreign keys alone cannot.

The other options miss important pieces: focusing only on PK/FK ignores data-value rules; limiting to Not Null ignores uniqueness, ranges, and pattern checks; and truncating to only defaults and domain constraints leaves out necessary checks, unique constraints, and the behaviors specified by referential actions.