Given the following ARM template snippet, what will be the value of the output named storageAccountName after deployment?
{
"outputs": {
"storageAccountName": {
"type": "string",
"value": "myStorage123"
}
}
}The output value is the value field inside the output definition.
The output named storageAccountName has a value of "myStorage123". This is what the deployment outputs.
ARM templates support several output types. Which of the following is NOT a valid output type?
Think about the basic data types ARM templates support for outputs.
ARM templates support string, int, bool, object, and securestring as output types. float is not supported.
Consider this ARM template outputs section:
{
"outputs": {
"nestedOutput": {
"type": "object",
"value": {
"name": "appService",
"id": "12345"
}
}
}
}What is the exact JSON output value for nestedOutput after deployment?
Outputs of type object return JSON objects, not strings.
The output value is a JSON object with keys name and id. It is not a string or wrapped inside another object.
You want to output a secret value from your ARM template without exposing it in deployment logs or UI. Which output type should you use?
Think about how ARM templates handle sensitive data in outputs.
The securestring output type masks the value in logs and UI, protecting secrets.
In an ARM template, an output references a property of a resource that does not exist or is misspelled. What will be the deployment output behavior?
Consider how ARM template validation works before deployment completes.
ARM template deployment fails if an output references a property that does not exist, as it is a template validation error.