Which two metrics should you use to identify the appropriate RU/s for the telemetry data? Each correct answer presents part of the solution. NOTE: Each correct selection is worth one point.
A.
Number of requests
B.
Number of requests exceeded capacity
C.
End to end observed read latency at the 99 th percentile
Suggested Answer:AE🗳️
Scenario: The telemetry data must be monitored for performance issues. You must adjust the Cosmos DB Request Units per second (RU/s) to maintain a performance SLA while minimizing the cost of the RU/s. With Azure Cosmos DB, you pay for the throughput you provision and the storage you consume on an hourly basis. While you estimate the number of RUs per second to provision, consider the following factors: Item size: As the size of an item increases, the number of RUs consumed to read or write the item also increases.
I think AE is correct. We are estimating RU/s. By calculating storage data divided by the number of requests, you know how much is average data size per request. Since 1RU is about 1KB item, you can estimate the average RU/s required.
I think DE is the correct one.
https://docs.microsoft.com/en-us/azure/cosmos-db/request-units?fbclid=IwAR2etKSJ0ZcHjnzbfJ6gdlu1_UHN8Sx4VfHn8MNdz4Qnxs0-KzJV4APyU24#request-unit-considerations
E for sure, but I'm not sure of the D.
The option given is "session consistency" and actually the concept is called "data consistency" and "session" is just one of the data consistency levels.
As in link stated:
Data consistency: The strong and bounded staleness consistency levels consume approximately two times more RUs while performing read operations when compared to that of other relaxed consistency levels.
D is out of the question because Session consistency is just the configuration you set. You observer other things and may want to chaneg consitency level
Factors that affect the cost of query operations include:
The number of query results
The number of predicates
The nature of the predicates
The number of user-defined functions
The size of the source data
The size of the result set
Projections
Look at info for basic capacity planner in this link: https://docs.microsoft.com/en-us/azure/cosmos-db/estimate-ru-with-capacity-planner. Throughput is the same as RU/s. The inputs include storage and # of requests.
Not sure on the answer to this one but I would think F was one of them. You provision throughput for a container which is a measure of crud per second so looking at the average throughput makes sense to me. Can't see what benefit E gives you here - RUs are about activity taking place in a given second.
This section is not available anymore. Please use the main Exam Page.DP-200 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
extraego
Highly Voted 4 years, 11 months agoZanzara
Highly Voted 5 years, 1 month agoTreadmill
4 years, 11 months agodev2dev
4 years, 4 months agodumpsm42
Most Recent 4 years, 6 months agohart232
4 years, 9 months agorjdask
4 years, 11 months agoLuke97
5 years, 1 month agopawhit
5 years, 1 month agoHuepig
5 years, 3 months ago