Microsoft AZ-305 Practice Test - Questions Answers, Page 14

Azure Cosmos DB approaches data consistency as a spectrum of choices. This approach includes more options than the two extremes of strong and eventual consistency. You can choose from five welldefined levels on the consistency spectrum.

With Cosmos DB any write into any region must be replicated and committed to all configured regions within the account.

Reference:

https://docs.microsoft.com/en-us/azure/cosmos-db/consistency-levels-tradeoffs

Azure Front Door enables you to define, manage, and monitor the global routing for your web traffic by optimizing for best performance and instant global failover for high availability. With Front Door, you can transform your global (multi-region) consumer and enterprise applications into robust, highperformance personalized modern applications, APIs, and content that reaches a global audience with Azure. Front Door works at Layer 7 or HTTP/HTTPS layer and uses anycast protocol with split TCP andMicrosoft's global network for improving global connectivity.

Reference:

https://docs.microsoft.com/en-us/azure/frontdoor/front-door-overview

Azure Container Instances (ACI) lets you quickly deploy container instances without additional infrastructure overhead. When you connect with AKS, ACI becomes a secured, logical extension of your AKS cluster. The virtual nodes component, which is based on Virtual Kubelet, is installed in your AKS cluster that presents ACI as a virtual Kubernetes node. Kubernetes can then schedule pods that run as ACI instances through virtual nodes, not as pods on VM nodes directly in your AKS cluster.

Your application requires no modification to use virtual nodes. Deployments can scale across AKS and ACI and with no delay as cluster autoscaler deploys new nodes in your AKS cluster.

Note: AKS clusters can scale in one of two ways:

The cluster autoscaler watches for pods that can't be scheduled on nodes because of resource constraints. The cluster then automatically increases the number of nodes. The horizontal pod autoscaler uses the Metrics Server in a Kubernetes cluster to monitor the resource demand of pods. If an application needs more resources, the number of pods is automatically increased to meet the demand.

Reference:

https://docs.microsoft.com/en-us/azure/aks/concepts-scale5

With Azure Blueprints, the relationship between the blueprint definition (what should be deployed) and the blueprint assignment (what was deployed) is preserved. This connection supports improved tracking and auditing of deployments. Azure Blueprints can also upgrade several subscriptions at once that are governed by the same blueprint.

Reference:

https://docs.microsoft.com/en-us/answers/questions/26851/how-is-azure-blue-prints-differentfrom-resource-m.html

Buy reserved capacity

Sign in to the Azure portal.

Select All services > Reservations.

Select Add and then in the Purchase Reservations pane, select SQL Database to purchase a new reservation for SQL Database. Fill in the required fields. Existing databases in SQL Database and SQL Managed Instance that match the attributes you select qualify to get the reserved capacity discount. The actual number of databases or managed instances that get the discount depends on the scope and quantity selected.

Review the cost of the capacity reservation in the Costs section.

Select Purchase.

Select View this Reservation to see the status of your purchase.

Reference:

https://docs.microsoft.com/en-us/azure/azure-sql/database/reserved-capacity-overview

Quantity: The amount of compute resources being purchased within the capacity reservation. The quantity is a number of vCores in the selected Azure region and Performance tier that are being reserved and will get the billing discount. For example, if you run or plan to run multiple databases with the total compute capacity of Gen5 16 vCores in the East US region, then you would specify the quantity as 16 to maximize the benefit for all the databases.

Reference:

https://docs.microsoft.com/en-us/azure/azure-sql/database/reserved-capacity-overview

Each level provides availability and performance tradeoffs. The following image shows the different consistency levels as a spectrum.

Note: The service offers comprehensive 99.99% SLAs which covers the guarantees for throughput, consistency, availability and latency for the Azure Cosmos DB Database Accounts scoped to a single Azure region configured with any of the five Consistency Levels or Database Accounts spanning multiple Azure regions, configured with any of the four relaxed Consistency Levels.

Reference:

https://azure.microsoft.com/en-us/support/legal/sla/cosmos-db/v1_3/

https://docs.microsoft.com/en-us/azure/cosmos-db/consistency-levels#consistency-levels-andlatency

Standard StorageV2 supports the Archive access tier, which would be the cheapest solution.

Reference:

https://docs.microsoft.com/en-us/azure/storage/common/storage-introduction