AI-200 practice question 3 of 10
Your team is building an AI model serving application using Azure Cosmos DB for NoSQL as the vector database. The application stores embeddings for…
Full set: 67 questionsIn Azure Cosmos DB for NoSQL, vector embeddings are large arrays. If not explicitly excluded from the standard indexing policy, Cosmos DB attempts to index every element, leading to excessive Request Unit (RU) consumption and storage costs. Vector indexes are defined separately, so the vector field must be excluded from standard indexing. Additionally, Strong consistency requires reading from a quorum, which doubles the RU cost for read operations compared to Eventual consistency. Switching to Eventual consistency reduces RU consumption and improves read latency.
A. Incorrect because Cosmos DB does not support composite indexes that combine scalar fields with vector embedding properties.
C. Incorrect because replicating data via change feed does not improve the query performance or reduce RU consumption of the primary database.
- Microsoft Learn: "Vector search in Azure Cosmos DB for NoSQL"
Section: Vector indexing policies. (https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/vector-search)
- Microsoft Learn: "Consistency levels in Azure Cosmos DB"
Section: Consistency levels and throughput. (https://learn.microsoft.com/en-us/azure/cosmos-db/consistency-levels)
Keep practicing
Take the free AI-200 practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other AI-200 practice questions
- Question 1You are developing an AI application that processes customer embeddings stored in Azure C…
- Question 2You are developing an Al-powered API that retrieves connection strings and API keys from …
- Question 4You optimize an Al inference API that uses Redis caching. You must reduce the risk of ser…
