Question

Difficulty: HardRelational Data Storage Solutions

An international logistics company is designing the data tier for a new transport management platform. The platform consists of two distinct subsystems:

* The tracking subsystem requires a database that supports cross-database queries, SQL Server Agent for scheduling route calculation jobs, and Common Language Runtime (CLR) integration. The solution must minimize operational overhead.
* The invoicing subsystem requires a single database that experiences highly variable traffic patterns, including long periods of zero activity. The solution must minimize compute costs during idle periods.

Which two Azure SQL services should you recommend to support the subsystems? (Select TWO).

  1. Azure SQL Managed Instance for the tracking subsystemAnswer
  2. Azure SQL Database serverless for the invoicing subsystemAnswer
  3. C
    SQL Server on Azure Virtual Machines for the tracking subsystem
  4. D
    Azure SQL Database Elastic Pools for the invoicing subsystem
  5. E
    Azure SQL Database (single database) with provisioned compute for the tracking subsystem

Answer

Azure SQL Managed Instance for the tracking subsystem, and Azure SQL Database serverless for the invoicing subsystem
The correct recommendations are Azure SQL Managed Instance for the tracking subsystem and Azure SQL Database serverless for the invoicing subsystem. Azure SQL Managed Instance supports instances requiring SQL Server Agent, CLR integration, and cross-database queries without the administrative overhead of managing virtual machines. Azure SQL Database serverless is ideal for a single database with unpredictable traffic and idle periods because it automatically scales compute resources and pauses during inactivity to reduce compute costs to zero.

Step-by-Step Solution

1
Analyze the requirements for the tracking subsystem.
The subsystem requires legacy compatibility features including SQL Server Agent, CLR integration, and cross-database queries, but specifies that operational overhead must be minimized.
This rules out Azure SQL Database single database (which lacks SQL Agent/CLR/cross-db query support) and makes SQL Server on Azure VMs less optimal than a PaaS solution due to higher operational overhead.
2
Select the optimal database service for the tracking subsystem.
Azure SQL Managed Instance is chosen.
Managed Instance provides near 100% compatibility with the SQL Server database engine, including SQL Agent, CLR, and cross-database queries, while running as a fully managed PaaS service.
3
Analyze the requirements for the invoicing subsystem.
The subsystem consists of a single database with highly variable traffic and periods of inactivity, requiring compute costs to be minimized during idle times.
This points to a serverless model where resources auto-scale and can be paused when not in use.
4
Select the optimal database service for the invoicing subsystem.
Azure SQL Database serverless is chosen.
Azure SQL Database serverless automatically scales compute and supports auto-pausing, billing only for storage when paused, which perfectly satisfies the cost optimization requirement for a single database.

Key Concept

Azure SQL service tier selection based on feature compatibility (SQL Agent, CLR, cross-database queries) and workload auto-scaling requirements.
Rate this question