Storing secrets in Azure - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use Azure Key Vault for storing secrets?

Which of the following is the main reason to use Azure Key Vault for storing secrets instead of storing them directly in application code?

A It allows anyone in the organization to read secrets without restrictions.

B It automatically writes secrets into application code for faster access.

C It stores secrets in plain text for easy debugging.

D It encrypts secrets and controls access centrally, reducing risk of exposure.

💡 Hint

Think about security and access control for sensitive information.

Azure Key Vault encrypts secrets and provides centralized access control, which helps protect sensitive data better than embedding secrets in code.

❓ Configuration

intermediate

Accessing a secret from Azure Key Vault using Managed Identity

You want an Azure Virtual Machine to access a secret from Azure Key Vault without storing credentials in code. Which configuration allows this?

A Assign a Managed Identity to the VM and grant it 'Get' permission on the Key Vault access policy.

B Store the Key Vault access key in the VM's environment variables.

C Enable public access on the Key Vault so the VM can read secrets anonymously.

D Create a user account and hardcode its password in the VM application.

💡 Hint

Think about how Azure services can authenticate securely without passwords.

Managed Identity lets the VM authenticate to Key Vault securely without credentials, by granting it specific permissions.

❓ Architecture

advanced

Designing secret rotation with Azure Key Vault

You need to design a system where application secrets rotate automatically every 30 days without downtime. Which architecture best supports this?

A Use Azure Key Vault with versioned secrets and configure the application to fetch the latest version at startup and periodically.

B Manually update secrets in the application code every 30 days and redeploy the app.

C Store secrets in a database and update them without notifying the application.

D Disable secret rotation to avoid application failures.

💡 Hint

Consider how to update secrets without stopping the application.

Azure Key Vault supports secret versioning. Applications can retrieve the latest secret version dynamically, enabling smooth rotation.

❓ security

advanced

Preventing unauthorized access to Azure Key Vault secrets

Which of the following configurations best prevents unauthorized users from accessing secrets in Azure Key Vault?

A Disable logging to hide access attempts and avoid alerts.

B Allow all IP addresses to access the Key Vault and assign all users the 'Reader' role.

C Enable firewall rules to restrict network access and use Azure RBAC to assign minimum required permissions.

D Share Key Vault access keys via email to trusted users.

💡 Hint

Think about limiting who and where can access the Key Vault.

Restricting network access and using role-based access control limits exposure and enforces least privilege.

❓ service_behavior

expert

Behavior of Azure Key Vault when a secret is deleted

What happens to a secret in Azure Key Vault immediately after it is deleted, assuming soft-delete is enabled?

A The secret is copied to a backup vault automatically.

B The secret is marked as deleted but remains recoverable for a retention period before permanent removal.

C The secret is archived and accessible only by administrators indefinitely.

D The secret is permanently removed instantly and cannot be recovered.

💡 Hint

Consider Azure Key Vault's soft-delete feature behavior.

With soft-delete enabled, deleted secrets remain recoverable for a configurable retention period before permanent deletion.