Pass the Microsoft Certified: Azure Cosmos DB Developer Specialty DP-420 Questions and answers with Dumpstech

C:\Users\Waqas Shahid\Desktop\Mudassir\Untitled.jpg

Instead create an Azure function that uses Azure Cosmos DB Core (SQL) API change feed as a trigger and Azure event hub as the output.

The Azure Cosmos DB change feed is a mechanism to get a continuous and incremental feed of records from an Azure Cosmos container as those records are being created or modified. Change feed support works by listening to container for any changes. It then outputs the sorted list of documents that were changed in the order in which they were modified.

The following diagram represents the data flow and components involved in the solution:

Box 1 = The current backup policy provides protection for: 2 Hours

 Azure Cosmos DB automatically takes backups of your data at regular intervals. The backup interval and the retention period can be configured from the Azure portal. You can also choose between two backup modes: periodic backup mode and continuous backup mode. Periodic backup mode is the default mode for all existing accounts and it takes a full backup of your database every 4 hours by default.  Cont inuous backup mode is a new mode that allows you to restore to any point of time within either 7 or 30 days 1 .

For your scenario, based on the exhibit, you have configured a backup for an Azure Cosmos DB for NoSQL account using the periodic backup mode with a backup interval of 1 hour and a reten tion period of 2 hours. This means that Azure Cosmos DB will take a full backup of your database every hour and keep only the latest two backups. Therefore, the current backup policy provides protection for  2 hours .

Box 2: In case of emergency, you must (answer choice) to restore the backup = create a support ticket

Azure Cosmos DB automatically takes backups of your data at regular intervals. You can configure the backup interval and the retention period from the Azure portal. You can also choose between two backup modes: periodic backup mode and continuous backup mode. Periodic backup mode is the default mode for all existing accounts and it takes a full backup of your database every 4 hours by default.  Continuous backup mode is a new mode that allows you to restore to any point of time within either 7 or 30 days 1 .

For your scenario, based on the exhibit, you have configured a backup for an Azure Cosmos DB for NoSQL account using the periodic backup mode with a backup interval of 1 hour and a retention period of 2 hours. This means that Azure Cosmos DB will take a full backup of your database every hour and keep only the latest two backups. In case of emergency, you must  create a support ticket  to restore the backup. This is the answer to your question.

To restore data from a periodic backup, you need to create a support request with Azure Cosmos DB team and provide the following information:

The name of your Azure Cosmos DB account

The name of the database or container that you want to restore

The date and time (in UTC) that you want to restore from

The name of the target Azure Cosmos DB account where you want to restore the data

The name of the target resource group where you want to restore the data

The Azur e Cosmos DB team will then initiate the restore process and notify you when it is completed 2 .

The disableLocalAuth property is a boolean flag that indicates whether local authentication methods such as primary/secondary keys are disabled for the Azure Cosmos DB account.  Setting this property to true improves security by ensuring that Azur e Cosmos DB accounts exclusively require Azure Active Directory identities for authentication 1 .

Batch size: An integer that represents how many objects are being written to Cosmos DB collection in each batch. Usually, starting with the default batch size is sufficient. To further tune this value, note:

Cosmos DB limits single request ' s size to 2MB. The formula is " Request Size = Single Document Size * Batch Size " . If you hit error saying " Request size is too large " , reduce the batch size value.

The larger the batch size, the better throughput the service can achieve, while make sure you allocate enough RUs to empower your workload.

Box 1 = Range

 Azure Cosmos DB supports three types of indexes: range, spatial and composite. For the query you provided, which is an equality query on a single property, the best type of index to use is  range .  Range index is based on an ordered tree-like structure and it is used for equality queries, range queries and checking for the presence of a property 1 .  Range index also supports any string or number 2 .

Box 2 = Composite

Azure Cosmos DB supports three types of indexes: range, spatial and composite. For the query you provided, which is an order by query on two properties, the best type of index to use is  composite .  Composite ind ex is used for optimizing order by queries on multiple prop erties 1 .  Composite index allows you to specify a list of property paths and sort orders that are used for ordering items 2 .

Box 3 = spatial

Azure Cosmos DB supports three types of indexes: range, spatial and composite. For the query you provided, which is a spatial query on a point property, the best type of index to use is  spatial .  Spatial index is used for querying items based on their location or proximity to a given point 1 .  Spatial index supports point, polygon and linestring data types 2 .

Bounded staleness is frequently chosen by globally distributed applications that expect low write latencies but require total global order guarantee. Bounded staleness is great for applications featuring group collaboration and sharing, stock ticker, publish-subscribe/queueing etc.

Scenario: Application updates in con-product frequently cause HTTP status code 429 " Too many requests " . You discover that the 429 status code relates to excessive request unit (RU) consumption during the updates.