Microsoft Microsoft Certified: Azure Cosmos DB Developer Specialty DP-420 Questions & Answers

• Question 31:

  You have a container named container1 in an Azure Cosmos DB Core (SQL) API account.

  You need to provide a user named User1 with the ability to insert items into container1 by using role-based access control (RBAC). The solution must use the principle of least privilege.

  Which roles should you assign to User1?

  A. CosmosDB Operator only

  B. DocumentDB Account Contributor and Cosmos DB Built-in Data Contributor

  C. DocumentDB Account Contributor only

  D. Cosmos DB Built-in Data Contributor only

  Correct Answer: A

  Cosmos DB Operator: Can provision Azure Cosmos accounts, databases, and containers. Cannot access any data or use Data Explorer. Incorrect Answers:

  B: DocumentDB Account Contributor can manage Azure Cosmos DB accounts. Azure Cosmos DB is formerly known as DocumentDB.

  C: DocumentDB Account Contributor: Can manage Azure Cosmos DB accounts.

  Reference: https://docs.microsoft.com/en-us/azure/cosmos-db/role-based-access-control

• Question 32:

  You have an Azure Cosmos DB Core (SQL) API account.

  You configure the diagnostic settings to send all log information to a Log Analytics workspace.

  You need to identify when the provisioned request units per second (RU/s) for resources within the account were modified.

  You write the following query.

  AzureDiagnostics

  | where Category == "ControlPlaneRequests"

  What should you include in the query?

  A. | where OperationName startswith "AccountUpdateStart"

  B. | where OperationName startswith "SqlContainersDelete"

  C. | where OperationName startswith "MongoCollectionsThroughputUpdate"

  D. | where OperationName startswith "SqlContainersThroughputUpdate"

  Correct Answer: A

  The following are the operation names in diagnostic logs for different operations:

  1.

  RegionAddStart, RegionAddComplete

  2.

  RegionRemoveStart, RegionRemoveComplete

  3.

  AccountDeleteStart, AccountDeleteComplete

  4.

  RegionFailoverStart, RegionFailoverComplete

  5.

  AccountCreateStart, AccountCreateComplete

  6.

  *AccountUpdateStart*, AccountUpdateComplete

  7.

  VirtualNetworkDeleteStart, VirtualNetworkDeleteComplete

  8.

  DiagnosticLogUpdateStart, DiagnosticLogUpdateComplete

  Reference: https://docs.microsoft.com/en-us/azure/cosmos-db/audit-control-plane-logs

• Question 33:

  You have an Azure Cosmos DB for NoSQL account.

  You need to create an Azure Monitor query that lists recent modifications to the regional failover policy.

  Which Azure Monitor table should you query?

  A. CDBPartitionKeyStatistics

  B. CDBQueryRunTimeStatistics

  C. CDBDataPlaneRequests

  D. CDBControlPlaneRequests

  Correct Answer: D

• Question 34:

  You plan to create an Azure Cosmos DB account that will use the NoSQL API.

  You need to create a grouping strategy for items that will be stored in the account. The solution must ensure that write and read operations on the items can be performed within the same transact!

  What should you use to group the items?

  A. logical partitions

  B. physical partitions

  C. databases

  D. containers

  Correct Answer: A

• Question 35:

  You have an application named App1 that reads the data in an Azure Cosmos DB Core (SQL) API account. App1 runs the same read queries every minute. The default consistency level for the account is set to eventual.

  You discover that every query consumes request units (RUs) instead of using the cache.

  You verify the IntegratedCacheiteItemHitRatemetric and the IntegratedCacheQueryHitRatemetric. Both metrics have values of 0.

  You verify that the dedicated gateway cluster is provisioned and used in the connection string.

  You need to ensure that App1 uses the Azure Cosmos DB integrated cache.

  What should you configure?

  A. the indexing policy of the Azure Cosmos DB container

  B. the consistency level of the requests from App1

  C. the connectivity mode of the App1 CosmosClient

  D. the default consistency level of the Azure Cosmos DB account

  Correct Answer: C

  Because the integrated cache is specific to your Azure Cosmos DB account and requires significant CPU and memory, it requires a dedicated gateway node. Connect to Azure Cosmos DB using gateway mode.

  Reference: https://docs.microsoft.com/en-us/azure/cosmos-db/integrated-cache-faq

• Question 36:

  After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.

  You have an Azure Cosmos DB Core (SQL) API account named account 1 that uses autoscale throughput.

  You need to run an Azure function when the normalized request units per second for a container in account1 exceeds a specific value.

  Solution: You configure an Azure Monitor alert to trigger the function.

  Does this meet the goal?

  A. Yes

  B. No

  Correct Answer: A

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

  Note: Alerts are used to set up recurring tests to monitor the availability and responsiveness of your Azure Cosmos DB resources. Alerts can send you a notification in the form of an email, or execute an Azure Function when one of your metrics reaches the threshold or if a specific event is logged in the activity log.

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

• Question 37:

  You have an Azure Cosmos DB for NoSQL account1 that is configured for automatic failover. The account1 account has a single read-write region in West US and a and a read region in East US.

  You run the following PowerShell command.

  Update-AzCosmosDBAccountFailoverPriority -ResourceGroupName `rg1` -Name `account1` -FailoverPolicy @(`East US`, `West US`)

  What is the effect of running the command?

  A. A manual failover will occur.

  B. The account will be unavailable to writes during the change.

  C. The provisioned throughput for account1 will increase.

  D. The account will be configured for multi-region writes.

  Correct Answer: D

  You can use the Set-AzCosmosDBAccountRegion cmdlet to update the regions that an Azure Cosmos DB account uses. You can use this cmdlet to add a region or change the region failover order. The cmdlet requires a resource group name, an Azure Cosmos DB account name, and a list of regions in desired failover order1. For your scenario, based on the PowerShell command, you are using the Set- AzCosmosDBAccountRegion cmdlet to update the regions for an Azure Cosmos DB account named account1 that is configured for automatic failover. The command specifies two regions: West US and East US. The effect of running the command is that the account will be configured for multi-region writes.

  Multi-region writes is a feature of Azure Cosmos DB that allows you to write data to any region in your account and have it automatically replicated to all other regions. This feature provides high availability and low latency for write operations across multiple regions. To enable multi-region writes, you need to specify at least two regions in your account and set them as write regions2. In your command, you are setting both West US and East US as write regions by using the -IsZoneRedundant parameter with a value of $true for both regions.

• Question 38:

  You have a database named db1in an Azure Cosmos DB for NoSQL account named account 1.

  You need to write JSON data to db1 by using Azure Stream Analytics. The solution must minimize costs.

  Which should you do before you can use db1 as an output of Stream Analytics?

  A. in account, add a private endpoint.

  B. In db1, create containers that have a custom indexing policy and analytical store disabled.

  C. In account, enable a dedicated gateway.

  D. In db1, create containers that have an automatic indexing policy and analytical store enabled.

  Correct Answer: A

• Question 39:

  You need to create a database in an Azure Cosmos DB Core (SQL) API account.

  The database will contain three containers named coll1, coll2, and coll3. The coll1 container will have unpredictable read and write volumes.

  The coll2 and coll3 containers will have predictable read and write volumes.

  The expected maximum throughput for coll1 and coll2 is 50,000 request units per second (RU/s) each.

  How should you provision the collection while minimizing costs?

  A. Create a serverless account.

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

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

  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.

• Question 40:

  Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.

  After you answer a question in this section, you will NOT be able to return to it. As a result1 these questions will not appear in the review screen.

  You have a database in an Azure Cosmos DB for NoSQL account that is configured for multi-region writes.

  You need to use the Azure Cosmos OB SDK to implement the conflict resolution policy for a container. The solution must ensure that any conflicts are sent to the conflicts feed.

  Solution: You set ConflictResolutionMode to Laswriterwins and you use the default settings for the policy.

  Does this meet the goal?

  A. Yes

  B. No

  Correct Answer: A