Exam DP-600 topic 1 question 80 discussion

The “CREATE TABLE … AS CLONE OF” statement is the most efficient way to create a copy of a table in the same Fabric tenant. This statement creates a new table in the specified schema that is an exact clone of the source table, including the table structure, data, and indexes. This approach minimizes the amount of data copied, as it simply creates a reference to the underlying data rather than performing a full table scan and data copy. Options A and B, which use INSERT INTO or SELECT INTO, would require scanning the entire source table and copying the data row-by-row, which is less efficient than the CLONE method. Option D, CREATE TABLE … AS SELECT, would also work to create a copy of the table, but it would perform a full table scan and data copy, which is less efficient than the CLONE approach.

https://learn.microsoft.com/en-us/fabric/data-warehouse/clone-table Microsoft Fabric offers the capability to create near-instantaneous zero-copy clones with minimal storage costs.

The schemas are existing so the correct answer is CREATE TABLE schema2.city AS SELECT * FROM schema1.city;

should be C, since copying of data should be minimized

CLONE AS Creates a new table as a zero-copy clone of another table in Warehouse in Microsoft Fabric. Only the metadata of the table is copied. The underlying data of the table, stored as parquet files, is not copied. A zero-copy clone creates a replica of the table by copying the metadata, while still referencing the same data files in OneLake. The metadata is copied while the underlying data of the table stored as parquet files is not copied. The creation of a clone is similar to creating a table within a Warehouse in Microsoft Fabric.

go with D. C is a clone of table's metadata not copy data activity

AS CLONE basically minimizes the copying of data. That's the biggest requirement.

C. CREATE TABLE schema2.city AS CLONE OF schema1.city; This statement creates a new table named city in schema2 that has the same structure as the city table in schema1 without copying any data. It essentially creates a metadata reference to the original table, which minimizes the data copying.

Option A: INSERT INTO schema2.city SELECT * FROM schema1.city; This option assumes that schema2.city already exists. It will insert data into schema2.city but will not create the table. Option B: SELECT * INTO schema2.city FROM schema1.city; This option copies data from schema1.city to schema2.city but is typically used in SQL Server to create a new table and copy data. However, it doesn't handle schema changes well and might not be the best for large datasets. Option C: CREATE TABLE schema2.city AS CLONE OF schema1.city; This is not a valid T-SQL syntax for creating tables. Option D: CREATE TABLE schema2.city AS SELECT * FROM schema1.city; This statement creates a new table schema2.city and copies all data from schema1.city into it (CTAS). This option is efficient for creating a new table with the same schema and data as the original table.

D is the correct answer. Only the metadata of the table is copied. The underlying data of the table, stored as parquet files, is not copied. https://learn.microsoft.com/en-us/sql/t-sql/statements/create-table-as-clone-of-transact-sql?view=fabric

IMHO, C is good. Because: Within a warehouse, a clone of a table can be created near-instantaneously using simple T-SQL. A clone of a table can be created within or across schemas in a warehouse. Here: https://learn.microsoft.com/en-us/fabric/data-warehouse/clone-table#creation-of-a-table-clone

I would go with C, is the fastest way to replicate the schema.

C is correct - Cloning reduces data movement

C is correct

d is the write answer