An organization is planning to migrate and build new database workloads in Azure. You need to match each architectural requirement to the appropriate Azure database service.
To answer, match the requirement on the left to the correct Azure database service on the right.
- Migrate an on-premises SQL Server database that requires SQL Server Agent and cross-database queries with minimal code changes.Azure SQL Managed Instance
- Deploy a globally distributed, non-relational database for semi-structured data with guaranteed single-digit millisecond read/write latency.Azure Cosmos DB
- Run an open-source relational workload while ensuring that OS patching, backups, and high availability are managed by Azure.Azure Database for PostgreSQL
- Implement a relational database that automatically scales compute resources based on workload demand and pauses during inactive periods.Azure SQL Database
Answer
The requirement for SQL Server Agent and cross-database queries matches Azure SQL Managed Instance. The requirement for a globally distributed, non-relational database with single-digit millisecond latency matches Azure Cosmos DB. The requirement for an open-source relational workload with managed patching matches Azure Database for PostgreSQL. The requirement for a relational database with automatic compute scaling and pausing matches Azure SQL Database.
Matching the workloads requires mapping specific database capabilities to the appropriate Azure service. The requirement for SQL Server Agent and cross-database queries matches Azure SQL Managed Instance. The requirement for a globally distributed, non-relational database with single-digit millisecond latency matches Azure Cosmos DB. The requirement for an open-source relational workload with managed patching matches Azure Database for PostgreSQL. The requirement for a relational database with automatic compute scaling and pausing matches Azure SQL Database.
Step-by-Step Solution
Key Concept
Azure Database Services (Relational, Non-Relational, and Cosmos DB)