AZ-305 Design business continuity solutions Practice Question
Exhibit
{
"$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
"contentVersion": "1.0.0.0",
"parameters": {
"location": {
"type": "string",
"defaultValue": "[resourceGroup().location]"
},
"appServicePlanName": {
"type": "string"
},
"webAppName": {
"type": "string"
},
"backupStorageAccountName": {
"type": "string"
}
},
"resources": [
{
"type": "Microsoft.Web/sites/config",
"apiVersion": "2022-03-01",
"name": "[concat(parameters('webAppName'), '/backup')]",
"properties": {
"backupRequest": {
"enabled": true,
"storageAccountUrl": "[reference(resourceId('Microsoft.Storage/storageAccounts', parameters('backupStorageAccountName'))).primaryEndpoints.blob]",
"backupSchedule": {
"frequencyInterval": 1,
"frequencyUnit": "Day",
"keepAtLeastOneBackup": true,
"retentionPeriodInDays": 30
}
}
}
}
]
}Refer to the exhibit. You are deploying an ARM template to configure backup for an Azure Web App. The deployment fails with an error: 'The resource 'Microsoft.Web/sites/config' cannot be nested under a parent resource that is not deployed.' What is the MOST LIKELY cause?
⚠ Common exam trap
Many exam-takers confuse a missing parent resource with other common ARM deployment errors, such as invalid API versions or function resolution issues, rather than recognizing the specific nesting constraint error message.
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 parent web app resource is not defined in the template
The error indicates that the ARM template is trying to define a child resource (Microsoft.Web/sites/config) under a parent web app that has not been deployed within the same template. In ARM templates, nested resources require the parent resource to be defined in the same template, typically with a dependsOn element or by nesting the child resource inside the parent's resources array. Since the parent web app is missing from the template, the deployment fails because the resource manager cannot resolve the parent scope.
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 parent web app resource is not defined in the template
Why this is correct
In an ARM template, a child resource such as Microsoft.Web/sites/config/backup cannot be deployed unless its parent web app resource (Microsoft.Web/sites) is either defined in the same template or already exists in the resource group. Since the template omits the parent web app resource, Azure Resource Manager cannot resolve the resource identifier and the deployment fails with a validation error. To fix it, you must include the web app in the template and add a dependsOn relationship, or use an existing resource reference with the proper scope.
- ✗
The storageAccountUrl property uses a reference() that cannot be resolved
Why it's wrong here
The storageAccountUrl property commonly uses ARM's reference() function to retrieve the blob service endpoint or a storage key from a Microsoft.Storage/storageAccounts resource. reference() is fully resolvable when the referenced storage account is either deployed in the same template or already exists in the target resource group, so the presence of reference() does not explain the deployment failure. The claim that reference() cannot be resolved is therefore incorrect; the actual failure stems from the missing parent resource, not from an unresolvable reference.
- ✗
The apiVersion '2022-03-01' is not supported for this resource type
Why it's wrong here
For Microsoft.Web/sites/config resources, apiVersion 2022-03-01 is a valid, supported version in the Azure Web Apps REST API and can be used in the deployment of backup configuration child resources. If an unsupported API version were used, ARM would return a distinct error such as 'The apiVersion is invalid', but this is not the error observed here. Therefore, the apiVersion is not the cause of the failure.
- ✗
The backup schedule frequency interval is invalid
Why it's wrong here
The backup schedule for an Azure App Service backup uses frequencyUnit and frequencyInterval; when the unit is 'Day', a frequencyInterval of 1 is perfectly valid and falls within the accepted range. Azure's logic app backup schedule allows daily, weekly, or custom intervals, and 1 day is a common configuration. Thus, the frequency interval cannot be the reason the ARM template deployment fails.
Visual reference
Go deeper
Related to this question
About these practice questions
This AZ-305 question is part of Courseiva's 795-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-305 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-305 exam.