An organization is designing the relational data storage architecture on Azure for two workloads.
- Workload 1: A legacy back-office application that requires SQL Server Agent for automated job scheduling and relies on cross-database queries.
- Workload 2: A customer-facing portal with highly unpredictable traffic that frequently experiences long periods of inactivity. Minimizing cost during idle times is a key requirement.
To ensure business continuity, the storage backups for both workloads must survive the physical failure of a primary datacenter.
Which two Azure SQL options should you recommend to meet these requirements?
- Azure SQL Managed Instance with zone-redundant backup storage for Workload 1Cevap
- Azure SQL Database Serverless with zone-redundant backup storage for Workload 2Cevap
- CAzure SQL Database single database with zone-redundant backup storage for Workload 1
- DAzure SQL Managed Instance with locally redundant backup storage (LRS) for Workload 1
- ESQL Server on Azure Virtual Machines with Standard HDD storage for Workload 2
Cevap
Azure SQL Managed Instance with zone-redundant backup storage for Workload 1, and Azure SQL Database Serverless with zone-redundant backup storage for Workload 2
The correct recommendations are Azure SQL Managed Instance with zone-redundant backup storage for Workload 1, and Azure SQL Database Serverless with zone-redundant backup storage for Workload 2. Azure SQL Managed Instance provides full compatibility with the SQL Server database engine, including SQL Server Agent and cross-database queries, which are required for Workload 1. Azure SQL Database Serverless auto-scales compute and pauses during inactive periods to minimize costs, matching the requirements of Workload 2. Utilizing zone-redundant storage (ZRS) replicates data across separate availability zones within the region, ensuring backups survive the failure of a primary datacenter.
Adım Adım Çözüm
Anahtar Kavram
Selecting the appropriate Azure SQL relational database deployment options (Managed Instance vs. Database vs. VM) and backup redundancy levels to meet legacy feature requirements, cost-optimization goals, and resilience constraints.