Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Microsoft Certified: Azure Solutions Architect Expert · Microsoft
Step Sequence / Reordering Question
Add and arrange the steps in the correct execution order.
Hotspot Solution:
The best solution for migrating your on-premises SQL Server databases to Azure while ensuring backup support, automatic replication across regions, and minimal administrative effort is: Recommended: Azure SQL Managed Instance with Geo-Replication Why Azure SQL Managed Instance? User-Initiated Backups – Supports manual backup operations alongside automated Azure backups. Built-in Geo-Replication – Active Geo-Replication allows multiple secondary replicas across Azure regions for high availability. Minimized Administrative Overhead – Fully managed PaaS solution that automates patching, scaling, and failover. Alternative: Azure SQL Database with Failover Groups If your system can operate without full SQL Server compatibility, Failover Groups can replicate databases across regions with automatic failover. Best for cost-optimized disaster recovery but lacks some SQL Server features. Would you like guidance on configuring geo-replication policies or cost analysis for Managed Instance vs. SQL Database?
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
Correct answer: Deployment solution - SQL Server on Azure Virtual Machines Resiliency solution - Auto-failover group Why: User-initiated backups are supported with SQL Server on Azure VMs because you have full SQL Server control, including native BACKUP and RESTORE operations. Auto-failover groups provide automatic replication across Azure regions and automated failover with minimal administration, helping meet the business continuity requirement. Zone-redundant deployment only protects within a single region, so it does not satisfy the requirement for replication across Azure regions. Active geo-replication works at the database level, but Auto-failover groups provide a more managed business continuity solution with automatic failover and lower operational effort.
Its SQL DB > active geo-replication Auto-failover groups only have 1 secondary replica (another region). active-geo replication has up to 4 secondary replicas in other regions only SQL DB supports AGR MI supports only AFG FYI SQL also supports AFGs
The best solution for migrating your on-premises SQL Server databases to Azure while ensuring backup support, automatic replication across regions, and minimal administrative effort is: Recommended: Azure SQL Managed Instance with Geo-Replication Why Azure SQL Managed Instance? User-Initiated Backups – Supports manual backup operations alongside automated Azure backups. Built-in Geo-Replication – Active Geo-Replication allows multiple secondary replicas across Azure regions for high availability. Minimized Administrative Overhead – Fully managed PaaS solution that automates patching, scaling, and failover. Alternative: Azure SQL Database with Failover Groups If your system can operate without full SQL Server compatibility, Failover Groups can replicate databases across regions with automatic failover. Best for cost-optimized disaster recovery but lacks some SQL Server features. Would you like guidance on configuring geo-replication policies or cost analysis for Managed Instance vs. SQL Database?