AZ-900 Describe Azure architecture and services Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Azure SQL Database

  Why it's wrong here

  Azure SQL Database is a single database PaaS service that is designed for cloud-native applications and lacks several features found in on-premises SQL Server, such as SQL Agent and cross-database queries. Because the migration requires those features and needs minimal changes to the existing database and application, this option falls short. Additionally, Azure SQL Database does not offer native virtual network integration in the same way that Managed Instance does, making it less suitable for a straightforward migration from an existing on-premises SQL Server environment.

  When this WOULD be correct

  A company needs a fully managed, scalable relational database with built-in high availability and intelligence, but does not require SQL Server Agent, cross-database queries, or direct OS access. They want minimal administrative overhead and automatic patching.

• ✓

  Azure SQL Managed Instance

  Why this is correct

  Azure SQL Managed Instance is the correct choice because it provides full SQL Server engine compatibility, including SQL Agent and cross-database queries, which supports the vast majority of on-premises database features without requiring application redesign. It also offers native virtual network integration and automated backups, patching, and maintenance, giving the customer the same administrative simplicity as Azure SQL Database while retaining SQL Server's rich feature set. This makes it the ideal lift-and-shift target for migrating an on-premises SQL Server database.

• ✗

  SQL Server on Azure Virtual Machines

  Why it's wrong here

  SQL Server on Azure Virtual Machines provides full administrative control over the SQL Server instance and the underlying OS, but it requires the customer to handle OS patching, SQL Server updates, and other maintenance tasks, which they explicitly want to avoid. While it offers the highest level of compatibility and flexibility, that comes at the cost of significant operational overhead. Therefore, despite being a valid migration target, it does not meet the customer's requirement for reduced management responsibility.

  When this WOULD be correct

  A company needs full control over the SQL Server instance, including the OS, for custom configurations or third-party software, and is willing to manage patching and backups. They also require lift-and-shift migration with minimal changes.

• ✗

  Azure Database for SQL

  Why it's wrong here

  There is no Azure service named 'Azure Database for SQL'; the actual PaaS offerings for SQL Server are Azure SQL Database, Azure SQL Managed Instance, and SQL Server on Azure Virtual Machines. Since the customer requires a real, viable target service, this option cannot be selected. It is a common confusion with services like Azure Database for MySQL or Azure Database for PostgreSQL, which are not relevant to SQL Server migrations.

  When this WOULD be correct

  If the question asked for a fully managed, platform-as-a-service (PaaS) database service for MySQL, PostgreSQL, or MariaDB with built-in high availability and automatic patching, then Azure Database for SQL (likely a misnomer for Azure Database for MySQL/PostgreSQL) would be correct.

Option-by-option analysis

Why each answer is right or wrong

Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The AZ-900 exam frequently reuses these exact scenarios with slightly different constraints.

Analysis generated from the official AZ-900blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”

Go deeper

Related to this question