The Tamilalt Corporation is moving large amounts of data into Azure. They want to use a fully managed database service with global distribution and replication capabilities. They want to use Azure Cosmos DB.

The Tamilalt Corporation is moving large amounts of data into Azure. They want to use a fully managed database service with global distribution and replication capabilities. They want to use Azure Cosmos DB.

Which of the following statements about Azure Cosmos DB are TRUE? (Choose two.)

A) Time to Live or TTL is the ability to refresh items automatically from a container, after a certain time period.

B) Azure Cosmos DB provides only four APIs: Core (SQL) and MongoDB for document data, Azure Table, and Cassandra.

C) Replica-set is a self-managed and dynamically load-balanced group of replicas spread across a single fault domain.

D) The connection modes to connect to Azure Cosmos DB are DirectTcp, Directhttps, and Gateway.

E) The maximum of number of Azure Cosmos DB accounts that you can create under an Azure subscription is 100.

Explanation

The following statements are true:

• The connection modes to connect to Azure Cosmos DB are DirectTcp, Directhttps, and Gateway.
• The maximum of number of Azure Cosmos DB accounts that you can create under an Azure subscription is 100

You can create a maximum of 100 Azure Cosmos DB accounts under an Azure subscription. To manage your data and provisioned throughput, create one or more Azure Cosmos databases under your account and within that database, create one or more containers

DirectTcp, DirectHttps, and Gateway are connection modes to use with Azure Cosmos DB. DirectTcp and Directhttps use the TCP and HTTPS protocols. Both these modes need ports between 10000 and 20000 to be open, because Azure Cosmos DB uses dynamic TCP ports. Gateway mode uses the standard HTTPS port and a single endpoint.

Time to Live or TTL is not the ability to refresh items automatically from a container, after a certain time period. Time to Live or TTL is the ability to DELETE items automatically from a container, after a certain time period. TTL is configured in seconds. After a TTL is set for a container or an item, Azure Cosmos DB automatically deletes the items after the specified time period, since the time they were last modified.

Replica-set is a self-managed and dynamically load-balanced group of replicas spread across a multiple fault domains, not a single fault domain. Azure Cosmos DB’s global distribution relies on two key abstractions – replica-sets and partition-sets. A physical partition is materialized as a self-managed and dynamically load-balanced group of replicas spread across multiple fault domains, called a replica-set. A group of physical partitions, one from each of the configured with the Cosmos database regions, is composed to manage the same set of keys replicated across all the configured regions. This higher coordination primitive is called a partition-set - a geographically distributed dynamic overlay of physical partitions managing a given set of keys.

Azure Cosmos DB provides five APIs, not four: Core (SQL) and MongoDB for document data, Gremlin for graph data, Azure Table, and Cassandra.

 

Objective:

Describe core Azure services

Sub-Objective:

Describe core resources available in Azure

References:

Azure > Time to Live (TTL) in Azure Cosmos DB

Azure > Performance tips for Azure Cosmos DB and .NET

Azure > Use Data migration tool to migrate your data to Azure Cosmos DB

Azure > Quickstart: Create an Azure Cosmos account, container, and items with the Azure portal

Azure > Work with Azure Cosmos account