Exam DP-420 topic 2 question 8 discussion

All dedicated gateway connection strings follow the same pattern. Remove documents.azure.com from your original connection string and replace it with sqlx.cosmos.azure.com A C

The integrated cache in Azure Cosmos DB can be used only when the consistency level is set to either session or consistent prefix. Since App1 initially uses the consistent prefix consistency level, you need to adjust it to session (A), as session consistency is supported by the integrated cache. The dedicated gateway and its integrated cache require using a specific endpoint format (sqlx.cosmos.azure.com) to access the cache. So, you need to change the account endpoint to http://account1.sqlx.cosmos.azure.com (C). Why not the other options? B. Change the account endpoint to http://account1.documents.azure.com: This is the default endpoint format for Cosmos DB but does not support the integrated cache. D. Change the connection mode to direct: The connection mode must remain as gateway when using the integrated cache. E. Change the consistency level of requests to strong: The integrated cache does not support strong consistency.

I change my answer. The integrated cache uses the dedicated gateway within your Azure Cosmos DB account. The integrated cache only works with the Direct connection mode in the Cosmos DB SDK. Make sure App1 is configured to use this mode. While Consistent Prefix works with integrated cache, yet Microsoft recommends using Session consistency for optimal cache hit rates. If your application's design allows, consider switching to Session consistency to potentially further improve performance.

The integrated cache only works with the Direct connection mode in the Cosmos DB SDK. Make sure App1 is configured to use this mode. While Consistent Prefix works with integrated cache, yet Microsoft recommends using Session consistency for optimal cache hit rates. If your application's design allows, consider switching to Session consistency to potentially further improve performance. https://learn.microsoft.com/en-us/azure/cosmos-db/integrated-cache

AC are the correct options

A and C is correct. The endpoint needs to change and only Session and eventual consistency levels are supported

It's A and C. D is not an aswer because if you choose to connect with direct mode your requests will not use the dedicated gateway or the integrated cache. https://learn.microsoft.com/en-us/azure/cosmos-db/dedicated-gateway#connect-to-azure-cosmos-db-using-direct-mode

The answer is correct A and C

*"All dedicated gateway connection strings follow the same pattern. Remove documents.azure.com from your original connection string and replace it with sqlx.cosmos.azure.com" https://learn.microsoft.com/en-us/azure/cosmos-db/how-to-configure-integrated-cache?tabs=dotnet#configuring-the-integrated-cache *"You must ensure the request consistency is session or eventual" https://learn.microsoft.com/en-us/azure/cosmos-db/how-to-configure-integrated-cache?tabs=dotnet#adjust-request-consistency *Connection for dedicated gateway is "gateway" mode https://learn.microsoft.com/en-us/azure/cosmos-db/dedicated-gateway#connect-to-azure-cosmos-db-using-gateway-mode https://learn.microsoft.com/en-us/azure/cosmos-db/how-to-configure-integrated-cache?tabs=dotnet#verify-cache-hits

Selected Answer: AD

Selected Answer: AD

To use the integrated cache with an Azure Cosmos DB Core (SQL) API account, you need to use the "Gateway" connection mode and the "Session" or "Consistent Prefix" consistency levels. Therefore, you should perform the following actions for App1: A. Change the consistency level of requests to session. D. Change the connection mode.

To ensure that App1 can use the integrated cache, you need to configure the Cosmos DB client SDK to use the Direct connection mode and set the consistency level to session. This is because the integrated cache is available only in the Direct connection mode and the session consistency level is recommended to maximize cache hit rates.