You need to recommend a SQL Server Integration Services (SSIS) package design that meets the ETL requirements. What should you include in the recommendation?

Adding new rows for changes implements a Type 2 SCD, which preserves full dimensional history by assigning a new surrogate key to each changed record rather than overwriting it; enabling inferred members allows the SSIS SCD component to insert placeholder dimension rows when fact records arrive referencing a member not yet loaded, preventing foreign key constraint failures and allowing the pipeline to complete successfully.

Updating non-key attributes in place describes a Type 1 SCD, which silently overwrites historical dimension values and destroys change history, violating any ETL requirement that implies tracking member changes over time.

Updating key attributes in dimension tables breaks referential integrity with existing fact table rows that hold the old surrogate key, causing orphaned fact records and is not a recognized SCD strategy.

Adding new rows while disabling inferred members causes the ETL pipeline to fail with a constraint error whenever a fact record arrives referencing a dimension member that has not yet been processed, making the design brittle.