Databricks Certified Data Engineer - Professional
Get started today
Ultimate access to all questions.
To minimize organizational disruption while meeting new requirements for a customer-facing application, how can the data engineering team rename and add fields to an aggregate table (used by multiple teams) while minimally interrupting other teams in the organization without increasing the number of tables that need to be managed?
(Note: The solution should maintain compatibility with existing BI dashboards, ML models, analytical queries, and other downstream workloads while addressing the specific needs of the customer-facing application.)
To minimize organizational disruption while meeting new requirements for a customer-facing application, how can the data engineering team rename and add fields to an aggregate table (used by multiple teams) while minimally interrupting other teams in the organization without increasing the number of tables that need to be managed?
(Note: The solution should maintain compatibility with existing BI dashboards, ML models, analytical queries, and other downstream workloads while addressing the specific needs of the customer-facing application.)
Exam-Like
A
Send all users notice that the schema for the table will be changing; include in the communication the logic necessary to revert the new table schema to match historic queries.
2.9%
B
Configure a new table with all the requisite fields and new names and use this as the source for the customer-facing application; create a view that maintains the original data schema and table name by aliasing select fields from the new table.
Comments
Loading comments...