A zinc-roof workshop wants one configuration client in the app, but DbPassword must remain a vault secret. What App Configuration pattern meets that goal?
Select an answer to reveal the explanation.
Short Explanation
One config client, two stores: put a Key Vault reference in App Configuration for DbPassword. The app still needs vault get-secret rights through its identity—the reference is a pointer, not a plaintext copy.
Full Explanation
App Configuration can store Key Vault references so applications use a single configuration provider while secret values remain in Key Vault. The app’s managed identity (or other credential) must still be authorized to get the secret. Copying the password into App Configuration or into the image defeats vault centralization.