Develop Azure compute solutions →mediumMultiple ChoiceObjective-mapped

AZ-204 Develop Azure compute solutions Practice Question

Exhibit

Refer to the exhibit.

{
  "type": "Microsoft.Web/sites/config",
  "apiVersion": "2022-09-01",
  "name": "appsettings",
  "properties": {
    "WEBSITE_RUN_FROM_PACKAGE": "1",
    "APPINSIGHTS_INSTRUMENTATIONKEY": "<key>",
    "MyApp:Setting1": "Value1"
  }
}

You are deploying an Azure App Service using an ARM template. After deployment, you find that the application settings are not applied. What is the most likely issue?

⚠ Common exam trap

The trap here is that candidates often focus on syntax errors (like colons or resource types) rather than the implicit deployment ordering requirement, missing that the 'dependsOn' property is mandatory for child resources to ensure they are applied after the parent site exists.

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

✓

The resource is missing a dependsOn property for the parent site

When deploying application settings via an ARM template, the 'Microsoft.Web/sites/config' resource (which contains the appsettings) must have a 'dependsOn' property referencing the parent 'Microsoft.Web/sites' resource. Without this dependency, Azure Resource Manager may attempt to apply the settings before the site exists, causing the settings to be silently ignored or not applied. This is a common deployment ordering issue.

Answer analysis

Option-by-option breakdown

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

✓
The resource is missing a dependsOn property for the parent site
Why this is correct
When deploying nested resources like application settings (Microsoft.Web/sites/config) for an Azure App Service, it is crucial to explicitly define a dependency on the parent Microsoft.Web/sites resource. Without the dependsOn property, Azure Resource Manager (ARM) might attempt to deploy the child configuration resource before the parent App Service instance has been fully provisioned and is ready to accept configuration changes. This can lead to deployment failures, as the target parent resource for the settings would not yet exist or be in a stable state.
✗
The resource type should be 'Microsoft.Web/sites/appsettings'
Why it's wrong here
The correct resource type for managing application settings within an Azure App Service is 'Microsoft.Web/sites/config'. While 'appsettings' is the specific configuration section being targeted, it is not part of the resource type itself. Instead, 'appsettings' is specified as the 'name' property of the 'Microsoft.Web/sites/config' resource, indicating that this particular configuration resource manages the application settings for the parent web app.
✗
The apiVersion is outdated, use '2021-02-01'
Why it's wrong here
The apiVersion '2022-09-01' is a perfectly valid and relatively recent API version for Microsoft.Web resources. Azure frequently releases new API versions to introduce features or improvements, but older, stable versions remain supported for extended periods. There is no requirement to use the absolute latest API version unless specific new features are needed, and '2022-09-01' would successfully deploy the resource.
✗
The property 'MyApp:Setting1' uses a colon, which is not allowed
Why it's wrong here
Colons (:) are indeed allowed and commonly used within Azure App Service application setting keys. This syntax is often leveraged to represent hierarchical or nested configuration structures, especially when integrating with frameworks like ASP.NET Core, which interpret colons as delimiters for configuration sections. Therefore, a setting key such as 'MyApp:Setting1' is perfectly valid and will be correctly processed by the App Service.

Go deeper

AZ-204 Develop Azure compute solutions Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question