Exam DP-201 All Questions

View all questions & answers for the DP-201 exam

Exam DP-201 topic 1 question 23 discussion

Actual exam question from Microsoft's DP-201

Question #: 23
Topic #: 1

You have a MongoDB database that you plan to migrate to an Azure Cosmos DB account that uses the MongoDB API.
During testing, you discover that the migration takes longer than expected.
You need to recommend a solution that will reduce the amount of time it takes to migrate the data.
What are two possible recommendations to achieve this goal? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.

A. Increase the Request Units (RUs).
B. Turn off indexing.
C. Add a write region.
D. Create unique indexes.
E. Create compound indexes.

Show Suggested Answer

Suggested Answer: AB 🗳️
A: Increase the throughput during the migration by increasing the Request Units (RUs).
For customers that are migrating many collections within a database, it is strongly recommend to configure database-level throughput. You must make this choice when you create the database. The minimum database-level throughput capacity is 400 RU/sec. Each collection sharing database-level throughput requires at least 100 RU/sec.
B: By default, Azure Cosmos DB indexes all your data fields upon ingestion. You can modify the indexing policy in Azure Cosmos DB at any time. In fact, it is often recommended to turn off indexing when migrating data, and then turn it back on when the data is already in Cosmos DB.
Reference:
https://docs.microsoft.com/bs-latn-ba/Azure/cosmos-db/mongodb-pre-migration

by Leonido at April 25, 2020, 4:25 p.m.

Comments

Submit Cancel

alexvno

Highly Voted 4 years, 10 months ago

Correct

upvoted 20 times

...

chaoxes

Highly Voted 4 years, 5 months ago

A. Increase the request units (RUs) B. Turn off indexing

upvoted 12 times

...

cadio30

Most Recent 4 years ago

Propose solution is correct, by default azure cosmos db create an index though the feature could be toggle to prevent it from happening. Reference: https://docs.microsoft.com/bs-latn-ba/Azure/cosmos-db/mongodb-post-migration

upvoted 1 times

...

sjain91

4 years, 1 month ago

turn off indexing and increase the request units - Answer A is correct

upvoted 1 times

...

MSFTLearn

4 years, 7 months ago

Indexing makes write operation slower. "By default, indexing policy is set to automatic. It's achieved by setting the automatic property in the indexing policy to true. Setting this property to true allows Azure CosmosDB to automatically index documents as they are written." https://docs.microsoft.com/en-us/azure/cosmos-db/index-policy

upvoted 4 times

sunil_kalra

4 years, 5 months ago

yes, we can turn that indexing off and turn it back on after data load is complete

upvoted 2 times

...

M0e

4 years, 7 months ago

The explanation for B. is incorrect. MongoDB API only creates an index for _id field. From the documentation: "The Azure Cosmos DB's API for MongoDB server version 3.6 automatically indexes the _id field only. This field can't be dropped. It automatically enforces the uniqueness of the _id field per shard key. To index additional fields, you apply the MongoDB index-management commands. This default indexing policy differs from the Azure Cosmos DB SQL API, which indexes all fields by default." So, I think B can not the correct answer.

upvoted 5 times

...

djangodev

4 years, 7 months ago

I think its A & D. The link that is provided in explanation, does not mention about the turning off indexes, however it mentions Creating Unix Indexes. Any suggestion?

upvoted 3 times

syu31svc

4 years, 6 months ago

I agree on this one

upvoted 1 times

...

Leonido

5 years, 1 month ago

Just a thought - If I migrate from Amazon and I have many locations there, it will make sense to have multiple write sites and run migration in parallel from several different locations. That will server as a migration accelerator.

upvoted 2 times

...