Question 11
UnclassifiedAn app often reads a customer profile and the customer's active preferences together. What is a Cosmos DB modeling consideration?
Correct answer: D
Explanation
Cosmos DB is a NoSQL document database, so data is often modeled for the way the app reads it. If an app frequently reads a customer profile and active preferences together, keeping them in one document or closely related documents follows the rule to "model documents around query and transaction patterns" instead of automatically normalizing every entity.
Why each option is right or wrong
A. Store JSON as an image file.
B. Split every field into a separate container by default.
C. Use only relational joins for every read.
D. Model documents around query and transaction patterns rather than automatically normalizing every entity.
Cosmos DB is designed for denormalized document modeling, where related data is often embedded to match the application’s read and transaction paths. In this scenario, the app repeatedly fetches the profile and active preferences together, so a single-document or closely grouped design reduces cross-document lookups and aligns with Cosmos DB’s partitioned, request-unit-based access model rather than a relational normalization approach.