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 DP-900 Exam - Topic 1 Question 117 Discussion

Your company is designing a database that will contain session data for a website. The data will includenotifications, personalization attributes, and products that are added to a shopping cart.Which type of data store will provide the lowest latency to retrieve the data?
C) columnar
A) key/value
B) graph
D) document

Microsoft DP-900 Exam - Topic 1 Question 117 Discussion

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

Your company is designing a database that will contain session data for a website. The data will include

notifications, personalization attributes, and products that are added to a shopping cart.

Which type of data store will provide the lowest latency to retrieve the data?

Show Suggested Answer Hide Answer
Suggested Answer: C

https://docs.microsoft.com/en-us/azure/architecture/data-guide/technology-choices/analytical-data-stores

by Francine at Jan 25, 2026, 04:28 PM

Limited Time Offer

25%

Off

Get Premium DP-900 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Erasmo
5 days ago
Plus, they scale well with user growth.
upvoted 0 times
...
Norah
10 days ago
Agreed! They handle session data efficiently.
upvoted 0 times
...
Kristel
15 days ago
Definitely! Document stores like MongoDB are great for this.
upvoted 0 times
...
Kerrie
20 days ago
I think a NoSQL database would be best. Low latency is key.
upvoted 0 times
...
Muriel
26 days ago
Totally agree, NoSQL is the way to go for session data!
upvoted 0 times
...
Verona
2 months ago
Wait, are we sure NoSQL is always faster?
upvoted 0 times
...
Sherly
3 months ago
Definitely going with a key-value store for this.
upvoted 0 times
...
Jolanda
3 months ago
I think SQL can be fast too, depends on the setup!
upvoted 0 times
...
Yasuko
3 months ago
NoSQL databases are usually the best for low latency.
upvoted 0 times
...
Glenna
3 months ago
Redis, the name just sounds fast, you know?
upvoted 0 times
...
Elbert
3 months ago
Redis is the way to go, it's lightning fast!
upvoted 0 times
...
Maryann
3 months ago
Definitely Redis, it's designed for fast in-memory data access.
upvoted 0 times
...
Jeffrey
4 months ago
Memcached could also work well for caching session data.
upvoted 0 times
...
Coral
4 months ago
I'd go with a NoSQL database like MongoDB for this use case.
upvoted 0 times
...
Linwood
4 months ago
Redis would be the best choice for low-latency data retrieval.
upvoted 0 times
...
Tish
4 months ago
I feel like we discussed how caching can improve performance, but I’m uncertain if that applies directly to this scenario.
upvoted 0 times
...
Elenor
4 months ago
If I recall correctly, using a key-value store would help with quick access, but I can't remember if it’s the best choice for session data specifically.
upvoted 0 times
...
Cory
5 months ago
I remember practicing a question about data retrieval speeds, and I think NoSQL databases could also be a good option, but they might not be the fastest.
upvoted 0 times
...
Osvaldo
5 months ago
I think we might need to consider using an in-memory data store like Redis for low latency, but I'm not entirely sure.
upvoted 0 times
...
Mitsue
5 months ago
Ooh, good point about the shopping cart data. I was thinking more about the notifications and personalization, but we'll need to optimize for all the different data types. Lots to consider here!
upvoted 0 times
...
Daniel
6 months ago
I'd probably lean towards a columnar database like Amazon Redshift or Google BigQuery. They're designed for fast analytical queries, which could be useful for the shopping cart data.
upvoted 0 times
...
Latosha
6 months ago
Definitely going to need to do some research on the different data store options and their performance characteristics. Latency is key, but we'll also need to consider scalability and consistency requirements.
upvoted 0 times
...
Carline
6 months ago
Hmm, I'm not sure. I'd need to think more about the access patterns and volume of data. A NoSQL database like MongoDB or Cassandra might also work well for this use case.
upvoted 0 times
...
Shanda
6 months ago
I think I'd start by considering the different types of data we need to store and how they might be accessed. Notifications and personalization data are likely accessed frequently, so a low-latency store like Redis or Memcached could be a good option.
upvoted 0 times
...

Save Cancel