Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You have an Azure Synapse Analytics dedicated SQL pool that contains a table named Table1. You have files that are ingested and loaded into an Azure Data Lake Storage Gen2 container named container1. You plan to insert data from the files into Table1 and transform the data. Each row of data in the files will produce one row in the serving layer of Table1. You need to ensure that when the source data files are loaded to container1, the DateTime is stored as an additional column in Table1. Solution: You use an Azure Synapse Analytics serverless SQL pool to create an external table that has an additional DateTime column. Does this meet the goal?
Man, Microsoft loves to word these Synapse questions so tricky. A tbh, because creating an external table with a DateTime column feels like it solves it. You can define the schema and just query with the extra field, right? Unless they're looking for a physical insert into Table1 (dedicated pool) not just metadata. Not 100% on this one, could easily see B being right too.
Seen a similar drag & drop on a practice test. From what I recall, you'd usually (1) create the resource pool, (2) create a workload group assigning the pool, then (3) configure the classifier function for App1. Order can vary but the core is pool first, then group, then classification. Official docs and lab demos cover this routine pretty well if you want to check deeper. Not 100% sure since more than one sequence is valid here.