Azure App Configuration

Practice questions

1. Question 1Q-423392

   An Azure App Service uses a system-assigned managed identity to read configuration values from Azure App Configuration. The application must not modify key-values or manage the App Configuration resource. Which Azure role should be assigned to the identity?

   1. A.App Configuration Data Reader
   2. B.App Configuration Data Owner
   3. C.Contributor
   4. D.Reader
   See the answer and solution
2. Question 2Q-A7ED65

   An ASP.NET Core application uses Azure App Configuration for application settings. A database password must not be stored as a plain value in App Configuration. Which design securely allows the application to retrieve the password at runtime?

   1. A.Store the password directly in App Configuration and grant the application App Configuration Data Owner.
   2. B.Store the password in Azure Key Vault, store a Key Vault reference in App Configuration, and grant the application's managed identity permission to read the secret.
   3. C.Encrypt the password with a customer-managed key and store the encrypted value in an App Configuration label.
   4. D.Store the password in an App Configuration feature flag and restrict access using a read-only connection string.
   See the answer and solution
3. Question 3Q-5F6092

   An ASP.NET Core application loads settings from Azure App Configuration. The team wants changes to take effect without restarting the application, but only after the key Settings:Sentinel changes. Refresh checks must occur at most once every five minutes during incoming requests. Which implementation satisfies these requirements?

   1. A.builder.Configuration.AddAzureAppConfiguration(options => { options.Connect(new Uri(endpoint), new DefaultAzureCredential()).ConfigureRefresh(refresh => refresh.Register("Settings:Sentinel", refreshAll: true).SetRefreshInterval(TimeSpan.FromMinutes(5))); }); app.UseAzureAppConfiguration();
   2. B.builder.Configuration.AddAzureAppConfiguration(options => { options.Connect(new Uri(endpoint), new DefaultAzureCredential()).ConfigureRefresh(refresh => refresh.Register("Settings:Sentinel", refreshAll: false)); }); app.UseAzureAppConfiguration();
   3. C.builder.Configuration.AddAzureAppConfiguration(options => { options.Connect(new Uri(endpoint), new DefaultAzureCredential()).ConfigureRefresh(refresh => refresh.Register("Settings:Sentinel", refreshAll: true).SetRefreshInterval(TimeSpan.Zero)); });
   4. D.builder.Configuration.AddAzureAppConfiguration(options => { options.Connect(new Uri(endpoint), new DefaultAzureCredential()); }); app.UseAzureAppConfiguration();
   See the answer and solution
4. Question 4Q-B94F88

   An ASP.NET Core application stores Api:BaseUrl in Azure App Configuration with separate Production and Staging labels. The production deployment must load only the Production value for keys under Api:. Which provider configuration should be used?

   1. A.options.Select("Api:*", "Production")
   2. B.options.Select("Api:*", LabelFilter.Null)
   3. C.options.Select("Production", "Api:*")
   4. D.options.Select("Api:*")
   See the answer and solution
5. Question 5Q-FE2BE0

   An ASP.NET Core application uses Azure App Configuration feature flags. The team wants to evaluate flags through IFeatureManager in application code. Which setup is required?

   1. A.Call UseFeatureFlags() on the App Configuration provider and register feature management with AddFeatureManagement().
   2. B.Store each feature flag as a connection string and register it with AddDbContext().
   3. C.Call UseKeyVault() and register IConfiguration as a singleton.
   4. D.Enable Azure App Service deployment slots and register AddFeatureManagement() only.
   See the answer and solution