Note: This question is part of a series of questions that present the same scenario. For your convenience, the
scenario is repeated in each question. Each question presents a different goal and answer choices, but the text
of the scenario is exactly the same in each question in this series.
Start of repeated scenario
You are migrating an existing on-premises data warehouse named LocalDW to Microsoft Azure. You will use
an Azure SQL data warehouse named AzureDW for data storage and an Azure Data Factory named AzureDF
for extract, transformation, and load (ETL) functions.
For each table in LocalDW, you create a table in AzureDW.
On the on-premises network, you have a Data Management Gateway.
Some source data is stored in Azure Blob storage. Some source data is stored on an on-premises Microsoft
SQL Server instance. The instance has a table named Table1.
After data is processed by using AzureDF, the data must be archived and accessible forever. The archived data
must meet a Service Level Agreement (SLA) for availability of 99 percent. If an Azure region fails, the archived
data must be available for reading always. The storage solution for the archived data must minimize costs.
End of repeated scenario.
You need to define the schema of Table1 in AzureDF.
What should you create?
A.
a gateway
B.
a linked service
C.
a dataset
D.
a pipeline