Develop Azure compute solutions →hardMultiple ChoiceObjective-mapped

AZ-204 Develop Azure compute solutions Practice Question

Exhibit

Refer to the exhibit.

```json
{
  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
  "contentVersion": "1.0.0.0",
  "parameters": {
    "webAppName": {
      "type": "string",
      "defaultValue": "myWebApp"
    }
  },
  "resources": [
    {
      "type": "Microsoft.Web/sites",
      "apiVersion": "2022-09-01",
      "name": "[parameters('webAppName')]",
      "location": "[resourceGroup().location]",
      "properties": {
        "siteConfig": {
          "appSettings": [
            {
              "name": "WEBSITE_RUN_FROM_PACKAGE",
              "value": "1"
            }
          ]
        }
      }
    }
  ]
}
```

You deploy the above ARM template. Later, you update the web app's code by deploying a new ZIP package to Azure Blob Storage and updating the WEBSITE_RUN_FROM_PACKAGE setting with the new package URL. However, the web app continues to run the old code. What is the most likely cause?

⚠ Common exam trap

Test-takers frequently assume setting the value to '1' is a generic 'enable' flag, not realizing it has a specific meaning (local package) and that external packages require the full URL as the setting value.

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 value '1' indicates the package is from local storage, not an external URL.

When the WEBSITE_RUN_FROM_PACKAGE app setting is set to '1', it tells Azure App Service to use a local package stored in the site's wwwroot folder. To use an external package from Azure Blob Storage, the setting must be set to the full URL of the blob (with a SAS token if private). Keeping the value as '1' means the service ignores the new blob URL and continues to run the old local package.

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 app setting name is misspelled. It should be 'WEBSITE_RUN_FROM_ZIP'.
Why it's wrong here
The question implies an issue with deploying a web app package. The setting 'WEBSITE_RUN_FROM_ZIP' was an older, deprecated method for running an app directly from a zip file. The current and recommended setting for running an app from a package, whether local or external, is 'WEBSITE_RUN_FROM_PACKAGE'. Therefore, suggesting 'WEBSITE_RUN_FROM_ZIP' as the correct name is inaccurate for modern Azure App Service deployments, which primarily utilize the 'WEBSITE_RUN_FROM_PACKAGE' setting.
✗
The setting requires a value of '0' to enable external packages.
Why it's wrong here
The 'WEBSITE_RUN_FROM_PACKAGE' setting controls how an Azure App Service runs from a deployment package. A value of '0' explicitly disables this feature, meaning the application will not attempt to run directly from a package, and instead expects traditional file-based deployment. To enable running from an external package URL, the setting's value must be the URL of the package itself, not '0', which would effectively turn off the package-based deployment feature.
✗
The ARM template uses an incorrect apiVersion.
Why it's wrong here
Azure Resource Manager (ARM) templates rely on 'apiVersion' to specify the version of the resource provider API being used for resource creation or updates. While an incorrect or outdated 'apiVersion' can sometimes lead to deployment failures or unexpected behavior for resource properties, the interpretation of specific application settings like 'WEBSITE_RUN_FROM_PACKAGE' is primarily governed by the App Service runtime itself. The provided 'apiVersion' is generally valid for App Service configurations and does not directly affect how this particular application setting's value is processed.
✓
The value '1' indicates the package is from local storage, not an external URL.
Why this is correct
When 'WEBSITE_RUN_FROM_PACKAGE' is set to '1', it instructs the Azure App Service to run the application directly from a zip package that has already been deployed to the 'data/SitePackages' folder within the app's local file system. This value does not signify an external URL; rather, it points to a locally staged package. To run an application from an external URL, the value of 'WEBSITE_RUN_FROM_PACKAGE' must be the full HTTP or HTTPS URL of the zip package itself, allowing the App Service to download and mount it dynamically.

Quick reference

Azure Blob Storage Tier Comparison

Tier	Storage Cost	Retrieval Cost	Latency	Use Case
Hot	Highest	Lowest	Immediate	Active data, frequent reads
Cool	Lower	Higher	Immediate	Data accessed < once / month
Cold	Lower still	Higher	Immediate	Data accessed < once / quarter
Archive	Lowest	Highest + rehydration delay	Hours	Long-term compliance retention

Go deeper

AZ-204 Develop Azure compute solutions Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Azure Blob Storage Tier Comparison

Related to this question