A smart grid utility provider is planning to migrate its relational data workloads to Azure. The migration includes the following two target databases:
* TelemetryDB stores real-time smart meter telemetry data and requires full access to the operating system's registry and local file system to run legacy hardware-interface drivers.
* BillingDB stores customer billing history and requires support for cross-database queries and SQL Server Agent jobs to automate end-of-month processing, but the operations team wants to eliminate operating system-level patching and management.
Which two Azure SQL deployment options should you recommend to host these databases? (Select two.)
- SQL Server on Azure Virtual Machines for TelemetryDBCevap
- Azure SQL Managed Instance for BillingDBCevap
- CAzure SQL Database single database for BillingDB
- DAzure SQL Managed Instance for TelemetryDB
- EAzure SQL Database elastic pool for TelemetryDB
Cevap
SQL Server on Azure Virtual Machines for TelemetryDB and Azure SQL Managed Instance for BillingDB
Hosting TelemetryDB on SQL Server on Azure Virtual Machines is correct because the database requires full access to the operating system registry and file system to run legacy drivers, which is only supported in an IaaS model. Hosting BillingDB on Azure SQL Managed Instance is correct because it provides a fully managed PaaS environment that eliminates operating system patching while supporting cross-database queries and SQL Server Agent.
Adım Adım Çözüm
Anahtar Kavram
Understanding the feature support and management boundaries of different Azure SQL deployment options (Azure SQL Database, Azure SQL Managed Instance, and SQL Server on Azure VMs) is critical to matching legacy requirements with the appropriate service tier.