Exam DP-420 All Questions

View all questions & answers for the DP-420 exam

Exam DP-420 topic 5 question 3 discussion

Actual exam question from Microsoft's DP-420

Question #: 3
Topic #: 5

HOTSPOT -
You have a database named db1 in an Azure Cosmos DR Core (SQL) API account named account1. The db1 database has a manual throughput of 4,000 request units per second (RU/s).
You need to move db1 from manual throughput to autoscale throughput by using the Azure CLI. The solution must provide a minimum of 4,000 RU/s and a maximum of 40,000 RU/s.
How should you complete the CLI statements? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Hot Area:

Show Suggested Answer

Suggested Answer:

Box 1: migrate -
The az cosmosdb sql database throughput migrate command migrates the throughput of the SQL database between autoscale and manually provisioned.
Syntax: az cosmosdb sql database throughput migrate
--account-name
--name
--resource-group
--throughput-type {autoscale, manual}

Box 2: update -
The az cosmosdb sql database throughput update command updates the throughput of the SQL database under an Azure Cosmos DB account.
Syntax: az cosmosdb sql database throughput update
--account-name
--name
--resource-group
[--max-throughput]
[--throughput]

Box 3: 4000 -
Specify the throughput.

Parameter --throughput -
The throughput of SQL database (RU/s).
Note: Example migration from standard (manual) provisioned throughput to autoscale: Suppose you have a container with 10,000 RU/s manual provisioned throughput, and 25 GB of storage. When you enable autoscale, the initial autoscale max RU/s will be: 10,000 RU/s, which will scale between 1000 - 10,000 RU/s.
Note 2: Parameter --max-throughput
The maximum throughput resource can scale to (RU/s). Provided when the resource is autoscale enabled. The minimum value can be 4000 (RU/s).
Reference:
https://docs.microsoft.com/en-us/cli/azure/cosmosdb/sql/database/throughput

by Juba1711 at Nov. 29, 2022, 11:50 p.m.

Comments

Submit Cancel

RosaHutor

3 months ago

Migrate Update 40000 The question is probably incorrect. Usually `--throughput` parameter is used to configure throughput for manual mode. And `--max-throughput` is used for autoscale mode. But here `--throughput` is used for autoscale, so it is not clear how it will work, probably it will be ignored or the script will fail. https://microsoftlearning.github.io/dp-420-cosmos-db-dev/instructions/30-adjust-throughput-cli-script.html I think the question is incorrect. If the order of commands is correct, then we have to use `--max-throughput` 40000 instead of `--throughput ...`. If the order is incorrect, then we should call `-- throughput 40000` and after that we should change mode to autoscale. https://learn.microsoft.com/en-us/azure/cosmos-db/autoscale-faq?tabs=azure-powerShell#how-does-the-migration-between-autoscale-and-standard--manual--provisioned-throughput-work-

upvoted 1 times

RosaHutor

3 months ago

Anyway, answer for 3rd option is 40000, and not 4000

upvoted 1 times

...

[Removed]

7 months, 1 week ago

Migrate Update 4000 The selected answer is correct.

upvoted 3 times

...

Norvegec

1 year ago

This is very tricky question. They didn't specified the order of command in the question. The thing is, you should use "--max-throughput" attribute to set it (to 40000), cause "--throughput" is ignored in this case. Thus, the correct sequence of commands are reversed: // first, set default (max) provisioned mode (that will converted to max throughput when migration to autoscale) az cosmosdb sql database throughput update -a "account1" -g "cosmosdbrg" -n "db1" --max-throughput 40000 // then migrate to autoscale keeping the current provisioned throughput as max az cosmosdb sql database throughput migrate -a "account1" -g "cosmosdbrg" -n "db1" --throughput-type autoscale Because in autoscale mode you would still pay 1/10 of specified max throughput, you matches requirements specified in the question.

upvoted 2 times

xRiot007

11 months ago

You can only refer to the script on the screen, not add *possible* commands before it. Given this, I think that script is incorrect. When updating it should also provide a max throughput prop set to 40.000. This question seems incomplete to me.

upvoted 1 times

...

b890yc

1 year, 2 months ago

Answer: migrate, update & 4000 az cosmosdb sql database throughput migrate -a "account1" -g "cosmosdbrg" -n "db1" --throughput-type autoscale az cosmosdb sql database throughput update -a "account1" -g "cosmosdbrg" -n "db1" ---throughput 4000 To set max throughput, use the following command. az cosmosdb sql database throughput update -a "account1" -g "cosmosdbrg" -n "db1" --max-throughput 40000

upvoted 2 times

xRiot007

11 months ago

There is no 3rd command in the picture...

upvoted 1 times

...

azuredemo2022three

1 year, 5 months ago

Answer is Migrate / Migrate / 40000

upvoted 3 times

azuredemo2022three

1 year, 5 months ago

Correct Script az cosmosdb sql database throughput migrate -a "account1" -g "cosmosdbrg" -n "db1" --throughput-type autoscale az cosmosdb sql database throughput update -a "account1" -g "cosmosdbrg" -n "db1" --max-throughput 40000

upvoted 2 times

...

TRUESON

1 year, 7 months ago

For the second don‘t confuse throughput & max-throughput

upvoted 1 times

...

Juba1711

2 years ago

correct https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/manage-with-cli?source=recommendations#migrate-a-database-to-autoscale-throughput

upvoted 3 times

...