Question 260
An automation service rotates an Azure Storage account key. Security requires the new key never appear in pipeline console logs or plain text configuration. Which operational design is suitable?
Explanation
Correct Answer
Azure Key Vault and comparable managed secret systems can hold sensitive storage credentials with access controlled by identity and auditable permissions. During rotation, automation should update protected secret versions and configure consumers to retrieve them securely, without printing the value to build logs or committing it to source control. Restrict who can list or regenerate storage account keys and test clients after the update. Where workloads support managed identities, removing the Shared Key dependency entirely can further reduce exposure.
Incorrect Answers
Pipeline output can be retained, forwarded or copied before anyone deletes a log. Printing a newly generated storage account key violates the secrecy requirement and creates an avoidable exposure. Keep credential values in secure secret stores and use redacted status or authentication success indicators for troubleshooting.
Azure resource tags are metadata, not a secure vault for secrets. Users who can inspect resource metadata could read the credential, and tags may be copied into inventory and billing systems. Store storage account keys in a protected secret store and avoid plaintext handling during deployment.
Publishing sensitive key material as a broadly visible deployment output can expose it to logs, history and users without a legitimate need. The requirement is protected handling and distribution, not convenient display. Use an approved secret reference and narrowly scoped access instead of emitting the credential itself.