Your user extension that you validated and tested earlier is now failing. What could be a possible cause?

• A. Authentication failure
• B. Sandbox expired
• C. Permissions changed
• D. Your custom ETL process changed the structure of the target table in ADW due to changes in the data structure at the source

Answer: (D)

When a previously validated extension starts failing, the most plausible reason is a change in the data contract between the source and the target, specifically the target table’s structure in ADW being altered by the ETL. The extension was validated against a known schema: a fixed set of columns, data types, and their order. If the ETL updates the target table to reflect new source data—adding, removing, or changing columns or data types—the extension’s mappings and commands no longer align with the actual table, causing failures. To fix this, synchronize and update the extension’s metadata and mappings to match the new target schema, adjust any SQL or data-type handling accordingly, and re-validate with sample data. Check the ETL logs and the target table definition to identify exactly what changed, then ensure the extension and target schema are in agreement.