A .NET application must read 50 different secrets from Key Vault at startup. What caching strategy reduces calls?

1. A Fetch all 50 secrets on every request
2. B Use the SecretClient with built-in caching; fetch once at startup and cache in memory with TTL
3. C Store secrets in a local file at deployment
4. ✓ D Use Azure App Configuration with Key Vault references for cached reads (correct answer)

Shortcut: Azure App Configuration with Key Vault references caches resolved secrets and refreshes them on a configurable interval, reducing Key Vault call volume significantly compared to direct fetching on each request.