A company is planning to host four new application workloads on Microsoft Azure. Each workload has specific database requirements. Which Azure database service should you select for each application workload?
- A web application that stores semi-structured catalog data using JSON documents and requires global distribution with guaranteed single-digit millisecond latency.Azure Cosmos DB
- A corporate application migrating from an on-premises Microsoft SQL Server environment that requires a fully managed relational database engine with high compatibility.Azure SQL Database
- An open-source application built using the LAMP stack (Linux, Apache, MySQL, PHP) that requires a managed relational database service in Azure.Azure Database for MySQL
- An analytics application that requires a fully managed relational database based on the PostgreSQL engine to run complex spatial queries.Azure Database for PostgreSQL
Answer
Match the web application requiring JSON documents and low latency with Azure Cosmos DB; match the corporate SQL Server migration with Azure SQL Database; match the LAMP stack application with Azure Database for MySQL; and match the PostgreSQL analytics application with Azure Database for PostgreSQL.
The correct matches correctly align the application workload requirements with their targeted Azure Database services. Relational database engines (SQL Server, MySQL, PostgreSQL) are matched to their corresponding managed PaaS offerings (Azure SQL Database, Azure Database for MySQL, Azure Database for PostgreSQL), while the non-relational JSON workload with global scaling needs is matched to Azure Cosmos DB.
Step-by-Step Solution
Key Concept
Selecting the correct Azure database service based on relational versus non-relational database types, compatibility requirements, and engine types.
Estimated Time:1m 30s