Question 90
The cloud operations team reviews the following risk: An Azure Container App needs to read a protected secret but its outbound code uses an expired service principal secret rather than a platform credential. Which explanation fits the observed symptoms most closely?
Explanation
Correct Answer
The described technical condition is: The Container App does not use an attached managed identity with the correct Key Vault data-plane permission. The appropriate corrective action is: Attach a supported managed identity and grant the intended Key Vault secret-read role. Confirm with: The app retrieves secrets via its identity and remains operational after the old client secret is revoked.
Incorrect Answers
Sensitive credentials are stored in ordinary configuration instead of supported Container Apps secrets or identity. “Configure a secure Container Apps secret reference or managed identity for database access” would address that alternative cause, not the condition in this question: the Container App does not use an attached managed identity with the correct Key Vault data-plane permission.
“Use secure value handling or managed identity based authentication for the containerized application” responds to this separate finding: sensitive values are placed in plain configuration rather than secure parameters or supported protected secret references. This question instead needs “Attach a supported managed identity and grant the intended Key Vault secret-read role”, so the alternative does not meet the stated condition.
The cluster's public API server authorized IP ranges were not configured for restricted administrative access. “Configure approved API server authorized IP ranges or move to private control-plane access” applies to that separate problem. The observed case is an Azure Container App needs to read a protected secret but its outbound code uses an expired service principal secret rather than a platform credential; choosing this alternative would address the wrong failure mode.