DP-420 Online Practice Questions and Answers

Correct Answer:

Box 1: Yes

VM1 is on vnet1.subnet1 which has the Endpoint Status enabled.

Box 2: No

Only virtual network and their subnets added to Azure Cosmos account have access. Their peered VNets cannot access the account until the subnets within peered virtual networks are added to the account.

Box 3: No

Only virtual network and their subnets added to Azure Cosmos account have access.

Reference:

https://docs.microsoft.com/en-us/azure/cosmos-db/how-to-configure-vnet-service-endpoint

Correct Answer:

Box 1: No

Azure Cosmos DB's change feed is a great choice as a central data store in event sourcing architectures where all data ingestion is modeled as writes (no updates or deletes).

Note: The change feed does not capture deletes. If you delete an item from your container, it is also removed from the change feed. The most common method of handling this is adding a soft marker on the items that are being deleted. You

can add a property called "deleted" and set it to "true" at the time of deletion. This document update will show up in the change feed. You can set a TTL on this item so that it can be automatically deleted later.

Box 2: No

The _etag format is internal and you should not take dependency on it, because it can change anytime.

Box 3: Yes

Change feed support in Azure Cosmos DB works by listening to an Azure Cosmos container for any changes.

Reference:

https://docs.microsoft.com/en-us/azure/cosmos-db/sql/change-feed-design-patterns

https://docs.microsoft.com/en-us/azure/cosmos-db/change-feed

Correct Answer: B

Correct Answer: A

The indexing policy has an includedPaths array that contains only one path:

/product/brand/ . This means that only the properties under /product/brand will be indexed.

The symbol indicates that only scalar values will be indexed, not arrays or objects1.

The excludedPaths array contains a single path: /* .

This means that all other properties will be excluded from indexing.

The * symbol indicates a wildcard that matches any property name1.

Therefore, the paths /product/category , /product/[ ]/category , and /product/brand/tailspin will not be indexed.

Correct Answer: B

Azure Cosmos DB offers two different capacity modes: provisioned throughput and serverless1. Provisioned throughput mode allows you to configure a certain amount of throughput (expressed in Request Units per second or RU/s) that is

provisioned on your databases and containers. You get billed for the amount of throughput you've provisioned, regardless of how many RUs were consumed1. Serverless mode allows you to run your database operations without having to

configure any previously provisioned capacity. You get billed for the number of RUs that were consumed by your database operations and the storage consumed by your data1. To create a database that minimizes costs, you should consider

the following factors:

The read and write volumes of your containers

The predictability and variability of your traffic The latency and throughput requirements of your application The geo-distribution and availability needs of your data Based on these factors, one possible option that you could choose is B. Create

a provisioned throughput account. Set the throughput for coll1 to Autoscale. Set the throughput for coll2 and coll3 to Manual.

This option has the following advantages:

It allows you to handle unpredictable read and write volumes for coll1 by using Autoscale, which automatically adjusts the provisioned throughput based on the current load1. It allows you to handle predictable read and write volumes for coll2

and coll3 by using Manual, which lets you specify a fixed amount of provisioned throughput that meets your performance needs1.

It allows you to optimize your costs by paying only for the throughput you need for each container1.

It allows you to enable geo-distribution for your account if you need to replicate your data across multiple regions1.

This option also has some limitations, such as:

It may not be suitable for scenarios where all containers have intermittent or bursty traffic that is hard to forecast or has a low average-to-peak ratio1. It may not be optimal for scenarios where all containers have low or sporadic traffic that

does not justify provisioned capacity1.

It may not support availability zones or multi-master replication for your account1. Depending on your specific use case and requirements, you may need to choose a different option. For example, you could use a serverless account if all

containers have low or sporadic traffic that does not require predictable performance or geo-distribution1 . Alternatively, you could use a provisioned throughput account with Manual for all containers if all containers have stable and consistent

traffic that requires predictable performance or geo-distribution1.

Correct Answer: D

Correct Answer: A

Correct Answer: B

Explanation:

Instead configure an Azure Monitor alert to trigger the function.

You can set up alerts from the Azure Cosmos DB pane or the Azure Monitor service in the Azure portal.

Reference:

https://docs.microsoft.com/en-us/azure/cosmos-db/create-alerts

Correct Answer: D

Explanation:

Time to live for containers and items

The time to live value is set in seconds, and it is interpreted as a delta from the time that an item was last modified. You can set time to live on a container or an item within the container:

Time to Live on a container (set using DefaultTimeToLive):

If missing (or set to null), items are not expired automatically.

If present and the value is set to "-1", it is equal to infinity, and items don't expire by default.

If present and the value is set to some non-zero number "n" – items will expire "n" seconds after their last modified time.

Reference:

https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/time-to-live

Correct Answer: C

Scenario: Develop an app named App2 that will run from the retail stores and query the data in account2. App2 must be limited to a single DNS endpoint when accessing account2.

By using Azure Private Link, you can connect to an Azure Cosmos account via a private endpoint. The private endpoint is a set of private IP addresses in a subnet within your virtual network.

When you're using Private Link with an Azure Cosmos account through a direct mode connection, you can use only the TCP protocol. The HTTP protocol is not currently supported.

Reference:

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