Cyber Monday 2024! 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:

Audry
5 months ago
Database Migration Assistant is more for schema and code migration, not data migration.
upvoted 0 times
...
Vivan
6 months ago
But what about Database Migration Assistant? Shouldn't we consider that too?
upvoted 0 times
...
Micaela
6 months ago
I agree with Azure Data Factory can handle data migration efficiently.
upvoted 0 times
...
Audry
6 months ago
I think we should use Azure Data Factory for the migration.
upvoted 0 times
...
Margurite
7 months ago
Database Migration Assistant is more for schema and code migration, not data migration.
upvoted 0 times
...
Luisa
7 months ago
But what about Database Migration Assistant? Shouldn't we consider that too?
upvoted 0 times
...
Geoffrey
7 months ago
I agree with Margurite, Azure Data Factory can handle data migration efficiently.
upvoted 0 times
...
Margurite
7 months ago
I think we should use Azure Data Factory for the migration.
upvoted 0 times
...
Jolene
8 months 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
8 months 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
8 months 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 months 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 months 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
8 months 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
8 months 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
Chandra
7 months ago
Azure Migrate is used for server migration, not data migration in this scenario.
upvoted 0 times
...
Lanie
7 months ago
C
upvoted 0 times
...
Winifred
7 months ago
Makes sense, thanks for clarifying.
upvoted 0 times
...
Leota
7 months ago
A
upvoted 0 times
...
Denise
7 months ago
Azure Data Factory is the tool that can help migrate data from the third-party application to Azure Cosmos DB.
upvoted 0 times
...
Paola
7 months ago
B
upvoted 0 times
...
Keena
7 months ago
Yes, the third-party application is the source of the data that needs to be migrated.
upvoted 0 times
...
Yvette
8 months ago
A
upvoted 0 times
...
...
Bong
8 months ago
Database migration, huh? I bet the answer involves some kind of Azure service. Let's see what the options are.
upvoted 0 times
Keneth
7 months ago
I'm not sure. Maybe Azure Migrate would be the best option.
upvoted 0 times
...
Tish
7 months ago
No, I believe Database Migration Assistant is the right choice here.
upvoted 0 times
...
Marshall
7 months ago
I think we should use Azure Data Factory.
upvoted 0 times
...
...
Kizzy
8 months ago
Hmm, this seems straightforward enough. I'm wondering if there's a catch somewhere.
upvoted 0 times
...
Jeniffer
8 months 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