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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Microsoft AZ-204 Exam - Topic 2 Question 97 Discussion

Actual exam question for Microsoft's AZ-204 exam
Question #: 97
Topic #: 2
[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

by Merilyn at Jul 01, 2024, 01:51 PM

Limited Time Offer

25%

Off

Get Premium AZ-204 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Bettina
5 months ago
Wait, can you really do ACID with Cosmos DB? Sounds tricky!
upvoted 0 times
...
Annice
5 months ago
I thought Gremlin API was the best choice here?
upvoted 0 times
...
Jennifer
5 months ago
Sharding on username? Not sure that’s right for ACID.
upvoted 0 times
...
Tu
5 months ago
Totally agree, unsharded is the way to go!
upvoted 0 times
...
Loise
6 months ago
You need an unsharded collection for ACID transactions.
upvoted 0 times
...
Maybelle
6 months ago
I recall that unsharded collections can simplify things, but I wonder if they support ACID operations effectively for multiple documents.
upvoted 0 times
...
Carmen
6 months ago
I’m a bit confused about the APIs. I thought the MongoDB API could handle multiple document updates, but I’m not entirely sure.
upvoted 0 times
...
Ngoc
6 months ago
I think we practiced a similar question where we had to decide between sharded and unsharded collections. I feel like sharding on username might help with performance.
upvoted 0 times
...
Marjory
6 months ago
I remember we discussed the importance of ACID transactions in Cosmos DB, but I'm not sure which API to choose for this scenario.
upvoted 0 times
...
Bev
6 months ago
Alright, I've got a plan. I think creating a sharded collection on the username field is the way to go. That should allow me to update multiple documents for a single user in a single ACID operation.
upvoted 0 times
...
Jutta
6 months ago
I'm a bit confused on the different API options for Azure Cosmos DB. I'll need to make sure I understand the differences and how they might impact the solution.
upvoted 0 times
...
Yuki
6 months ago
Okay, let's see here. The key things I'm looking for are the ability to update multiple documents for a single username in a single operation. I think the sharding option might be the way to go, but I'll need to double-check the details.
upvoted 0 times
...
Lourdes
7 months ago
Hmm, this seems like a tricky one. I'll need to carefully read through the requirements and think about the best way to configure Azure Cosmos DB to support the ACID update operation.
upvoted 0 times
...
Louisa
7 months ago
The key is to identify the correct services for full sync and delta sync. I'll walk through each option methodically.
upvoted 0 times
...
Dustin
7 months ago
Okay, resetting the ports for the specific FC IDs seems like the most direct approach. I'll make sure to double-check the IDs mentioned in the question.
upvoted 0 times
...
Rosann
7 months ago
Looks like they're testing our understanding of unethical business practices. I'm pretty sure this is about bribery.
upvoted 0 times
...
Franklyn
7 months ago
I think if the deterioration rates are low, going for on-stream inspection could be the best option, but I'm not entirely sure if that's what we discussed in class.
upvoted 0 times
...
Rodrigo
2 years ago
Option A sounds like it's straight out of left field. I'm going with C and D as the correct answers to this one.
upvoted 0 times
Mary
2 years ago
I agree, and D for unsharded collection seems like the right move too.
upvoted 0 times
...
Ryan
2 years ago
I think C is a good choice, sharding on username makes sense.
upvoted 0 times
...
...
Janna
2 years ago
I think both options are valid, it depends on the specific requirements of the application.
upvoted 0 times
...
Huey
2 years ago
But wouldn't creating an unsharded collection to store documents be more efficient?
upvoted 0 times
...
Aleshia
2 years ago
Haha, A and B are completely off-base! This is clearly a Cosmos DB question, not a Gremlin or MongoDB one. C and D are the way to go.
upvoted 0 times
Xuan
2 years ago
Yeah, A and B are not the right options. C and D are the correct actions to take.
upvoted 0 times
...
Herschel
2 years ago
A and B are definitely not the right choices. C and D are the way to go.
upvoted 0 times
...
Filiberto
2 years ago
Definitely, C and D are the correct actions to configure Azure Cosmos DB.
upvoted 0 times
...
Catherin
2 years ago
I agree, A and B are not relevant here. C and D make more sense.
upvoted 0 times
...
...
James
2 years ago
I disagree, I believe we should create a collection sharded on username to store documents.
upvoted 0 times
...
Stephaine
2 years ago
I think B and D are the right answers. Using the Azure Cosmos DB for MongoDB API will give you the flexibility to perform atomic updates across multiple documents.
upvoted 0 times
Renea
2 years ago
D) Create an unsharded collection to store documents.
upvoted 0 times
...
Asuncion
2 years ago
B) Configure Azure Cosmos DB to use the Azure Cosmos DB for MongoDB API.
upvoted 0 times
...
...
Deandrea
2 years ago
The correct answers are C and D. Sharding the collection on the username will allow for the atomic updates across multiple documents associated with a single user.
upvoted 0 times
Vince
2 years ago
B) Configure Azure Cosmos DB to use the Azure Cosmos DB for MongoDB API.
upvoted 0 times
...
Valentin
2 years ago
A) Configure Azure Cosmos DB to use the Azure Cosmos DB for Apache Gremlin API.
upvoted 0 times
...
...
Huey
2 years ago
I think we should configure Azure Cosmos DB to use the Azure Cosmos DB for MongoDB API.
upvoted 0 times
...

Save Cancel