QuestionQ46

VerifiedSecure, monitor, troubleshoot Azure solutions

You are developing an AI API that is deployed to ACA. The API needs database credentials stored in Key Vault. Key Vault is configured to use Azure RBAC for access control.

The security team rotates the database credentials periodically. The application must always use the newest version of every credential without redeployment and without exposing secrets in code or configuration.

You need to implement a secure secret-access strategy that prevents credential exposure and retrieves the latest version of each secret at runtime without redeploying the container.

Which three actions should you perform? Each correct answer presents part of the solution.

NOTE: Each correct selection is worth one point.

Choose three
Explanation

Azure RBAC authorization requires a Key Vault RBAC role assignment, such as Key Vault Secrets User, for the workload identity; a Key Vault access policy is not the authorization model in this configuration. A system-assigned managed identity lets the containerized application authenticate to Key Vault without storing credentials. Retrieving an unversioned secret URI through the Key Vault SDK at runtime obtains the current secret version, so credential rotation does not require a container redeployment.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!