An ASP.NET Core app uses Azure App Configuration with 100 settings. You must ensure all configuration values remain consistent when individual settings change, support dynamic updates without restarting the app, and reduce calls to the App Configuration APIs. Which two steps help implement dynamic configuration updates?

To ensure consistency and dynamic updates while reducing API calls, you should use a sentinel key. A sentinel key is a special key updated when other configuration settings change. By registering this sentinel key and setting refreshAll to true, the application monitors only the sentinel key. When it detects a change, it refreshes all 100 settings in a single batch, ensuring consistency and reducing individual API calls. Increasing the cache expiration reduces the frequency with which the application checks App Configuration for updates, further decreasing API calls. Decreasing the cache expiration would increase API calls. Azure Key Vault is for secrets management, not for dynamic configuration updates of this nature. Registering all keys with refreshAll set to false would require individual monitoring of each key, increasing API calls and complexity. Environment variables are static and do not support dynamic updates.