Answer: Switch the first partition from stg.Sales to dbo.Sales.

## Detailed Explanation ### Understanding Partition Switching Partition switching is a metadata-only operation in Azure Synapse Analytics that allows you to quickly exchange data between tables with identical schemas and partition structures. This operation is extremely fast because it doesn't physically move data - it only updates metadata pointers. ### Analysis of Options **Option C: Switch the first partition from stg.Sales to dbo.Sales** ✅ - **Optimal Choice**: This is the correct approach for minimizing load times - **How it works**: The partition switch operation instantly replaces the content of the first partition in dbo.Sales with the content from stg.Sales - **Performance**: This is a metadata-only operation that completes almost instantly, regardless of data volume - **Data Integrity**: Maintains transactional consistency during the switch **Option A: Insert the data from stg.Sales into dbo.Sales** ❌ - **Issue**: This requires physical data movement and processing - **Performance Impact**: Significantly slower as it involves reading data from source and writing to destination - **Resource Intensive**: Consumes compute resources and generates transaction logs **Option B: Switch the first partition from dbo.Sales to stg.Sales** ❌ - **Issue**: This moves data in the wrong direction - **Result**: Would empty the first partition in dbo.Sales rather than populate it with staging data - **Contrary to Requirement**: Does not achieve the goal of overwriting dbo.Sales with staging data **Option D: Update dbo.Sales from stg.Sales** ❌ - **Issue**: Update operations are resource-intensive and slow - **Performance Impact**: Requires row-by-row processing, locking, and extensive logging - **Not Suitable**: Completely contradicts the requirement to minimize load times ### Why Partition Switching is Optimal 1. **Minimal Load Time**: The operation completes in milliseconds as it only updates metadata 2. **Zero Data Movement**: No physical data transfer occurs 3. **Transactional Safety**: The switch is atomic and maintains data consistency 4. **Best Practice**: Microsoft recommends partition switching for large-scale data loading scenarios in dedicated SQL pools ### Prerequisites for Successful Partition Switching - Identical table schemas between source and target - Matching partition definitions and boundaries - Proper indexing alignment - Sufficient permissions for ALTER TABLE operations This approach aligns with Azure Synapse Analytics best practices for high-performance data loading in partitioned tables.

Author: LeetQuiz Editorial Team