HOTSPOT - You need to build a solution to collect the telemetry data for Race Central. What should you use? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point. Hot Area:
Suggested Answer:
API: Table - Azure Cosmos DB provides native support for wire protocol-compatible APIs for popular databases. These include MongoDB, Apache Cassandra, Gremlin, and Azure Table storage. Scenario: The telemetry data must migrate toward a solution that is native to Azure.
Consistency level: Strong - Use the strongest consistency Strong to minimize convergence time. Scenario: The data must be written to the Azure datacenter closest to each race and must converge in the least amount of time. Reference: https://docs.microsoft.com/en-us/azure/cosmos-db/consistency-levels
MongoDB: telemetry data is sent to MongoDB database
Eventual: The data should be written to nearest data center and latency should be minimize so answer in eventual.
I have check on other website and this are the correct answer for this..
I think "Mongo DB" and "strong".
MongoDB since the application already uses it.
Strong, because the cars should be monitored _in real time_. Lower consistencies increase waiting periods, and IMHO the real-time business requirement has priority over any technical requirement about RU's.
The second box should be "session". Please check the following link. You can't enable multi region writes with strong consistency.
https://docs.microsoft.com/en-us/azure/cosmos-db/consistency-levels#strong-consistency-and-multiple-write-regions
Yes you can enable multiple write regions to any consistency level. However, the differences are in the impact in case of failover - recover time and recover point.
For strong consistency in multiple write region, in case of a failover, you have a recovery time maximum of 240 minutos and the period of updates that you might afford to lose goes up to 1 week (RPO)...
So the correct answer is still the Strong.
hi,
no. telemetry data happens at real time and it represents several events sent at the same time to be processed so you must have a low level consistency here so that the throughput can be higher.
eventual
regards
Strong consistency level DOES NOT support multi-write enable. I just tried it in my Cosmos DB Account. You would get the following error: Update Default Consistency
Accounts configured with default consistency level as 'Strong' cannot be enabled for multiple write locations(i.e. EnableMultipleWriteLocations=true). Consider relaxing default consistency level of the account to enable multiple write locations.
ActivityId: ade4c368-bf45-43c0-ae45-095f71c0e051, Microsoft.Azure.Documents.Common/2.11.0
Requirements says "The data must be written to the Azure datacentre closest to each race and must converge in the least amount of time." So answer is Session as Eventual takes long time to converge and Strong will consume more RUs.
Not sure about the 2nd box.
Strong consistency is taking least amount of time to converge, however it take double RU/s than Session. And one of the requirement is "minimize the RU/s cost".
Session is guaranteed to honor the consistent-prefix, monotonic reads, monotonic writes, read-your-writes, and write-follows-reads guarantees. And out-side of session (for a different region, single master account) would be Consistent Prefix, which is also guarantees that read never see out-of-order writes.
You have always other ways to minimize RU/s cost like elastic pools, azure query performance insights, automatic tuning, etc. But not the consistency of it in the least amount of time for other regions. Having said that, the correct option should be Strong.
The data should be written to nearest Azure Location. This implies the enable of multi-writes which disables the Strong consistency. Therefore, bounded staleness consistency is the highest (in terms of fast converge) which can be applied in this case.
And this API is native toAzure too.
"Azure Cosmos DB provides native support for wire protocol-compatible APIs for popular databases. These include MongoDB, Apache Cassandra, Gremlin, and Azure Table storage."
Yes same mentioned mutiple times here:
https://docs.microsoft.com/en-us/azure/cosmos-db/mongodb-introduction
upvoted 1 times
...
...
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.
zulajariwala
Highly Voted 5 years agoThiruthuvaRajan
3 years, 12 months agoSTH
Highly Voted 5 years, 6 months agoz8zhong
5 years, 3 months agoHuepig
5 years, 2 months agoArd
4 years, 11 months agoNeelesh
4 years, 11 months agoCandiy
4 years, 6 months agodeepz8
4 years, 2 months agodev2dev
Most Recent 4 years, 4 months agomohowzeh
4 years, 5 months agosyu31svc
4 years, 6 months agoalfespa17
4 years, 7 months agosomeoneNoWhere
4 years, 6 months agosomeoneNoWhere
4 years, 6 months agodumpsm42
4 years, 5 months agojeanpaulh
4 years, 3 months agohart232
4 years, 8 months agosandGrain
4 years, 8 months agoavix
4 years, 10 months agoArd
4 years, 11 months agoLuke97
5 years agohart232
4 years, 8 months agosomeoneNoWhere
4 years, 6 months agosomeoneNoWhere
4 years, 6 months ago[Removed]
5 years, 1 month agoepgd
5 years, 4 months agoOnlyPraveen
4 years, 7 months ago