Question 12 — AZ-104 Case Study Set
Review the pipeline commands used by Paideffort.
- name: Deploy platform
run: |
az group deployment create \
--resource-group $RESOURCE_GROUP \
--template-file ./infra/main.json
az storage account create \
--resource-group $RESOURCE_GROUP \
--name $ARTIFACT_STORAGE \
--location $LOCATION
az functionapp create \
--resource-group $RESOURCE_GROUP \
--name $FUNCTION_APP \
--storage-account $ARTIFACT_STORAGE
Which two changes best address Paideffort's stated deployment objectives? (Select two answers)
Replace
az group deployment createwith the recommendedaz deployment group createcommand.Declare the storage and function resources in ARM-based infrastructure definitions rather than provisioning them through separate service-specific commands.
Remove the ARM deployment and retain only the storage and function CLI commands because imperative deployment improves traceability.
Move the storage and function commands into separate manual administrator procedures so the pipeline contains fewer commands.
Correct answers
Replace
az group deployment createwith the recommendedaz deployment group createcommand.Declare the storage and function resources in ARM-based infrastructure definitions rather than provisioning them through separate service-specific commands.
Explanations
Correct Answer:
Replace az group deployment create with the recommended az deployment group create command.
Declare the storage and function resources in ARM-based infrastructure definitions rather than provisioning them through separate service-specific commands.
Explanation:
Paideffort wants a supported resource-group deployment command and wants Resource Manager to coordinate infrastructure creation. The newer az deployment group create command satisfies the first requirement. Moving additional infrastructure into declarative templates reduces the sequence of individual provisioning calls and allows Resource Manager to manage deployment ordering and parallelism where possible.
Wrong Answers:
Remove the ARM deployment and retain only the storage and function CLI commands because imperative deployment improves traceability.
Paideffort is moving toward infrastructure as code precisely to improve configuration consistency, traceability, and repeatability. Replacing the template with imperative provisioning would work against those objectives.
Move the storage and function commands into separate manual administrator procedures so the pipeline contains fewer commands.
This would decrease automation while introducing infrastructure changes that are not consistently represented in the version-controlled deployment definition.