There is a Dedicated SQL Pool in which the existing tables are using clustered columnstore index. You are planning for a partition switch to improve the performance following your partition strategy. You run the partition table function on the first two tables. But they were not successful. Which of the options tells about the possible reasons for this failure? (Multiple choice)
 

Answer options:

A.Partition boundaries should not be the same.
B.Partition boundaries should be the same.
C.Table definitions should match.
D.Table definitions shouldn’t match.
E.Dedicated SQL Pool support only partition splitting and merging using ALTER TABLE statement.

Correct Answer: B and C
Dedicated SQL pool supports partition switching, splitting, and merging. Each function is executed using the ALTER TABLE statement. 
But in the case of Data Partition Switching between two tables, the partitions must align to their respective boundaries and table functions should be matching. Otherwise, we will have errors in this operation, and partition metadata sync will be failed. The reason behind this is that check constraints are not available to enforce the range of values in a table. So, the source and target tables should have the same partition boundaries. Options A and D are incorrect: For partition switching to succeed, the boundaries should be the same, and table definitions should be met. So, they are incorrect and not a reason for the failure of the partition switching function.
Options B and C are correct: These will be possible reasons for the failure of the partition switching function.
Option E is incorrect: Dedicated SQL pool not only supports splitting and merging but also partition switching.
Reference: To know more, please refer to the docs below: 

https://docs.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-tables-partition#partition-switching