Your question is Handle Unstable Source Schemas. Take a moment with it on the right.
Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).
You are supporting a data pipeline that pulls records from an external API into a warehouse for reporting and downstream analytics. The source changes field names, adds nested objects, and sometimes returns partial or malformed payloads, which causes broken loads and missing metrics. The team needs a clear way to keep data flowing while preserving traceability and backfill options.
What would you do if a customer’s data source has unstable APIs or frequent schema changes?