Question 25 — AZ-104 Case Study Set
Review the parameter definition used by Paideffort.
"adminSecret": {
"type": "string",
"defaultValue": "Paideffort-Temporary-2026"
}
Which change best addresses the security requirement associated with this parameter? (Select one answer)
Change the parameter to
secureStringand require the secret to be supplied without a hardcoded default.Change the parameter to
stringwith an allowedValues collection containing approved production passwords.Move the parameter value into a variable so the password no longer appears in the parameters section.
Return the parameter value through an output so deployment automation can verify the configured secret.
Correct answers
Change the parameter to
secureStringand require the secret to be supplied without a hardcoded default.
Explanations
Correct Answer:
Change the parameter to secureString and require the secret to be supplied without a hardcoded default.
Explanation:
Paideffort prohibits hardcoded credentials and requires confidential deployment values to remain protected. Using secureString and removing the default value addresses both requirements.
Wrong Answers:
Change the parameter to string with an allowedValues collection containing approved production passwords.
This would embed candidate passwords directly in the infrastructure definition and keep the value as an ordinary string, which conflicts with Paideffort's security requirements.
Move the parameter value into a variable so the password no longer appears in the parameters section.
The confidential value would still be hardcoded in the template. Moving it to another template section does not provide secure secret handling.
Return the parameter value through an output so deployment automation can verify the configured secret.
Returning the secret would unnecessarily expose confidential information and directly conflict with Paideffort's requirement to protect deployment credentials.