Which columns define the identity and versioning in the CustomerMaster example?

Which columns define the identity and versioning in the CustomerMaster example?

• A. Customer ID and Address
• B. Customer ID and EffectiveDate
• C. Customer ID and Status
• D. Customer ID and CreatedDate

Answer: (B)

Identity is tied to the customer with a stable key, while versioning is captured by when the record becomes valid. Using the Customer ID with the EffectiveDate lets you distinguish each specific version of a customer’s data, because the same Customer ID can have multiple rows each with a different EffectiveDate representing different time periods. This setup supports temporal history, meaning you can track how the customer's information changes over time. Other columns like Address or Status can change, but they don’t by themselves define a unique version, and CreatedDate only marks when the row was created, not the period during which it’s valid. So the combination of Customer ID and EffectiveDate best defines both identity and versioning.

Identity is tied to the customer with a stable key, while versioning is captured by when the record becomes valid. Using the Customer ID with the EffectiveDate lets you distinguish each specific version of a customer’s data, because the same Customer ID can have multiple rows each with a different EffectiveDate representing different time periods. This setup supports temporal history, meaning you can track how the customer's information changes over time. Other columns like Address or Status can change, but they don’t by themselves define a unique version, and CreatedDate only marks when the row was created, not the period during which it’s valid. So the combination of Customer ID and EffectiveDate best defines both identity and versioning.