Importing Data to Azure Subscription | Destination Options
Question
You have an Azure subscription named Subscription1.
You have 5 TB of data that you need to transfer to Subscription1.
You plan to use an Azure Import/Export job.
What can you use as the destination of the imported data?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.C
Azure Import/Export service is used to securely import large amounts of data to Azure Blob storage and Azure Files by shipping disk drives to an Azure datacenter.
https://docs.microsoft.com/en-us/azure/storage/common/storage-import-export-serviceWhen you need to transfer large amounts of data to an Azure subscription, you can use Azure Import/Export service. This service allows you to transfer large amounts of data to and from Azure by shipping hard drives to an Azure data center. Once the hard drives arrive, the data is uploaded to your Azure storage account.
In this case, you have 5 TB of data that you need to transfer to your Azure subscription named Subscription1 using Azure Import/Export job. You need to choose a destination for your imported data. Among the options provided, you can use Azure Blob storage, Azure Files, or Azure Data Box.
The correct answer among the options provided is C. Azure File Storage. Azure File Storage is a fully managed file share service in Azure, that allows you to share files across applications and VMs. It is a good choice for importing file-based data.
Azure Cosmos DB is a globally distributed multi-model database service. It is not a good choice for importing large amounts of data using Azure Import/Export job as it is not a file-based storage solution.
Azure SQL Database is a fully managed relational database service in Azure. It is not a good choice for importing large amounts of data using Azure Import/Export job as it is not a file-based storage solution.
Azure Data Lake Store is a hyperscale repository for big data analytics workloads in Azure. While it is a good choice for storing large amounts of data, it is not an appropriate choice for importing file-based data using Azure Import/Export job.
