Develop Solutions for Cosmos DB

Question 1

Which Consistency Level always has the latest commited write?

Answer 1

Strong

Question 2

Which Consistency Level will eventually be complete in a given timeframe?

• Strong
• Bounded staleness
• Session
• Consistent prefix
• Eventual

Answer 2

Bounded staleness

Question 3

Which Consistency Level will be consistent within a client context?

Answer 3

Session

Question 4

Which Consistency Level may not be complete, but won’t be out of order?

• Strong
• Bounded staleness
• Session
• Consistent prefix
• Eventual

Answer 4

Consistent Prefix

Question 5

Which Consistency Level may return events out of order?

• Strong
• Bounded staleness
• Session
• Consistent prefix
• Eventual

Answer 5

Eventual Consistency

Question 6

If you need to ensure that clients never receive a partial write, which one should you use?

• Strong
• Bounded staleness
• Session
• Consistent prefix
• Eventual

Answer 6

Strong

Question 7

Which of the following options affects the number of request units it takes to write a document?

Size of the document

Item property count

Indexing policy

All of the above

Answer 7

All of the above

Question 8

True or False? A partition key defines the partition strategy, it’s set when you create a container and can’t be changed

Answer 8

True

Question 9

True or false: You can add a partition key to an Azure Cosmos DB container after it has been created.

Answer 9

False, You can set the partition key only when the container is created.

Question 10

True or False? Core (SQL) API is the default Api for Azure Cosmos DB

Answer 10

True

Question 11

True or False? Core (SQL) API: You can query hierarchical JSON documents with a SQL-like language

Answer 11

True

Question 12

Which consistency level should you use for the lowest latency?

Answer 12

Eventual

Question 13

What’s the standard throughput on a cosmos DB container?

Answer 13

400 RU/s

Question 14

When would you choose between Standard and autoscale for throughput?

Answer 14

Standard - for workloads with steady or predictable traffic

Autoscale - for workloads with variable or unpredicable hours

Question 15

When will you save more with manual vs autoscalling?

Answer 15

Of all hours in a month, if you set autoscale max RU/s Tmax and use the full amount Tmax for 66% of the hours or less, it’s estimated you’ll save with autoscale.

Question 16

What are some use cases for using autoscale?

Answer 16

Variable or unpredictable workloads
    New applications
    Infrequently used applications
    Development and test workloads
    Scheduled production workloads/queries

Question 17

Which class would you use to retreive data from an Azure Cosmos DB?

Answer 17

DocumentClient

Question 18

What class would you use to retrieve data from an Azure table storage account?

Answer 18

CloudTableClient