Ultimate access to all questions.
The marketing team needs to share aggregated data with the sales organization, but the field names differ between teams and some marketing-specific fields are not approved for sales.
Which solution best resolves this scenario while prioritizing simplicity?
Explanation:
Option A is the simplest solution because creating a view allows the sales team to access only approved fields with aliased names without duplicating data. Views automatically reflect changes in the underlying table, avoiding the need for complex sync mechanisms (B, C) or pipeline modifications (D). B (DEEP CLONE) and C (CTAS + job) introduce data redundancy and maintenance overhead. D requires altering the production pipeline, increasing complexity.