Free DP-420 Exam Braindumps
Designing and Implementing Cloud-Native Applications Using Microsoft Azure Cosmos DB Questions 11–15 (page: 22)

Updated On: 16-Nov-2026
View Related Case Study

You have an Azure Cosmos DB for NoSQL account named account1 that supports an application named App1. App1 uses the consistent prefix consistency level.
You configure account1 to use a dedicated gateway and integrated cache.
You need to ensure that App1 can use the integrated cache.
Which two actions should you perform for App1? Each correct answer presents part of the solution.
Note: Each correct selection is worth one point.

  1. Change the consistency level of requests to session.
  2. Change the account endpoint to http://account1.documents.azure.com.
  3. Change the account endpoint to http://account1.sqlx.cosmos.azure.com.
  4. Change the connection mode to direct.
  5. Change the consistency level of requests to strong.

Answer(s): A,C

Explanation:

C: Modify your application's connection string to use the new dedicated gateway endpoint.
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 dedicated gateway will always have the same connection string, even if you remove and reprovision it.
A: You must adjust the request consistency to session or eventual. If not, the request will always bypass the integrated cache.


Reference:

https://docs.microsoft.com/en-us/azure/cosmos-db/how-to-configure-integrated-cache



View Related Case Study

HOTSPOT (Drag and Drop is not supported)
You have an Azure subscription.
You need to create a container named Container1 in an Azure Cosmos DB for NoSQL account by using a Bicep file. The solution must ensure that Container1 supports partition key sizes of up to 1 KB.
How should you complete the file? To answer, select the appropriate options in the answer area.
Note: Each correct selection is worth one point.
Hot Area:

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Box 1: MultiHash
Since multiple paths are provided ('/TenantId' and '/UserID'), this represents a Hierarchical Partition Key setup, which requires setting the kind to 'MultiHash'.
For a single partition key path, this value would be 'Hash'.
Box 2: 2
To support partition key sizes of up to 1 KB (large partition keys), you must configure the partition key version to 2.
Version 1 only supports the older 101-byte.


Reference:

https://learn.microsoft.com/en-us/azure/cosmos-db/hierarchical-partition-keys



View Related Case Study

You have an Azure subscription that contains an Azure Cosmos DB for NoSQL account named Account1. Account1 has a default consistency level of strong and is in the East US Azure region.
You need to recommend configuration changes to Account1 that meet the following requirements:
● Add a second Azure region of West US.
● Enable multi-region writes.
● Maximize data consistency.
What should you recommend?

  1. Add the West US region, and then enable multi-region writes without changing the default consistency level.
  2. Change the default consistency level to session, add the West US region, and then enable multi-region writes.
  3. Change the default consistency level to eventual, add the West US region, and then enable multi-region writes.
  4. Change the default consistency level to consistent prefix, add the West US region, and then enable multi-region writes.

Answer(s): B

Explanation:

Change the default consistency level to session, add West US, and enable multi-region writes. Session is the strongest compatible consistency level among the listed choices and provides read-your-writes and monotonic-read guarantees within a client session when session tokens are maintained.


Reference:

https://learn.microsoft.com/en-us/azure/cosmos-db/consistency-levels#session-consistency



View Related Case Study

HOTSPOT (Drag and Drop is not supported)
You have a multi-region Azure Cosmos DB account named account1 that has a default consistency level of strong.
You have an app named App1 that is configured to request a consistency level of session.
How will the read and write operations of App1 be handled? To answer, select the appropriate options in the answer area.
Hot Area:

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Box 1: Write and replicate data to every region synchronously
Overriding the default consistency level only applies to reads within the SDK client. An account configured for strong consistency by default will still write and replicate data synchronously to every region in the account.
Box 2: To which App1 is connected.
Overriding the default consistency level only applies to reads within the SDK client.
When the SDK client instance or request overrides this with Session or weaker consistency, reads will be performed using a single replica.
For read operations, Azure Cosmos DB sends the cached session token to the server with a guarantee of receiving data that corresponds to the specified (or a more recent) session token.


Reference:

https://learn.microsoft.com/en-us/azure/cosmos-db/consistency-levels



View Related Case Study

You have a Windows 11 device that has the Azure Cosmos DB emulator installed.
You need to use the emulator to validate the implementation of a hierarchical partition key.
Which command line switch should you use when you launch the emulator?

  1. /Key
  2. /KeyFile
  3. /EnablePreview
  4. /PartitionCount

Answer(s): C

Explanation:

To validate a hierarchical partition key (subpartitioning) implementation, you must use the /EnablePreview command line switch when launching the local Azure Cosmos DB Emulator.


Reference:

https://learn.microsoft.com/en-us/azure/cosmos-db/hierarchical-partition-keys



Viewing page 22 of 61
Viewing questions 106 - 110 out of 296 questions


Post your Comments and Discuss Microsoft DP-420 exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!