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.

Practice

1. Why do managed databases save time for users?

easy

A. They require manual installation of software.

B. Users must configure backups themselves.

C. They handle setup and maintenance automatically.

D. They need constant manual performance tuning.

Solution

1. Step 1: Understand what setup and maintenance mean

   Setup means installing and configuring the database. Maintenance means keeping it running smoothly over time.

2. Step 2: Identify how managed databases help

   Managed databases automate setup and maintenance tasks, so users don't do them manually.

3. Final Answer:

   They handle setup and maintenance automatically. -> Option C

4. Quick Check:

   Managed databases save time by automating setup and maintenance [OK]

Hint: Managed means automatic setup and upkeep [OK]

Common Mistakes:

• Thinking users must install software manually
• Assuming backups are always manual
• Believing performance tuning is always user responsibility

2. Which of the following is the correct way to describe a managed database service in Azure?

easy

A. A service where you manually install and update the database software.

B. A service that automatically handles backups and scaling.

C. A service that requires you to manage security patches yourself.

D. A service that only provides storage without database features.

Solution

1. Step 1: Review managed database features

   Managed databases automatically handle backups, scaling, and updates.

2. Step 2: Match options to features

   A service that automatically handles backups and scaling. correctly states automatic backups and scaling. Others describe manual tasks or lack features.

3. Final Answer:

   A service that automatically handles backups and scaling. -> Option B

4. Quick Check:

   Managed means automatic backups and scaling [OK]

Hint: Managed means automatic, not manual tasks [OK]

Common Mistakes:

• Confusing manual installation with managed service
• Ignoring automatic backup features
• Thinking managed means only storage

3. Consider this Azure managed database feature list:
{automaticBackups: true, scaling: 'auto', securityPatches: 'auto', manualTuning: false}
What is the expected behavior of this database service?

medium

A. Backups and patches happen automatically; scaling adjusts as needed.

B. Manual tuning is required for performance; backups are automatic.

C. Backups and security patches are manual; scaling is fixed.

D. Scaling is manual; security patches are not applied.

Solution

1. Step 1: Analyze the feature list

   automaticBackups: true means backups happen automatically. scaling: 'auto' means scaling adjusts automatically. securityPatches: 'auto' means patches apply automatically. manualTuning: false means no manual tuning needed.

2. Step 2: Match behavior to options

   Backups and patches happen automatically; scaling adjusts as needed. matches all automatic features and no manual tuning.

3. Final Answer:

   Backups and patches happen automatically; scaling adjusts as needed. -> Option A

4. Quick Check:

   Automatic backups, patches, and scaling = Backups and patches happen automatically; scaling adjusts as needed. [OK]

Hint: Look for 'auto' to mean automatic handling [OK]

Common Mistakes:

• Assuming manual tuning is needed despite false flag
• Confusing manual and automatic scaling
• Ignoring security patch automation

4. You deployed an Azure managed database but notice backups are not running automatically. What is the most likely cause?

medium

A. Scaling settings prevent backups from running.

B. The database requires manual backup configuration every day.

C. Managed databases never support automatic backups.

D. Backup feature was not enabled during setup.

Solution

1. Step 1: Understand managed database backup defaults

   Managed databases usually have automatic backups but require enabling the feature during setup.

2. Step 2: Identify the cause of missing backups

   If backups are not running, likely the feature was not enabled, not that backups are always manual or unsupported.

3. Final Answer:

   Backup feature was not enabled during setup. -> Option D

4. Quick Check:

   Automatic backups need enabling [OK]

Hint: Check if backup feature is enabled first [OK]

Common Mistakes:

• Believing backups are always manual
• Thinking scaling affects backups
• Assuming managed databases lack backup support

5. Your company needs a database that automatically scales with traffic, secures data with patches, and backs up daily without manual work. Which Azure database choice best fits this need?

hard

A. Azure SQL Database managed service

B. Self-hosted SQL Server on Azure VM

C. Azure Blob Storage for data storage

D. Manual installation of MySQL on Azure VM

Solution

1. Step 1: Identify requirements

   Needs automatic scaling, automatic security patches, and daily backups without manual work.

2. Step 2: Match Azure services to requirements

   Azure SQL Database managed service provides all these features automatically. Self-hosted or manual installations require manual management. Blob Storage is not a database.

3. Final Answer:

   Azure SQL Database managed service -> Option A

4. Quick Check:

   Managed service fits all automatic needs [OK]

Hint: Managed services automate scaling, patches, backups [OK]

Common Mistakes:

• Choosing self-hosted requiring manual management
• Confusing storage with database
• Ignoring automatic patching and backups