
Ultimate access to all questions.
A data engineering team is managing high-impact aggregate tables used for BI dashboards, machine learning models, and customer-facing applications. One customer-facing application requires renaming several existing fields and adding new ones to a shared aggregate table.
Which strategy allows the team to implement these schema changes for the application while ensuring zero disruption to other downstream consumers and minimizing the management overhead of additional physical tables?
A
Use Delta Lake’s deep clone functionality to create a new table with the required schema and synchronize changes between the original and new tables.
B
Communicate the schema changes to all organizational stakeholders and provide a migration guide for updating legacy queries to the new field names.
C
Create a new physical table with the updated schema for the application, then replace the original table name with a view that aliases the new table's fields to match the original schema.
D
Replace the current table with a logical view that maintains the existing query logic and create a completely separate physical table to support the customer-facing application.