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 DP-900 Exam - Topic 4 Question 98 Discussion

Actual exam question for Microsoft's DP-900 exam
Question #: 98
Topic #: 4
[All DP-900 Questions]

At which two levels can you set the throughput for an Azure Cosmos DB account? Each correct answer presents a complete solution.

NOTE: Each correct selection is worth one point.

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

0/2000 characters
Richelle
4 months ago
I thought it was just database and partition, but I guess not!
upvoted 0 times
...
Paul
4 months ago
Yup, container and database are the right answers!
upvoted 0 times
...
Raymon
4 months ago
Wait, can you really set it at the item level? That seems off.
upvoted 0 times
...
Judy
4 months ago
Totally agree, it's container and database!
upvoted 0 times
...
Coletta
5 months ago
You can set throughput at the container and database levels.
upvoted 0 times
...
Micheal
5 months ago
I’m a bit confused; I thought you could set it at the item level too, but that doesn’t seem right now. I’ll go with container and database.
upvoted 0 times
...
Dick
5 months ago
I feel like I read something about partitioning, but I don't think you can set throughput there. It's probably just container and database.
upvoted 0 times
...
Anika
5 months ago
I remember practicing a question like this, and I think it's definitely container and database. But I could be mixing it up with another topic.
upvoted 0 times
...
Della
5 months ago
I think the throughput can be set at the container level, but I'm not sure about the second one. Maybe the database level?
upvoted 0 times
...
Yan
5 months ago
Based on my understanding of Cosmos DB, I believe the two levels where you can set throughput are container and database. That seems like the most logical answer.
upvoted 0 times
...
Lonna
5 months ago
I'm a bit confused by this question. I know Cosmos DB has different levels, but I'm not sure if it's container and item, or container and database. I'll have to think about this one.
upvoted 0 times
...
Robt
5 months ago
Okay, let me think this through. I know Cosmos DB has containers and databases, so those are probably the two levels. I'll go with container and database.
upvoted 0 times
...
Lyndia
5 months ago
Hmm, I'm not too sure about this one. I know Cosmos DB has different levels, but I can't remember the specifics off the top of my head.
upvoted 0 times
...
Carri
5 months ago
This seems like a straightforward question about Azure Cosmos DB. I'm pretty confident I can get this one right.
upvoted 0 times
...
Glendora
10 months ago
Ah, the joys of Azure Cosmos DB. Setting throughput is like navigating a cosmic minefield, but I'm feeling lucky. C) database and D) partition, baby!
upvoted 0 times
...
Marvel
11 months ago
Oof, multiple levels for throughput? Sounds like a cosmic DB-sized headache to me. I'm just going to go with C) database and hope for the best. Fingers crossed!
upvoted 0 times
Aleisha
9 months ago
Let's hope for the best and go with C) database and D) partition for setting throughput.
upvoted 0 times
...
Glendora
9 months ago
I'm not sure about the other level, maybe D) partition could be the second option?
upvoted 0 times
...
Lavera
10 months ago
I think you're right, C) database is one of the levels for setting throughput.
upvoted 0 times
...
...
Dorathy
11 months ago
This one's a no-brainer! B) item and D) partition, hands down. Cosmos DB is all about scaling to the max, and these options let you do just that. *chef's kiss*
upvoted 0 times
Gretchen
9 months ago
Agreed, B) item and D) partition are the key levels for managing throughput in Azure Cosmos DB.
upvoted 0 times
...
Ernest
10 months ago
Definitely, those options give you the flexibility to scale your Cosmos DB account efficiently.
upvoted 0 times
...
Louisa
10 months ago
I think you're right, B) item and D) partition are the way to go for setting throughput.
upvoted 0 times
...
...
Carlee
11 months ago
Hmm, let's see. I'm going with A) container and C) database. Gotta keep that data flowing, even if it means setting the throughput at multiple levels. Classic Cosmos DB, am I right?
upvoted 0 times
Mollie
9 months ago
User2: Cosmos DB is all about flexibility and scalability, setting throughput at different levels is key.
upvoted 0 times
...
Dan
9 months ago
User1: Definitely, setting the throughput at multiple levels ensures smooth data flow in Azure Cosmos DB.
upvoted 0 times
...
Izetta
10 months ago
User2: Agreed, it's important to manage the throughput at both container and database levels for optimal performance.
upvoted 0 times
...
Larae
11 months ago
User1: I think you're right, A) container and C) database are the correct levels to set the throughput.
upvoted 0 times
...
...
Aron
11 months ago
Ah, the power of Azure Cosmos DB's throughput settings! I'd say C) database and D) partition are the correct answers here. Gotta love that fine-tuned control over performance, right?
upvoted 0 times
...
Thomasena
11 months ago
Actually, it's at the container and database levels. The throughput can be adjusted for each container and database in Azure Cosmos DB.
upvoted 0 times
...
Joesph
11 months ago
I believe it's at the container and partition levels.
upvoted 0 times
...
Thomasena
11 months ago
I think you can set the throughput at the container and database levels.
upvoted 0 times
...

Save Cancel