You need to recommend a solution for the planned changes to the customer classifications. What should you recommend? (Each correct answer presents part of the solution. Choose all that apply.)

Adding a new row to the Customers table each time a classification changes would violate normalization principles and introduce duplicate customer records, making it difficult to identify the current active customer record and causing data integrity issues.

Adding columns for each classification to the Customers table is a poor design pattern that creates sparse, wide tables and does not track the history or timing of classification changes, only storing a snapshot of current states.

Adding a separate table to track classification changes creates a proper audit/history trail, recording when each customer's classification changed, what it changed from and to, and timestamps - this is the standard approach for implementing a Type 2 slowly changing dimension or audit log without corrupting the base Customers table.

Adding a status column to the Classifications table allows the system to distinguish between currently active and previously active (historical) classifications for each customer, enabling queries to retrieve the current classification while preserving historical records without duplication.

Change Data Capture (CDC) is a SQL Server feature that captures low-level insert, update, and delete activity from transaction logs for ETL/replication purposes; it is not a recommended data modeling solution for business-level classification tracking and adds operational complexity without fulfilling the classification history requirement directly.