Microsoft Azure Data FundamentalsDescribe how to work with relational data on AzureHard
A global e-commerce company uses Azure Database for MySQL to power its storefront. Due to rapid growth, the database is experiencing high read traffic from multiple regions, leading to performance bottlenecks. Write operations are centralized, but read operations need to scale out globally with low latency. Which Azure Database for MySQL feature should be implemented to address this challenge?
- APoint-in-time restore
- BHigh Availability (HA) configuration
- CAutomatic scaling of compute
- DRead Replicas
Show answer & explanationAnswer & explanation
Correct answer: D. Read Replicas
Read Replicas in Azure Database for MySQL allow you to offload read-heavy workloads from the primary server to up to 10 read-only copies, which can be distributed globally to serve users with low latency, directly addressing the requirement for scaling out read operations.
Why the other options are wrong
- A. Point-in-time restore is a disaster recovery feature and does not address read scaling or performance bottlenecks.
- B. High Availability (HA) configuration ensures uptime in case of failures but does not scale out read workloads across regions.
- C. Automatic scaling of compute scales the primary server up or down, but it does not scale out reads across multiple instances or regions.
Azure DB for MySQL Read Replicas
A feature in Azure Database for MySQL that allows you to replicate data from a primary server to up to 10 read-only replica servers, enabling scale-out of read-heavy workloads and disaster recovery.
- Asynchronous replication.
- Replicas can be in different regions.
- Improves read performance and disaster recovery posture.
- Write operations are handled by the primary server only.
Memory trick: Read Replicas: Global libraries for speedy reads.