Which Azure databases meet zone redundancy for these App Service apps?
DRAG DROP
You have an Azure subscription.
You are designing a deployment plan for the Azure App Service web apps shown in the following table.
You need to recommend a database solution for the apps. The solution must meet the following requirements:
• Provide zone redundancy.
• Minimize costs and administrative effort.
What should you include in the recommendation for each app? To answer, drag the appropriate database types to the correct apps. Each database type may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
Community Insight
The item tests PaaS database selection under zone redundancy and least administrative effort; the trap is defaulting every SQL Server workload to Azure SQL Database or choosing IaaS for full compatibility.
This AZ-305 drag-and-drop asks you to match each App Service web app's database engine and workload needs to a zone-redundant Azure PaaS database while minimizing cost and administrative effort. The correct mapping uses Azure SQL Managed Instance for the SQL Server app, Cosmos DB for MongoDB, and Azure Database for MySQL Flexible Server for MySQL.
Picking SQL Server on Azure VMs for SQL compatibility or Cosmos DB for every workload; VMs add patching and HA overhead, and Cosmos DB is not a relational MySQL replacement.
Community Discussion (1 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The SQL Server-targeted app needs Azure SQL Managed Instance because Managed Instance provides near-full SQL Server compatibility, including instance-scoped features such as cross-database queries and SQL Agent that Azure SQL Database does not fully cover. Managed Instance is still PaaS and can be deployed zone-redundant, so it satisfies both availability and low administrative effort. The MongoDB app maps to Azure Cosmos DB's API for MongoDB, a zone-redundant, globally distributable PaaS service that avoids running MongoDB on VMs. The MySQL app maps to Azure Database for MySQL Flexible Server, which supports zone redundancy in supported regions and removes OS and database patching. This combination satisfies the stated zone-redundancy requirement with the least management overhead among compatible services.Why Other Candidate Answers Are Wrong
Azure SQL Database is cheaper, but it is the wrong fit for the SQL Server app when the table requires instance-level features such as cross-database queries; those features drive the answer to Managed Instance. SQL Server on Azure VMs would provide full compatibility, but it violates the minimize-administrative-effort requirement and usually increases cost. Self-managed MongoDB or MySQL on IaaS also adds patching, backup, and HA design work. Cosmos DB is not a fit for the MySQL relational app, and Azure Database for MySQL is not a fit for the MongoDB document workload.Community Comment Notes
gpais flagged an availability-SLA point, noting the scenario "says more than 99.995% availabitly" and that Cosmos DB multi-region reaches 99.999%, linking to the Cosmos DB overview. That supports choosing a zone-redundant, multi-region-capable PaaS service for the MongoDB workload rather than a single-region VM database. The practical takeaway is to read the table's workload-specific constraints, not just the generic zone-redundancy line, before defaulting to the cheapest SQL option.Official Reference
Exam Strategy
Read the table row by row and let the database engine plus any instance-level SQL Server requirement drive the choice before applying cost and admin-effort filters. Do not choose IaaS just because it offers full compatibility; AZ-305 usually rewards the managed PaaS option that still meets the feature constraint.
Frequently Asked Questions
Why is Azure SQL Managed Instance chosen instead of Azure SQL Database for the SQL Server app?
The SQL Server workload needs instance-level compatibility such as cross-database queries, which Azure SQL Database does not support; Managed Instance stays PaaS and can be zone-redundant.
Does Azure Database for MySQL support zone redundancy for the MySQL app?
Yes, Azure Database for MySQL Flexible Server supports zone redundancy in supported regions, meeting the requirement without IaaS management.
Related Analysis
Practice All AZ-305 Questions
Access 95 questions with complete answers and detailed explanations.
View Full AZ-305 Practice Test →