Suggested Answer:
Box 1: simple lookups - A key/value store associates each data value with a unique key. Most key/value stores only support simple query, insert, and delete operations. To modify a value (either partially or completely), an application must overwrite the existing data for the entire value. In most implementations, reading or writing a single value is an atomic operation. An application can store arbitrary data as a set of values. Any schema information must be provided by the application. The key/value store simply retrieves or stores the value by key. Reference: https://docs.microsoft.com/en-us/azure/architecture/guide/technology-choices/data-store-overview
according to the link in description: The Answer is: simple lookups.
Key/value stores are highly optimized for applications performing simple lookups, but are less suitable if you need to query data across different key/value stores. Key/value stores are also not optimized for querying by value.
the reference:
https://docs.microsoft.com/en-us/azure/architecture/guide/technology-choices/data-store-overview#keyvalue-stores
The answer given is correct. From the trainer handbook: A key-value store is the simplest (and often quickest) type of NoSQL database for inserting and querying data. Each data item in a key-value store has two elements, a key and a value. The key uniquely identifies the item, and the value holds the data for the item. The value is opaque to the database management system. Items are stored in key order.
a. Incorrect. Key/Value stores are generally schema-less and do not focus on enforcing constraints like relational databases do.
b. Correct. Key/Value stores are optimized for fast, straightforward lookups based on keys. They are ideal for retrieving values quickly without complex queries.
c. Incorrect. Key/Value stores are not designed for performing joins, as they do not have a relational structure. Joins are typically handled by relational databases.
d. Incorrect. While some Key/Value stores support transactions, they are not as robust as relational databases in handling complex transactions and typically focus on simple retrievals rather than transactional operations.
From the learning path "..The focus of a key-value store is to read and write data quickly. Search capabilities secondary. Key-value store excellent for data ingestion, when large volumes of data arrive as a continual stream and must be stored immediately..."
So why not transactional?
This section is not available anymore. Please use the main Exam Page.DP-900 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.
ati339
Highly Voted 8 months, 2 weeks agoJustMe84
Highly Voted 8 months, 2 weeks agoman5484
Most Recent 6 months, 3 weeks agothe_jigglypuff
7 months, 4 weeks agoRajeshAzure
8 months, 2 weeks agoAGTraining
1 year, 3 months agojames2033
1 year, 7 months agoHan__
1 year, 9 months agoakhil5432
1 year, 10 months agozanjeev
1 year, 10 months agochiiiweiii
2 years, 3 months agoEltooth
2 years, 11 months agoferoz777
2 years, 12 months agoEXODUS33
3 years agoXiltroX
3 years, 2 months agoVegasLC
3 years, 6 months agoAzureDP900
3 years, 8 months ago