You need to improve throughput for concurrent application requests to PostgreSQL.What should you implement?
Answer(s): A
To improve throughput for highly concurrent application requests in this architecture, you should implement connection pooling.PostgreSQL follows a process-based architecture where each client connection spawns a separate backend process. This consumes significant memory and CPU overhead during high concurrency. Connection pooling(using tools like PgBouncer or Azure's built-in pooler) allows containerized microservices to reuse a fixed set of database connections. This drastically reduces connection overhead, prevents database exhaustion, and maximizes throughput for short, rapid API queries like vector similarity searches.
https://medium.com/@srajanpathak45/a-principal-engineers-guide-to-postgresql-and-modern-alternatives-e8920fd6269a
DRAG DROP (Drag and Drop is not supported)You need to configure the Redis integration for the Recommendation API.Which configurations should you use? To answer, move the appropriate configurations to the correct requirements. You may use each configuration once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.Note: Each correct selection is worth one point.Select and Place:
Scenario, Application: Azure Managed Redis is used as a caching layer.Box 1: Configure the Time to Live (TTL) on each cache key You must configure the Time to Live (TTL) on each cache key to meet this requirement. Azure Managed Redis (like standard Redis) does not support a global, database-wide default TTL configuration for newly created keys.Scenario: Technical requirements: Caching: Redis cache entries must expire automatically after 10 minutes. Box 2: Publish invalidation events to a Redis channelPublishing invalidation events to a Redis Pub/Sub channel is a highly effective, standard architecture to invalidate cache entries across microservices or application nodes. It establishes a reactive, event-driven backplane that ensures system data integrity without requiring tight coupling between your database updates and web servers.Scenario: Technical requirements: Implement a reactive mechanism to invalidate cache entries upon metadata updates.Box 3: Implement the cache-aside pattern with lazy loading To meet your search latency target for recurring product requests, you should implement the cache-aside pattern with lazy loading.Directly reduces latency: Lazy loading ensures that frequently requested product data is kept in memory (Redis), allowing subsequent recurring requests to bypass the slower database completely.Optimizes memory usage: Data is only loaded into the cache when actually requested, preventing your Azure Managed Redis instance from filling up with rarely accessed product data.
https://learn.microsoft.com/en-us/azure/architecture/databases/architecture/write-through-caching-azure-sql-managed-redis https://www.gigson.co/blog/what-is-redis-a-beginners-guide-to-in-memory-caching
HOTSPOT (Drag and Drop is not supported)You need to configure vector embedding updates according to the business and technical requirements.Which configurations should you use? To answer, select the appropriate options in the answer area.Note: Each correct selection is worth one point.Hot Area:
Business Requirements: Embeddings for new or updated Azure Cosmos DB for NoSQL-hosted documents must be automatically generated. Technical Requirements: Vector similarity search must use embeddings stored in Azure Cosmos DB for NoSQL.Box 1: Change feed processor The Change feed processor is the correct component to configure for identifying document changes that should trigger vectorization.This feature in Azure Cosmos DB provides a reliable, distributed, and scalable way to listen to a constant stream of changes (inserts and updates) within a container. It allows you to process these modifications in real-time, making it the perfect trigger for automated workflows like sending new text to an embedding model.Box 2: Lease Container The lease container is the component you configure to coordinate and horizontally scale out the change feed-driven vectorization processing across multiple workers or compute instances.The Lease Container acts as state storage, tracks checkpoints, and distributes partition keys across parallel compute workers (such as Azure Functions or custom change feed processors) to scale out throughput processing safely without duplicate work.Incorrect: RU Throughput: Dictates the maximum performance limit, but provisioning RUs alone does not orchestrate or scale out multiple processing workers.Consistency Level: Affects data replication guarantees and read/write ordering, not parallel processing distribution.
https://blog.nashtechglobal.com/managing-record-changes-with-change-feed-in-azure-cosmos-db/
You need to address the known issue resulting from vector similarity queries.Which two actions should you perform? Each correct answer presents part of the solution.Note: Each correct selection is worth one point.
Answer(s): B,D
Known Issues: RU consumption spikes during vector similarity queries.To address the RU (Request Unit) consumption spikes during vector similarity queries in Azure Cosmos DB, you should perform the following two steps: Modify the indexing precision of the vector fields Change the vector index type from flat to quantizedFlat or diskANNIndexing Precision Tuning: Modifying parameters like vector quantization (e.g., configuring quantizedByteSize) alters the size and precision of the stored vector elements. Lowering the precision decreases memory usage and index size, allowing faster searches that consume far fewer RUs at the expense of marginal recall accuracy.Index Type Modification: A standard flat index conducts a brute-force k-nearest neighbors (kNN) exact search across every document. This requires vast computational overhead and causes RU spikes as your dataset grows. Transitioning to quantizedFlat or diskANN leverages compression techniques and advanced graph-traversal algorithms to perform approximate nearest neighbor (ANN) searches, dropping query latency and compute costs significantly.
https://learn.microsoft.com/en-us/azure/cosmos-db/gen-ai/vector-search-performance-tips
You deploy multiple instances of a change feed processor to handle a high ingestion rate within Azure Cosmos DB for NoSQL.Each processor instance must process a different subset of partitions.You need to ensure the workload is load-balanced across all processor instances.What should you configure?
Answer(s): C
To handle a high ingestion rate in Azure Cosmos DB for NoSQL, you must deploy multiple instances of the change feed processor using the same workflow name and same lease container.
https://github.com/Azure/azure-cosmos-dotnet-v3/wiki/Comprehensive-Test-Suite-for-Azure-Cosmos-DB-Change-Feed-Processor:-All-Versions-and-Deletes
Post your Comments and Discuss Microsoft AI-200 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the AI-200 content, but please register or login to continue.