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.