A quaking-bog path API uses the Azure SDK on a developer laptop (interactive login) and in Azure (managed identity) without #if AZURE secret forks. Which credential pattern supports that?
Select an answer to reveal the explanation.
Short Explanation
DefaultAzureCredential is the Swiss Army knife: Visual Studio or az login on the laptop, managed identity in Azure, one code path. No #if AZURE secret spaghetti and no password in App Configuration.
Full Explanation
DefaultAzureCredential tries a documented chain of credential sources, enabling the same application code to authenticate via developer tooling locally and via managed identity in Azure. Hard-coded client secrets, developer passwords in configuration, and storage shared-key credentials are not the preferred cross-environment Entra ID pattern for Key Vault and similar data planes.