Skip to content
Compiled Thoughts
Browse

AZ-305 Business Continuity solutions

April 29, 2025•1817 words•10 min read•
certification
azure
AI summarised

AZ-305 Azure Solutions Architect Expert

Azure Recommendations for Business Continuity Solutions

Below are the recommended Azure solutions for data storage as aligned with the AZ-305 exam objectives.

Design Solutions for Backup and Disaster Recovery

1. Recommend a Recovery Solution for Azure/Hybrid Workloads

Azure Site Recovery (ASR)

  • Use Case: Orchestrates replication, failover, and failback of Azure VMs, on-premises VMware/Hyper-V VMs, and physical servers.
  • Hybrid Workloads:
    • Replicate on-premises VMs to Azure for disaster recovery (DR).
    • Automate recovery plans with multi-VM consistency for apps spanning multiple VMs.
  • Recovery Objectives:
    • RPO: As low as 5 minutes (continuous replication).
    • RTO: Minutes with automated failover123.

Azure Backup

  • Centralized Management: Protects Azure VMs, on-premises files/folders (via MARS agent), SQL/PostgreSQL databases, SAP HANA, and Azure Blobs.
  • Hybrid Support:
    • Use Azure Backup Server (MABS) or DPM for on-premises VMware/Hyper-V VMs.
    • Long-term retention (up to 10 years) for compliance453.

Best Practices:

  • Combine ASR for VM failover and Azure Backup for granular file/database recovery.
  • Use Azure Arc to extend Azure management to on-premises servers for unified policy enforcement56.

2. Recommend a Backup/Recovery Solution for Compute

Azure VM Backup

  • Application-Consistent Snapshots: Ensures data integrity for apps like SQL Server73.
  • Managed Disk Backups:
    • Locally Redundant Storage (LRS): Protects against rack/drive failures.
    • Zone-Redundant Storage (ZRS): Tolerates zonal outages28.
  • Restore Options: Full VM restore, individual files, or disks.

Best Practices:

  • Enable Soft Delete and Resource Locks to prevent accidental deletion.
  • Use Azure Policy to enforce backup compliance across subscriptions79.

3. Recommend a Backup/Recovery Solution for Databases

Azure SQL Database/Managed Instance

  • Automated Backups:
    • Full weekly + differential every 12 hours + log backups every 10 minutes.
    • Point-in-Time Restore (PITR): Up to 35 days retention (extendable to 10 years with LTR)1011.
  • Azure Backup for SQL:
    • Application-consistent backups for SQL Server on Azure VMs3.

Cosmos DB

  • Continuous Backups: 7-day retention with 1-second granularity for NoSQL/API for MongoDB.

Best Practices:

  • For mission-critical SQL workloads, use Business Critical tier with built-in Always On availability groups1213.

4. Recommend a Backup/Recovery Solution for Unstructured Data

Azure Blob Storage

  • Operational Backup:
    • Point-in-Time Restore: Recover from accidental deletes/corruption using soft delete and versioning9.
  • Vaulted Backup:
    • Offsite backups to a Recovery Services vault with custom retention policies914.

Azure Files

  • Snapshot Backups:
    • Schedule daily/weekly snapshots with Azure Backup.
    • Restore individual files or entire shares instantly15.

Data Lake Storage Gen2

  • Vaulted Backup (Preview): Replicate containers to a backup vault for regional outages14.

Best Practices:

  • Use Cool/Archive tiers for infrequently accessed data to reduce costs914.

Design for High Availability

1. Recommend a High Availability Solution for Compute

Virtual Machine Scale Sets (VMSS)

  • Autoscaling: Adjust instance count based on CPU/memory metrics.
  • Orchestration Modes:
    • Flexible: Distribute VMs across Availability Zones (99.99% SLA).
    • Uniform: Fault/update domain isolation within a zone (99.95% SLA)16.

Availability Zones (AZs)

  • Deploy VMs across 3+ zones for resilience against data center failures81718.

Best Practices:

  • Use Proximity Placement Groups to minimize latency for performance-sensitive apps86.

2. Recommend a High Availability Solution for Relational Data

Azure SQL Database/Managed Instance

  • Business Critical Tier:
    • Built-in Always On availability groups with synchronous replicas.
    • Zone-Redundant Configuration: Spread replicas across AZs (99.995% SLA)181213.

SQL Server on Azure VMs

  • Always On Availability Groups:
    • Deploy primary and secondary replicas across Availability Zones6.

Best Practices:

  • For cross-region HA, enable Auto-Failover Groups in Azure SQL1213.

3. Recommend a High Availability Solution for Semi/Unstructured Data

Azure Cosmos DB

  • Multi-Region Writes: Enable writes in 30+ regions with automatic failover (99.999% SLA).
  • Consistency Levels: Choose from "Strong" to "Eventual" based on app needs.

Azure Blob Storage

  • Redundancy Options:
    • ZRS: 99.9999999999% durability within a region.
    • GRS: Cross-region replication for geo-resiliency98.

Azure Files

  • Zone-Redundant Storage (ZRS): HA within a region.
  • Geo-Redundant Storage (GRS): DR across regions15.

Best Practices:

  • For analytics workloads, use Data Lake Storage Gen2 with ZRS/GRS and hierarchical namespace14.

Summary Table

RequirementAzure RecommendationKey Features
Hybrid Workload RecoveryASR + Azure BackupRPO 5 min, automated failover, MARS agent for on-premises
Compute BackupAzure VM Backup (application-consistent snapshots)LRS/ZRS redundancy, Soft Delete
Database BackupSQL Automated Backups + Azure Backup for SQL VMsPITR, 15-min RPO, LTR up to 10 years
Unstructured Data BackupBlob Storage (versioning/soft delete) + Azure Files BackupOperational/vaulted backups, cross-region restore
Compute HAVMSS (Flexible mode) + Availability Zones99.99% SLA, autoscaling
Relational Data HASQL DB Business Critical (zone-redundant) + Auto-Failover Groups99.995% SLA, cross-region failover
Semi/Unstructured HACosmos DB (multi-region writes) + Blob ZRS/GRS99.999% SLA, geo-redundancy

By aligning these recommendations, you ensure compliance with Azure’s SLAs and optimize for cost, performance, and resilience.

Summarised with Perplexity.

Footnotes

  1. https://n2ws.com/blog/microsoft-azure-cloud-services/disaster-recovery-plans-in-azure-site-recovery-a-practical-guide ↩
  2. https://learn.microsoft.com/en-us/azure/virtual-machines/backup-and-disaster-recovery-for-azure-iaas-disks ↩ ↩2
  3. https://learn.microsoft.com/en-us/azure/backup/backup-azure-sql-database ↩ ↩2 ↩3 ↩4
  4. https://azure.microsoft.com/en-in/solutions/backup-and-disaster-recovery ↩
  5. https://learn.microsoft.com/en-us/azure/backup/backup-overview ↩ ↩2
  6. https://learn.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/availability-group-overview?view=azuresql ↩ ↩2 ↩3
  7. https://n2ws.com/blog/vm-backup-in-azure-a-practical-guide ↩ ↩2
  8. https://learn.microsoft.com/en-us/azure/virtual-machines/disks-high-availability ↩ ↩2 ↩3 ↩4
  9. https://learn.microsoft.com/en-us/azure/backup/blob-backup-overview ↩ ↩2 ↩3 ↩4 ↩5
  10. https://n2ws.com/blog/microsoft-azure-cloud-services/azure-sql-database-backup-a-practical-guide ↩
  11. https://learn.microsoft.com/en-us/azure/azure-sql/managed-instance/automated-backups-overview?view=azuresql ↩
  12. https://docs.azure.cn/en-us/azure-sql/managed-instance/high-availability-sla-local-zone-redundancy ↩ ↩2 ↩3
  13. https://learn.microsoft.com/en-us/azure/azure-sql/managed-instance/sql-managed-instance-paas-overview?view=azuresql ↩ ↩2 ↩3
  14. https://learn.microsoft.com/en-us/azure/backup/azure-data-lake-storage-backup-overview ↩ ↩2 ↩3 ↩4
  15. https://learn.microsoft.com/en-us/azure/backup/azure-file-share-backup-overview ↩ ↩2
  16. https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/overview ↩
  17. https://www.linkedin.com/pulse/azure-availability-sets-vs-zones-williams-oke-omosayin ↩
  18. https://learn.microsoft.com/en-us/azure/azure-sql/database/media/high-availability-sla/zone-redundant-business-critical-service-tier.png?view=azuresql\&sa=X\&ved=2ahUKEwirwKyu6fyMAxWXwvACHQW3IDUQ_B16BAgEEAI ↩ ↩2

If you want to get in touch and hear more about this topic, feel free to contact me on or via .

© 2026 Andrei Bodea

Privacy policy

Privacy Policy

Last Updated: 2026-08-11

Thank you for visiting Compiled Thoughts (the “Blog”). We value your privacy and want to clarify how we handle any information you may provide or that may be collected when you visit this Blog. By accessing or using the Blog, you agree to the terms of this Privacy Policy.

1. Information We Do Not Collect

  • No Analytics or Tracking — We do not run analytics software, tracking pixels, session recording, or any other tool intended to profile visitors or follow them across sites.

  • No Advertisements — Our Blog does not display third-party advertisements and, therefore, does not collect data for advertising or marketing purposes.

  • No Reader Accounts or Subscriptions — Readers cannot create an account or subscribe, so we do not collect or store reader account data. Sign-in exists only for the Blog’s own author, in order to publish content.

  • No Cookies Set By Us — We do not set cookies of our own for any purpose. Please see Section 2 for the third-party services your browser contacts when you visit.

2. Third-Party Services and Automatic Data Collection

The Blog is a static site with no database of readers. However, displaying a page does require your browser to make requests to the services listed below. Those services necessarily receive your IP address, your browser’s user agent, and the address of the page you requested. This happens automatically when you visit, and we ask that you take it into account when reading Section 1.

  • Web Hosting, Netlify — The Blog is hosted by Netlify, which serves every page and may retain standard server logs, including IP addresses, for operational and security purposes.

  • Typefaces, Google Fonts — Every page loads fonts from fonts.googleapis.com and fonts.gstatic.com. As a result, Google receives your IP address and user agent when you visit. We do not use Google Analytics or any other Google advertising or measurement product.

  • Netlify Identity — The home page loads a login widget from identity.netlify.com. It exists solely so the author can sign in to publish, it offers nothing to ordinary readers, and it is not used to identify you. Your browser requests it regardless, and the widget may use your browser’s local storage to hold a sign-in session.

We do not control what these providers log or how long they retain it. Please consult their own privacy policies if that matters to you.

3. Voluntary Information

If you choose to contact us directly (for example, through an email link or contact form, if provided), we may receive personal information such as your name or email address. In such cases:

  • We will use this information solely to respond to your inquiry.

4. No Third-Party Data Sharing

Beyond the automatic requests described in Section 2, we do not share, sell, rent, or otherwise disclose personal information to third parties, because we do not collect or store any personal information about readers. In the event you voluntarily submit personal data (e.g., via direct email), we do not disclose that to any external entity.

5. Children’s Privacy

Our Blog does not target or direct content specifically to children under the age of 13. We do not knowingly collect or maintain personal information from children under 13. If you believe we may have inadvertently received personal information from a child under 13, please contact us immediately so we can delete such information.

6. External Links

Our Blog may contain links to external websites about programming, interviewing, music, books, psychology, or other related content. We are not responsible for the content, privacy policies, or practices of any third-party sites. We encourage you to review the privacy policies of those websites before interacting with them or providing any personal information.

7. Security

Although we do not collect or store personal data on our servers, we still endeavor to use reasonable security measures to protect the Blog’s integrity. However, no data transmission or storage system can be guaranteed to be 100% secure. Your use of the Blog indicates you understand and accept any inherent risks.

8. Changes to This Privacy Policy

We may update or modify this Privacy Policy from time to time to reflect changes in our practices or for other operational, legal, or regulatory reasons. If we make any material changes, we will update the “Last Updated” date at the top of this document. Your continued use of the Blog after any changes signifies your acceptance of the revised Privacy Policy.

9. Contact Us

If you have any questions or concerns about this Privacy Policy, please reach out using the email address in the header of the page.

By using Compiled Thoughts, you acknowledge that you have read, understood, and agree to this Privacy Policy.