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 AZ-204 Topic 1 Question 99 Discussion

Actual exam question for Microsoft's AZ-204 exam
Question #: 99
Topic #: 1
[All AZ-204 Questions]

You are updating an application that stores data on Azure and uses Azure Cosmos DB for storage. The application stores data in multiple documents associated with a single username.

The application requires the ability to update multiple documents for a username in a single ACID operation.

You need to configure Azure Cosmos DB.

Which two actions should you perform? Each correct answer presents part of the solution.

NOTE: Each correct selection is worth one point.

Show Suggested Answer Hide Answer
Suggested Answer: B, D

Contribute your Thoughts:

Albina
4 months ago
Whoa, looks like we've got a real brain-bender here! But I'm feeling confident with C and D. Sharded collections and unsharded collections – the dynamic duo of Azure Cosmos DB!
upvoted 0 times
Alonzo
3 months ago
Definitely, having both sharded and unsharded collections will optimize our data storage.
upvoted 0 times
...
Margot
3 months ago
And don't forget about D! Unsharded collections are key for certain operations.
upvoted 0 times
...
Dong
3 months ago
I agree, C is important for storing documents efficiently.
upvoted 0 times
...
Loreen
3 months ago
I think C is the way to go. Sharding on username seems like a solid choice.
upvoted 0 times
...
...
Kandis
4 months ago
I believe we should also create a collection sharded on username to store documents for better organization.
upvoted 0 times
...
Ryann
4 months ago
I agree with William, using MongoDB API would be the right choice for updating multiple documents in a single ACID operation.
upvoted 0 times
...
Kerrie
4 months ago
Hold up, did someone say 'ACID'? I thought we were just here to have a good time, not learn about database transactions. C and D it is!
upvoted 0 times
Eve
3 months ago
Great, let's configure Azure Cosmos DB accordingly.
upvoted 0 times
...
Cyndy
3 months ago
Perfect, those two actions should help us update multiple documents for a username in a single ACID operation.
upvoted 0 times
...
Sarah
3 months ago
Yeah, that sounds good. And also D) Create an unsharded collection to store documents.
upvoted 0 times
...
Michal
3 months ago
I think we should go with C) Create a collection sharded on username to store documents.
upvoted 0 times
...
...
Alison
5 months ago
C and D, no doubt. Sharded collections are the future, and unsharded collections are the past. Embrace the present, my friends!
upvoted 0 times
Yvonne
4 months ago
Sharded collections are definitely the way to go for scalability and performance.
upvoted 0 times
...
Hollis
4 months ago
D) Create an unsharded collection to store documents.
upvoted 0 times
...
Luther
4 months ago
C) Create a collection sharded on username to store documents.
upvoted 0 times
...
...
Rupert
5 months ago
B and D, easy peasy! MongoDB API all the way, baby. Who needs ACID when you've got that sweet, sweet schemaless goodness?
upvoted 0 times
...
Sang
5 months ago
Hmm, I think C and D are the way to go. Gotta love that sharded collection to handle those multi-doc updates!
upvoted 0 times
Micah
4 months ago
Sharded collection is definitely the way to go for updating multiple documents in a single ACID operation.
upvoted 0 times
...
Carma
4 months ago
I agree, C and D are the correct actions to configure Azure Cosmos DB.
upvoted 0 times
...
...
William
5 months ago
I think we should configure Azure Cosmos DB to use the Azure Cosmos DB for MongoDB API.
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