Why managed databases matter in Azure - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a managed Azure SQL Database instance.

Azure

az sql db create --resource-group myResourceGroup --server myServer --name myDatabase --service-objective [1]

Drag options to blanks, or click blank then click option'

APremium

BStandard

CBasic

DFree

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'Free' which is not a valid service objective.

Using 'Basic' which is too limited for many workloads.

The Standard service objective is a common choice for managed Azure SQL Databases, balancing cost and performance.

2fill in blank

medium

Complete the code to enable automatic backups for the managed database.

Azure

az sql db update --resource-group myResourceGroup --server myServer --name myDatabase --backup-retention-days [1]

Drag options to blanks, or click blank then click option'

A0

B7

C30

D365

Attempts:

3 left

💡 Hint

Common Mistakes

Setting retention to 0 disables backups.

Choosing 7 days may be too short for some compliance needs.

Setting backup-retention-days to 30 enables automatic backups retained for 30 days, which is a common best practice.

3fill in blank

hard

Fix the error in the command to scale the managed database to a higher performance tier.

Azure

az sql db update --resource-group myResourceGroup --server myServer --name myDatabase --service-objective [1]

Drag options to blanks, or click blank then click option'

AP1

BS3

CBasic

DFree

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Free' which is invalid for production.

Choosing 'Basic' which is too low for scaling up.

The P1 tier is a Premium tier for higher performance. 'S3' is Standard but lower than Premium. 'Basic' and 'Free' are lower tiers.

4fill in blank

hard

Fill both blanks to configure geo-replication for disaster recovery.

Azure

az sql db replica create --resource-group myResourceGroup --server myServer --name myDatabase --partner-server [1] --partner-resource-group [2]

Drag options to blanks, or click blank then click option'

AmySecondaryServer

BmyResourceGroup

CsecondaryResourceGroup

DbackupResourceGroup

Attempts:

3 left

💡 Hint

Common Mistakes

Using the primary resource group for the partner resource group.

Confusing server names.

Geo-replication requires specifying the partner server name and the resource group where that server exists. Here, mySecondaryServer and secondaryResourceGroup are correct.

5fill in blank

hard

Fill all three blanks to create a managed database with geo-replication and a long backup retention.

Azure

az sql db create --resource-group [1] --server [2] --name [3] --backup-retention-days 35 --zone-redundant true

Drag options to blanks, or click blank then click option'

AprodResourceGroup

BprodServer

CprodDatabase

DbackupServer

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up server and resource group names.

Using backup server instead of production server.

To create a managed database with geo-replication and backups, specify the production resource group, server, and database name correctly.