A travel marketplace stores hotel listings whose attributes differ by property type and change often as partners add new fields. The catalog must be readable with low latency on several continents and stay available if one region fails. Which data type and store combination fits?
Show answer and explanation
Answer: B
Listings with varying attributes are semi-structured, and a multi-region document database stores them without a rigid schema while replicating data close to users on several continents. It also keeps serving requests when a region goes down. A single-region SQL server struggles with frequent schema changes and regional failure, object storage cannot run attribute queries, and a nightly warehouse is too stale for live listings.
Why the other options are wrong
- A. A single-region SQL server requires schema migrations each time partners add fields and offers no regional redundancy, so it misses both requirements.
- C. Object storage holds photos cheaply, but filenames are not a reliable query interface for attributes, and it does not replicate listing records for low-latency reads.
- D. Nightly warehouse loads leave listings stale for hours, and star-schema tables are built for analytics rather than serving live, frequently changing catalog reads.