Identify considerations for relational data on Azure →easyMultiple ChoiceObjective-mapped

DP-900 Practice Question: Identify considerations for relational data on Azure

Exhibit

Refer to the exhibit.

```json
{
  "properties": {
    "serverName": "myserver",
    "administratorLogin": "adminuser",
    "administratorLoginPassword": "P@ssw0rd!",
    "version": "12.0",
    "location": "eastus"
  }
}
```

Refer to the exhibit. This ARM template snippet is used to deploy which Azure resource?

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Azure SQL Database server

The ARM template snippet includes properties such as 'serverName', 'administratorLogin', and 'administratorLoginPassword', which are specific to an Azure SQL Database server deployment. Option A is incorrect because an Azure Database for MySQL server uses different properties like 'mysqlVersion' and 'storageProfile'. Option B is incorrect because Azure SQL Managed Instance requires properties like 'vCores', 'storageSizeInGB', and 'licenseType'. Option D is incorrect because Azure Synapse Analytics workspace deployments use properties like 'sqlAdministratorLogin' and 'defaultDataLakeStorage' but with different structure.

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 Database for MySQL server
Why it's wrong here
For an Azure Database for MySQL server, the ARM template uses the `Microsoft.DBforMySQL/servers` resource type, and its properties are different, including `version` (e.g., '5.7' or '8.0'), `sslEnforcement`, and a `storageProfile` object with fields like `storageMB` and `backupRetentionDays`. The snippet lacks these database-version and storage-profile properties and uses the `Microsoft.Sql/servers` schema, which is exclusive to the Azure SQL family, so MySQL is not correct.
✗
Azure SQL Managed Instance
Why it's wrong here
An Azure SQL Managed Instance is deployed using the `Microsoft.Sql/managedInstances` resource type, and its ARM template must include instance-scoped settings like `vCores`, `storageSizeInGB`, `licenseType`, and a `subnetId` because a managed instance runs as a dedicated engine inside a virtual network. The snippet only contains a logical server name and admin login, with no compute, storage, or network configuration, so this cannot be a Managed Instance template.
✓
Azure SQL Database server
Why this is correct
The ARM template snippet is a match for an Azure SQL Database logical server. The `Microsoft.Sql/servers` resource type uses exactly the properties shown: a server name, `administratorLogin`, `administratorLoginPassword`, and a location. A logical server is a management container for SQL databases and elastic pools, and this template is the standard way to provision that container before adding databases, firewall rules, or other child resources.
✗
Azure Synapse Analytics workspace
Why it's wrong here
The ARM template snippet defines a logical SQL server with properties like `administratorLogin` and `administratorLoginPassword`, which are specific to the `Microsoft.Sql/servers` resource type. In contrast, an Azure Synapse Analytics workspace is deployed using the `Microsoft.Synapse/workspaces` resource type, which requires settings such as `defaultDataLakeStorage` (to point to an Azure Data Lake Storage Gen2 account) and `sqlAdministratorLogin` at the workspace level. The absence of these Synapse-specific properties immediately rules out this option.

Go deeper

DP-900 Practice Question: Identify considerations for relational data on Azure

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question