AZ-204 Certification Practice Question #139

Question

You have an Azure Web app that uses Cosmos DB as a data store. You create a CosmosDB container by running the following PowerShell script:
$resourceGroupName = "testResourceGroup"
$accountName = "testCosmosAccount"
$databaseName = "testDatabase"
$containerName = "testContainer"
$partitionKeyPath = "/EmployeeId"
$autoscaleMaxThroughput = 5000

New-AzCosmosDBSqlContainer -
-ResourceGroupName $resourceGroupName
-AccountName $accountName
-DatabaseName $databaseName
-Name $containerName
-PartitionKeyKind Hash
-PartitionKeyPath $partitionKeyPath
-AutoscaleMaxThroughput $autoscaleMaxThroughput
You create the following queries that target the container:
SELECT * FROM c WHERE c.EmployeeId > '12345'
SELECT * FROM c WHERE c.UserID = '12345'
For each of the following statements, select Yes if the statement is true. Otherwise, select No.
NOTE: Each correct selection is worth one point.
Hot Area:

Accepted Answer

First, for autoscale containers in Cosmos DB, the throughput scales dynamically between a minimum of 10% of the set maximum autoscale throughput and the maximum throughput itself. With `AutoscaleMaxThroughput` set to 5000 RU/s, the scale range is 500 to 5000 RU/s, making the minimum throughput 500 RU/s (not 400 RU/s). Second, to qualify as an in-partition query, a query must include an equality filter on the partition key; because the first query uses a range filter (`c.EmployeeId > '12345'`), it cannot be optimized to a single partition. Third, because the second query filters on `UserID` (which is not the partition key `EmployeeId`), it must search across all partitions, classifying it as a cross-partition query.

More AZ-204 practice questions