An organization is evaluating database migration options and new application deployments in Microsoft Azure. How should the organization match each application workload requirement to the most appropriate Azure database service?
- An application requiring a globally distributed NoSQL database that can scale throughput and storage across multiple regions with multi-model API support.Azure Cosmos DB
- An enterprise application requiring a fully managed relational database with built-in high availability, built on the Microsoft SQL Server engine without operating system-level control.Azure SQL Database
- A legacy SQL Server database migration requiring host-level operating system access to run custom third-party database agents and shared disk configurations.SQL Server on Azure Virtual Machines
- An open-source web application stack requiring a fully managed relational database engine compatible with schema-based PostgreSQL queries.Azure Database for PostgreSQL
Answer
The correct pairings match Azure Cosmos DB with the globally distributed NoSQL workload, Azure SQL Database with the fully managed relational SQL Server workload without OS access, SQL Server on Azure Virtual Machines with the legacy SQL Server workload requiring OS access, and Azure Database for PostgreSQL with the open-source PostgreSQL workload.
The pairings are correct because Azure Cosmos DB provides globally distributed NoSQL capabilities. Azure SQL Database provides a managed PaaS experience for SQL Server relational databases. SQL Server on Azure Virtual Machines provides full OS access under the IaaS model. Azure Database for PostgreSQL provides a managed database service for open-source PostgreSQL workloads.
Step-by-Step Solution
Key Concept
Selecting appropriate Azure database services based on relational vs. non-relational, PaaS vs. IaaS, and engine requirements.
Estimated Time:1m 30s