Question 16 — AZ-104 Case Study Set
Given that Paideffort requires passwords and secrets to remain protected from deployment history, which change should be made to the adminSecret parameter? (Select one answer)
Change its type to
secureStringand remove the default secret value.Change its type to
objectand retain the existing default secret value.Move the secret into the variables section and continue using a string value.
Move the secret into the outputs section so downstream stages can retrieve it.
Correct answers
Change its type to
secureStringand remove the default secret value.
Explanations
Correct Answer:
Change its type to secureString and remove the default secret value.
Explanation:
Paideffort requires deployment secrets to remain protected and not be hardcoded. A password or secret should use secureString, and sensitive values should not have hardcoded defaults. Secure parameter values cannot be read or harvested from deployment history in the same way as ordinary string parameters.
Wrong Answers:
Change its type to object and retain the existing default secret value.
An ordinary object is not the secure type intended for confidential structured data, and retaining a hardcoded secret would still violate Paideffort's security requirement.
Move the secret into the variables section and continue using a string value.
Variables do not provide the protection required for sensitive deployment input. The secret would also remain embedded in the template definition.
Move the secret into the outputs section so downstream stages can retrieve it.
Returning the secret as an output would expose a confidential value rather than protecting it. Outputs should not be used to disclose Paideffort's administrator secret.