Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Microsoft Exam DP-420 Topic 10 Question 35 Discussion

Actual exam question for Microsoft's DP-420 exam
Question #: 35
Topic #: 10
[All DP-420 Questions]

You have a database named db1 in an Azure Cosmos DB f You have a third-party application that is exposed thro You need to migrate data from the application to a What should you use?

Show Suggested Answer Hide Answer
Suggested Answer: B

you can migrate data from various data sources to Azure Cosmos DB using different tools and methods.The choice of the migration tool depends on factors such as the data source, the Azure Cosmos DB API, the size of data, and the expected migration duration1. Some of the common migration tools are:

Azure Cosmos DB Data Migration tool: This is an open source tool that can import data to Azure Cosmos DB from sources such as JSON files, MongoDB, SQL Server, CSV files, and Azure Cosmos DB collections.This tool supports the SQL API and the Table API of Azure Cosmos DB2.

Azure Data Factory: This is a cloud-based data integration service that can copy data from various sources to Azure Cosmos DB using connectors.This tool supports the SQL API, MongoDB API, Cassandra API, Gremlin API, and Table API of Azure Cosmos DB3.

Azure Cosmos DB live data migrator: This is a command-line tool that can migrate data from one Azure Cosmos DB container to another container within the same or different account.This tool supports live migration with minimal downtime and works with any Azure Cosmos DB API4.

For your scenario, if you want to migrate data from a third-party application that is exposed through an OData endpoint to a container in Azure Cosmos DB for NoSQL, you should useAzure Data Factory.Azure Data Factory has an OData connector that can read data from an OData source and write it to an Azure Cosmos DB sink using the SQL API5. You can create a copy activity in Azure Data Factory that specifies the OData source and the Azure Cosmos DB sink, and run it on demand or on a schedule.


Contribute your Thoughts:

Jolene
6 days ago
Ah, but Azure Migrate is more focused on migrating VMs and servers, not necessarily application data. I think Azure Data Factory is the way to go here. It can handle all the data transformation and loading into Cosmos DB.
upvoted 0 times
...
Hui
6 days ago
Database Migration Assistant? That's a new one to me. I wonder if that's a specialized tool for Cosmos DB.
upvoted 0 times
...
Val
7 days ago
Hmm, I'm not so sure about Azure Data Factory. Doesn't that require a bit more setup and configuration? I was thinking Azure Migrate might be simpler, since it's designed for cloud migrations.
upvoted 0 times
...
Erin
8 days ago
Azure Migrate? That's usually for VM migrations, not database migrations. Interesting choice, let's see if that's a valid option here.
upvoted 0 times
...
Nydia
8 days ago
I think the key here is that we need to migrate data from an existing application to an Azure Cosmos DB. Based on that, I'd say Azure Data Factory is the best option. It's a great tool for ETL and data integration tasks like this.
upvoted 0 times
...
Stephania
9 days ago
I've used Azure Data Factory before for data migration, so that's my initial thought. But let's consider the other options too.
upvoted 0 times
...
Blair
9 days ago
This question is pretty straightforward, but I'm a bit confused about the wording. What do they mean by 'third-party application'? Is that the source of the data we need to migrate?
upvoted 0 times
...
Bong
10 days ago
Database migration, huh? I bet the answer involves some kind of Azure service. Let's see what the options are.
upvoted 0 times
...
Kizzy
12 days ago
Hmm, this seems straightforward enough. I'm wondering if there's a catch somewhere.
upvoted 0 times
...
Jeniffer
14 days ago
Ooh, a Cosmos DB question! That's right up my alley. Let's see what we've got here.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77