exam questions

Exam AZ-305 All Questions

View all questions & answers for the AZ-305 exam

Exam AZ-305 topic 3 question 20 discussion

Actual exam question from Microsoft's AZ-305
Question #: 20
Topic #: 3
[All AZ-305 Questions]

You plan to deploy an Azure Database for MySQL flexible server named Server1 to the East US Azure region.

You need to implement a business continuity solution for Server1. The solution must minimize downtime in the event of a failover to a paired region.

What should you do?

  • A. Create a read replica.
  • B. Store the database files in Azure premium file shares.
  • C. Implement Geo-redundant backup.
  • D. Configure native MySQL replication.
Show Suggested Answer Hide Answer
Suggested Answer: C 🗳️

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
Dumber
Highly Voted 1 year, 5 months ago
It tend to differ.. Answer A seems to be possible as well. It is faster then a restore. https://learn.microsoft.com/en-us/azure/mysql/flexible-server/concepts-read-replicas#cross-region-replication-in-geo-paired-region You can create a read replica in a different region from your source server. Cross-region replication can be helpful for scenarios like disaster recovery planning or bringing data closer to your users. Azure database for MySQL Flexible Server allows you to provision read-replica in the Azure supported [geo-paired region]
upvoted 20 times
nchebbi
12 months ago
The answer should be C: Geo-redundant backup: Read replica are not meant for business continuity, failing over is manual which doesn't meet the requirement of minimizing downtime. "There's no automated failover between source and replica servers. Read replicas is meant for scaling of read intensive workloads and isn't designed to meet high availability needs of a server. Stopping the replication on read replica to bring it online in read write mode is the means by which this manual failover is performed." https://learn.microsoft.com/en-us/azure/mysql/flexible-server/concepts-read-replicas#failover
upvoted 9 times
...
hidefo6963
1 year, 5 months ago
Looks like this is the answer (A), not C. Create a read replica, then manually failover it in the case of disaster. The answer C is a Backup, restoring it will take much longer
upvoted 7 times
josola
2 months, 3 weeks ago
No, read well.
upvoted 2 times
...
...
wooyourdaddy
1 year, 2 months ago
This answer seems to be supported by this link as well: https://learn.microsoft.com/en-us/azure/mysql/single-server/concepts-read-replicas#paired-regions which states: If you're using cross-region replicas for disaster recovery planning, we recommend you create the replica in the paired region instead of one of the other regions. Paired regions avoid simultaneous updates and prioritize physical isolation and data residency.
upvoted 6 times
...
...
NotMeAnyWay
Highly Voted 1 year, 4 months ago
Selected Answer: C
C. Implement Geo-redundant backup. The Geo-redundant backup (GRB) feature in Azure Database for MySQL allows automatic backups to be stored in a different geographic region (geography). In the event of a region-wide service disruption, you can restore the database from the geo-redundant backup, which helps minimize downtime. Other options do not provide business continuity in case of regional failures. Option A, creating a read replica, primarily helps with read-heavy workloads and not for disaster recovery. Option B, storing the database files in Azure premium file shares, might improve performance but does not specifically provide a disaster recovery solution. Option D, configuring native MySQL replication, isn't supported directly within Azure Database for MySQL. Instead, you would use Azure's built-in business continuity features, such as Geo-redundant backup.
upvoted 17 times
xitzee
1 year, 2 months ago
Except you are wrong. It may help with ready-heavy workload but at th esame time it is replica to which you are able to failover. Which definetely minimazes downtime in case of outage. Read replicas ARE disaster recovery solutions
upvoted 2 times
...
...
afrancoti
Most Recent 2 weeks, 2 days ago
"C" is correct. It is all here in "Geo-redundant backup" "The service backups can be configured as geo-redundant at create time. Enabling Geo-redundancy replicates the server backup data files in the primary region’s paired region to provide regional resiliency. Geo-redundant backup storage provides at least 99.99999999999999% (16 nines) durability of objects over a given year." https://learn.microsoft.com/en-us/azure/mysql/flexible-server/concepts-business-continuity
upvoted 1 times
...
SeMo0o0o0o
3 weeks, 1 day ago
Selected Answer: C
C is correct
upvoted 1 times
...
Thanveer
3 weeks, 3 days ago
Option B not A. Why not A? read below :- https://learn.microsoft.com/en-us/previous-versions/azure/mysql/single-server/concepts-read-replicas#when-to-use-a-read-replica
upvoted 1 times
...
ElectricPants
1 month, 1 week ago
Selected Answer: A
Read replicas in Azure Database for MySQL allow for near real-time replication to another region, which can be promoted to a standalone server if there’s a primary region failure. This minimizes downtime by providing a standby server in a paired region. Geo-redundant backup (Option C) provides data protection but does not enable quick failover with minimal downtime.
upvoted 1 times
...
cosmicT73
2 months, 2 weeks ago
As per Microsoft : The standalone server can't be made into a replica again. Before you stop replication on a read replica, ensure the replica has all the data that you require.`` then having a read replica for a disaster recovery with the intention to make it again a read replica after original server recovery will not be an optimal option. thus i would go for Option C. https://learn.microsoft.com/en-us/previous-versions/azure/mysql/single-server/concepts-read-replicas
upvoted 1 times
...
josola
2 months, 3 weeks ago
Several discussions indicate that "read replicas" are a failover solution. Yes, they are IF you don't mind some data loss or delay in spinning your new database. In other words, it's not a business continuity solution as the question requires. Then as the paragraphs below indicate "A" isn't the right answer. "There's no automated failover between source and replica servers. Read replicas is meant for scaling of read intensive workloads and ISN'T DESIGNED TO MEET HIGH AVAILABILITY NEEDS OF A SERVER. Stopping the replication on read replica to bring it online in read write mode is the means by which this manual failover is performed." "If you failover to the replica, the lag at the time you delink the replica from the source indicates how much data is lost." Then answer is C. https://learn.microsoft.com/en-us/azure/mysql/flexible-server/concepts-read-replicas#failover
upvoted 1 times
...
RickySmith
7 months ago
Selected Answer: C
C Enabling Geo-redundancy replicates the server backup data files in the primary region’s paired region to provide regional resiliency. https://learn.microsoft.com/en-us/azure/mysql/flexible-server/concepts-business-continuity
upvoted 1 times
...
arnitjoe
7 months, 1 week ago
Selected Answer: C
A read replica would offer read only access to the database during a failover. That is still an outage if the database requires writes. Since the question doesn't specify that the DB is read only, A would be wrong and an incomplete solution. Same with B and D. Only C is a complete solution.
upvoted 2 times
...
Lazylinux
7 months, 3 weeks ago
Selected Answer: C
I have to agree with C as per below While it's a rare event, if you want to recover from a region-level failure, you can perform database recovery by creating a new server using the latest geo-redundant backup available under the same subscription to get to the latest data. A new flexible server is deployed to the selected region. The time taken to restore depends on the previous backup and the number of transaction logs to recover. RPO in most cases would be <1 h and RTO would vary. https://learn.microsoft.com/en-us/azure/mysql/flexible-server/concepts-business-continuity
upvoted 3 times
...
SDiwan
9 months, 2 weeks ago
Selected Answer: C
"While it's a rare event, if you want to recover from a region-level failure, you can perform database recovery by creating a new server using the latest geo-redundant backup available under the same subscription to get to the latest data. A new flexible server is deployed to the selected region. The time taken to restore depends on the previous backup and the number of transaction logs to recover. RPO in most cases would be <1 h and RTO would vary." Source: https://learn.microsoft.com/en-us/azure/mysql/flexible-server/concepts-business-continuity
upvoted 2 times
...
Msaad7
10 months ago
Selected Answer: D
D. Configure native MySQL replication
upvoted 2 times
...
rgnanav
11 months ago
Selected Answer: C
https://learn.microsoft.com/en-us/azure/mysql/flexible-server/concepts-business-continuity While it's a rare event, if you want to recover from a region-level failure, you can perform database recovery by creating a new server using the latest geo-redundant backup available under the same subscription to get to the latest data. A new flexible server is deployed to the selected region. The time taken to restore depends on the previous backup and the number of transaction logs to recover. RPO in most cases would be <1 h and RTO would vary.
upvoted 2 times
...
nchebbi
12 months ago
Selected Answer: C
The answer should be C: Geo-redundant backup: Read replica are not meant for business continuity, failing over is manual which doesn't meet the requirement of minimizing downtime. "There's no automated failover between source and replica servers. Read replicas is meant for scaling of read intensive workloads and isn't designed to meet high availability needs of a server. Stopping the replication on read replica to bring it online in read write mode is the means by which this manual failover is performed." https://learn.microsoft.com/en-us/azure/mysql/flexible-server/concepts-read-replicas#failover
upvoted 1 times
...
maxustermann
1 year, 1 month ago
Selected Answer: A
Read only replica is supported on flexible server: https://learn.microsoft.com/en-us/azure/mysql/flexible-server/how-to-read-replicas-portal?source=recommendations Also: Azure Database for MySQL - Single Server is on the retirement path. We strongly recommend for you to upgrade to Azure Database for MySQL - Flexible Server. https://learn.microsoft.com/en-us/azure/mysql/single-server/concepts-read-replicas
upvoted 2 times
...
OrangeSG
1 year, 1 month ago
Selected Answer: C
Answer A is wrong because read replica is only applicable to "Azure Database for MySQL - Single Server", while the question said "You plan to deploy an Azure Database for MySQL flexible server" Refer to Microsoft document: Read replicas in Azure Database for MySQL https://learn.microsoft.com/en-us/azure/mysql/single-server/concepts-read-replicas
upvoted 2 times
argtoub
11 months, 3 weeks ago
https://learn.microsoft.com/en-us/azure/mysql/flexible-server/concepts-read-replicas
upvoted 1 times
...
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...