Q: 10
An application needs a key-value store with eventual consistency that can span
multiple regions and is primarily used to cache or store user preferences that
change infrequently. Which database should be selected for maximum availability
and global distribution with eventual consistency?
Options
Discussion
D every time for this. Firestore Native handles multi-region and eventual consistency well, fits key-value user prefs perfectly.
D . Firestore in Native Mode gives you global scaling and eventual consistency, which is exactly what you want for infrequent user preference changes across regions. Cloud SQL and Bigtable aren't really designed for this pattern. Open to other takes if I missed something.
D tbh, fits key-value and eventual consistency across regions best for this scenario.
I don’t think it’s B. D makes more sense for eventual consistency with multi-region and key-value, but not 100 percent certain.
Key detail is that Firestore Native Mode (D) supports multi-region and true eventual consistency, while Bigtable and Spanner lean toward other use cases. Pretty sure D unless you need strong consistency instead.
Probably D. Firestore Native Mode ticks all the boxes: global reach, eventual consistency, and fits a key-value user preferences use case. Official guides and practice exams stress this distinction a lot, so I think D is right unless there's something subtle in the scenario I missed. Anyone disagree?
D fits best here since Firestore Native Mode handles global distribution with eventual consistency, and it's ideal for storing key-value user preferences. Spanner is usually overkill unless strong consistency is required. Think D is right, but always happy to hear counterpoints.
D tbh, not C. Spanner trips folks up but it's really for strong consistency, while Firestore's eventual consistency wins here.
D imo. Firestore in Native Mode is designed for global scale and offers eventual consistency, which fits the question perfectly for key-value storage with max availability. Spanner (C) is stronger on global strong consistency but is more relational and probably overkill for just caching user prefs. Pretty sure D nails all the requirements here, open to arguments if someone sees Bigtable working better.
Maybe C, I remember a similar question on a practice exam picking Spanner for global availability and consistency.
Be respectful. No spam.
