Download Designing and Implementing Cloud-Native Applications Using Microsoft Azure Cosmos DB (beta).DP-420.VCEplus.2022-03-13.51q.vcex

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 discoverthat the 429 status code relates to excessive request unit (RU) consumption during the updates. Reference: https://docs.microsoft.com/en-us/azure/cosmos-db/consistency-levels

The partition key is what will determine how data is routed in the various partitions by Cosmos DB and needs to make sense in the context of your specific scenario. The IoT Device ID is generally the "natural" partition key for IoT applications.  Scenario: The iotdb database will contain two containers named con-iot1 and con-iot2. Ensure that Azure Cosmos DB costs for IoT-related processing are predictable. Reference:   https://docs.microsoft.com/en-us/azure/architecture/solution-ideas/articles/iot-using-cosmos-db

App1 queries the con-product and con-productVendor containers.  Note: Request unit is a performance currency abstracting the system resources such as CPU, IOPS, and memory that are required to perform the database operations supported by Azure Cosmos DB.   Scenario: Develop an app named App1 that will run from all locations and query the data in account1.  Once multi-region writes are configured, maximize the performance of App1 queries against the data in account1.  Whenever there are multiple solutions for a requirement, select the solution that provides the best performance, as long as there are no additional costs associated.  Incorrect Answers: A: Bounded staleness relates to writes. App1 only do reads.  Note: 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.  Reference: https://docs.microsoft.com/en-us/azure/cosmos-db/consistency-levels

leaseCollectionPrefix: when set, the value is added as a prefix to the leases created in the Lease collection for this Function. Using a prefix allows two separate Azure Functions to share the same Lease collection by using different prefixes.  Scenario: Use Azure Functions to send notifications about product updates to different recipients. Trigger the execution of two Azure functions following every update to any document in the con-product container.  Reference: https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-cosmosdb-v2-trigger

Box 1: CompanyID   After you create a container with a unique key policy, the creation of a new or an update of an existing item resulting in a duplicate within a logical partition is prevented, as specified by the unique key constraint. The partition key  combined with the unique key guarantees the uniqueness of an item within the scope of the container.  For example, consider an Azure Cosmos container with Email address as the unique key constraint and CompanyID as the partition key. When you configure the user's email address with a unique key, each item has a unique email  address within a given CompanyID. Two items can't be created with duplicate email addresses and with the same partition key value. Box 2: emailAddress Reference: https://docs.microsoft.com/en-us/azure/cosmos-db/unique-keys

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

Box 1: No An alert is triggered when the DB key is regenerated, not when it is used.  Note: The az cosmosdb keys regenerate command regenerates an access key for a Azure Cosmos DB database account. Box 2: No Only an SMS action will be taken.  Emailreceivers is empty so no email action is taken.  Box 3: Yes Yes, an alert is triggered when the DB key is regenerated.  Reference: https://docs.microsoft.com/en-us/cli/azure/cosmosdb/keys

Box 1: Resource tokens Resource tokens provide access to the application resources within a database. Resource tokens: Provide access to specific containers, partition keys, documents, attachments, stored procedures, triggers, and UDFs.  Box 2: Azure Resource Manager API You can use Azure Resource Manager to help deploy and manage your Azure Cosmos DB accounts, databases, and containers.  Incorrect Answers: The Microsoft Graph API is a RESTful web API that enables you to access Microsoft Cloud service resources.  Reference: https://docs.microsoft.com/en-us/azure/cosmos-db/secure-access-to-data https://docs.microsoft.com/enus/rest/api/resources/

Box 1: Yes The Automatic failover option allows Azure Cosmos DB to failover to the region with the highest failover priority with no user action should a region become unavailable.  Box 2: No West Europe is used for failover. Only North Europe is writable.  To Configure multi-region set UseMultipleWriteLocations to true.  Box 3: Yes Provisioned throughput with single write region costs $0.008/hour per 100 RU/s and provisioned throughput with multiple writable regions costs $0.016/per hour per 100 RU/s.  Reference: https://docs.microsoft.com/en-us/azure/cosmos-db/sql/how-to-multi-master https://docs.microsoft.com/en-us/azure/cosmosdb/optimize-cost-regions 

ARRAY_CONTAINS returns a Boolean indicating whether the array contains the specified value. You can check for a partial or full match of an object by using a boolean expression within the command.  Incorrect Answers: A: Default sorting ordering is Ascending. Must use Descending order. C: Order on Orders not on Type. Reference: https://docs.microsoft.com/en-us/azure/cosmos-db/sql/sql-query-array-contains