Azure Database for MySQL - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

Understanding Azure Database for MySQL High Availability

Which of the following statements correctly describes how Azure Database for MySQL provides high availability?

A It uses active-active replication across multiple regions to ensure zero downtime.

B It automatically creates a standby server in the same region with synchronous replication for failover.

C It requires manual setup of replication between two servers for high availability.

D It relies on client-side retry logic without any built-in failover mechanism.

💡 Hint

Think about how Azure ensures your database stays available without manual intervention.

Azure Database for MySQL provides high availability by automatically creating a standby server in the same region. It uses synchronous replication to keep data in sync and failover happens automatically if the primary server fails.

❓ Configuration

intermediate

Configuring Firewall Rules for Azure Database for MySQL

You want to allow your on-premises application to connect to your Azure Database for MySQL server. Which configuration step is necessary?

A Add the on-premises public IP address to the server's firewall rules in Azure portal.

B Enable public network access and leave firewall rules empty.

C Install a VPN client on the database server to accept connections.

D Configure a private endpoint and disable all firewall rules.

💡 Hint

Think about how Azure controls which IP addresses can reach your database server.

Azure Database for MySQL uses firewall rules to restrict access. To allow your on-premises app, you must add its public IP address to the server's firewall rules.

❓ Architecture

advanced

Designing for Read Scalability with Azure Database for MySQL

You have a web app with heavy read traffic and want to improve read performance using Azure Database for MySQL. Which architecture best supports this?

A Deploy multiple primary servers with independent databases and no replication.

B Use a single primary server and scale up its compute resources only.

C Use a single primary server with multiple read replicas configured in the same region.

D Configure multiple standby servers with synchronous replication for reads.

💡 Hint

Consider how Azure Database for MySQL supports scaling reads without affecting writes.

Azure Database for MySQL supports read replicas that asynchronously replicate data from the primary server. Multiple read replicas can handle read traffic, improving performance.

❓ security

advanced

Securing Data in Azure Database for MySQL

Which option correctly describes how Azure Database for MySQL protects data at rest?

A Data at rest is encrypted automatically using Azure Storage Service Encryption with a Microsoft-managed key.

B Data at rest is encrypted using client-side encryption only.

C Data at rest is encrypted only if you enable Transparent Data Encryption (TDE).

D Data at rest is not encrypted by default and requires manual encryption setup.

💡 Hint

Think about Azure's default encryption practices for managed database services.

Azure Database for MySQL automatically encrypts data at rest using Azure Storage Service Encryption with Microsoft-managed keys, providing built-in protection without extra setup.

✅ Best Practice

expert

Optimizing Backup Retention for Azure Database for MySQL

Your company requires backups to be retained for 35 days, but Azure Database for MySQL allows a maximum retention of 35 days. You want to ensure backups are available beyond this period. What is the best approach?

A Use the point-in-time restore feature to recover data beyond 35 days automatically.

B Increase the backup retention period beyond 35 days in the Azure portal settings.

C Disable automatic backups and create manual backups daily stored on the server.

D Configure the maximum 35-day retention and export backups regularly to Azure Blob Storage for longer retention.

💡 Hint

Consider Azure's backup retention limits and how to keep backups longer than allowed by default.

Azure Database for MySQL supports up to 35 days of backup retention. To keep backups longer, you should export backups regularly to Azure Blob Storage or another storage solution.

Practice

1. What is the main purpose of Azure Database for MySQL?

easy

A. To provide a managed MySQL database service in the cloud

B. To create virtual machines for running MySQL manually

C. To store files and documents in the cloud

D. To host websites without databases

Solution

1. Step 1: Understand Azure Database for MySQL service

   It is a managed service that runs MySQL databases in the cloud, handling maintenance tasks.

2. Step 2: Compare options with service purpose

   Only To provide a managed MySQL database service in the cloud describes a managed MySQL database service, others describe unrelated services.

3. Final Answer:

   To provide a managed MySQL database service in the cloud -> Option A

4. Quick Check:

   Managed MySQL service = To provide a managed MySQL database service in the cloud [OK]

Hint: Managed means Azure handles database tasks for you [OK]

Common Mistakes:

• Confusing database service with virtual machines
• Thinking it stores files like blob storage
• Assuming it hosts websites directly

2. Which of the following is the correct way to create a new Azure Database for MySQL server using Azure CLI?

easy

A. az mysql server new --resource-group MyGroup --name MyServer --location eastus --admin-user admin --admin-password MyPass123

B. az sql server create --resource-group MyGroup --name MyServer --location eastus --admin-user admin --admin-password MyPass123

C. az mysql server create --resource-group MyGroup --name MyServer --location eastus --admin-user admin --admin-password MyPass123

D. az mysql create server --resource-group MyGroup --name MyServer --location eastus --admin-user admin --admin-password MyPass123

Solution

1. Step 1: Identify correct Azure CLI command syntax

   The correct command to create a MySQL server is az mysql server create.

2. Step 2: Check options for correct command and parameters

   az mysql server create --resource-group MyGroup --name MyServer --location eastus --admin-user admin --admin-password MyPass123 uses the correct command and parameters. Options A, B, and C use incorrect commands or syntax.

3. Final Answer:

   az mysql server create --resource-group MyGroup --name MyServer --location eastus --admin-user admin --admin-password MyPass123 -> Option C

4. Quick Check:

   Correct CLI command = az mysql server create --resource-group MyGroup --name MyServer --location eastus --admin-user admin --admin-password MyPass123 [OK]

Hint: Use 'az mysql server create' to create MySQL server [OK]

Common Mistakes:

• Using 'az sql' instead of 'az mysql'
• Incorrect command order or missing 'server'
• Using 'new' or 'create server' incorrectly

3. Given this Azure CLI command output snippet after creating a MySQL server:

{
  "name": "myserver",
  "location": "eastus",
  "userVisibleState": "Ready",
  "version": "5.7"
}

What does the userVisibleState value indicate?

medium

A. The server is currently being deleted

B. The server is ready to use

C. The server is paused

D. The server is in an error state

Solution

1. Step 1: Understand 'userVisibleState' meaning

   This field shows the current status of the MySQL server as seen by the user.

2. Step 2: Interpret the value 'Ready'

   'Ready' means the server is fully set up and available for connections.

3. Final Answer:

   The server is ready to use -> Option B

4. Quick Check:

   'Ready' means usable server = The server is ready to use [OK]

Hint: 'Ready' means server is active and usable [OK]

Common Mistakes:

• Confusing 'Ready' with 'Paused' or 'Deleting'
• Assuming 'Ready' means error or maintenance
• Ignoring the status field meaning

4. You tried to connect to your Azure Database for MySQL server but got a connection error. Which of the following is the most likely cause?

medium

A. The MySQL version is outdated

B. The database name is missing in the connection string

C. The server is located in a different Azure region

D. The server firewall rules do not allow your client IP

Solution

1. Step 1: Identify common connection error causes

   Firewall rules blocking client IP is a frequent cause of connection failures.

2. Step 2: Evaluate other options

   MySQL version or region mismatch usually do not cause connection errors. Missing database name causes different errors.

3. Final Answer:

   The server firewall rules do not allow your client IP -> Option D

4. Quick Check:

   Firewall blocking IP = The server firewall rules do not allow your client IP [OK]

Hint: Check firewall rules to allow your IP address [OK]

Common Mistakes:

• Ignoring firewall settings
• Blaming MySQL version for connection issues
• Assuming region affects connectivity directly

5. You want to ensure your Azure Database for MySQL server automatically scales compute resources during peak hours and reduces them at night to save cost. Which Azure feature should you use?

hard

A. Use the 'Flexible Server' deployment option with auto-scaling enabled

B. Enable the 'Auto-scaling' feature in the server configuration

C. Configure the server with the 'Burstable' pricing tier

D. Manually change the server SKU daily using Azure CLI scripts

Solution

1. Step 1: Understand scaling options in Azure Database for MySQL

   The Flexible Server deployment supports auto-scaling features for compute resources.

2. Step 2: Evaluate options for auto-scaling support

   Use the 'Flexible Server' deployment option with auto-scaling enabled correctly identifies Flexible Server with auto-scaling. Burstable tier does not auto-scale. Manual scripts are not automatic. 'Auto-scaling' feature is not a direct setting in standard server.

3. Final Answer:

   Use the 'Flexible Server' deployment option with auto-scaling enabled -> Option A

4. Quick Check:

   Flexible Server supports auto-scaling = Use the 'Flexible Server' deployment option with auto-scaling enabled [OK]

Hint: Use Flexible Server for built-in auto-scaling [OK]

Common Mistakes:

• Confusing Burstable tier with auto-scaling
• Thinking manual scripts are automatic
• Assuming 'Auto-scaling' is a simple toggle in all servers