Examkin

Soru

Zorluk: Çok zorRelational Data Storage Solutions

A multinational retail chain is transitioning its legacy supply chain management platform to Microsoft Azure. The current platform relies on a SQL Server environment hosting three interconnected databases. These databases execute frequent cross-database updates using three-part object names (e.g., querying 'InventoryDB.dbo.Stock' from the 'SalesDB' database). Additionally, the system runs native SQL Server Agent jobs for nightly inventory reconciliation.

The target Azure architecture must satisfy the following constraints:
- Maintain native support for SQL Server Agent and three-part naming without refactoring the application code.
- Eliminate host operating system maintenance, engine patching, and database backup infrastructure management.
- Deliver sub-millisecond write latency specifically for database transaction logs to support high-throughput checkout events.
- Provide a read-only endpoint replica to offload heavy reporting queries from the primary transactional node.
- Protect all automated database backups against the loss of a primary datacenter.

Which Azure SQL deployment option should you recommend?

  1. Azure SQL Managed Instance (Business Critical tier)Cevap
  2. B
    Azure SQL Database (Single Database, Business Critical tier)
  3. C
    Azure SQL Managed Instance (General Purpose tier) configured with Locally Redundant Storage (LRS)
  4. D
    SQL Server on Azure Virtual Machines configured with Standard HDD storage for database transaction logs

Cevap

Azure SQL Managed Instance (Business Critical tier)
Azure SQL Managed Instance (Business Critical tier) is the ideal solution because it is a fully managed Platform as a Service (PaaS) offering that minimizes OS administration and database backup overhead. It provides full compatibility with SQL Server instance-level features, enabling native SQL Server Agent jobs and cross-database queries using three-part naming conventions. The Business Critical tier uses local SSD storage to ensure sub-millisecond write latencies for transaction logs, includes a built-in read-only replica for read-scale out, and supports geo-redundant or zone-redundant storage for backups to survive regional outages.

Adım Adım Çözüm

1
Analyze the application architectural and compatibility requirements.
The requirement for SQL Server Agent and native cross-database queries using three-part naming identifies that the destination database service must support instance-scoped features.
Azure SQL Database Single Database and Elastic Pools do not natively support these features, pointing towards either Azure SQL Managed Instance or SQL Server on Azure VMs.
2
Evaluate the management and administrative overhead constraint.
The requirement to minimize ongoing administrative overhead (such as patching and backups) dictates choosing a Platform as a Service (PaaS) solution.
SQL Server on Azure VMs is an Infrastructure as a Service (IaaS) solution, which places the burden of OS updates, database patching, and backups on the administrator. This leaves Azure SQL Managed Instance as the remaining candidate.
3
Evaluate storage latency, read-scale out, and redundancy requirements.
Sub-millisecond log write latency, native read-scale out, and datacenter-outage resilience point to the Business Critical tier of SQL Managed Instance configured with geo-redundant or zone-redundant storage.
The General Purpose tier does not support read-scale out and utilizes remote storage, which does not guarantee the required sub-millisecond log write performance. Backups must be configured with GRS or ZRS rather than LRS to survive a datacenter outage.

Anahtar Kavram

Selecting the appropriate Azure SQL deployment option and tier based on feature compatibility, management overhead, performance, and disaster recovery requirements.
Bu soruyu puanla

Konular

Relational Data Storage Solutions

Bu konudan daha fazla soru