Recommended Configuration Management Solution for Azure App Service
Question
You are designing a configuration management solution to support five apps hosted on Azure App Service. Each app is available in the following three environments: development, test, and production.
You need to recommend a configuration management solution that meets the following requirements:
-> Supports feature flags
-> Tracks configuration changes from the past 30 days
-> Stores hierarchically structured configuration values
-> Controls access to the configurations by using role-based access control (RBAC) permissions
-> Stores shared values as key/value pairs that can be used by all the apps
Which Azure service should you recommend as the configuration management solution?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.C
The Feature Manager in the Azure portal for App Configuration provides a UI for creating and managing the feature flags that you use in your applications.
App Configuration offers the following benefits:
-> A fully managed service that can be set up in minutes
-> Flexible key representations and mappings
-> Tagging with labels
-> Point-in-time replay of settings
-> Dedicated UI for feature flag management
-> Comparison of two sets of configurations on custom-defined dimensions
Enhanced security through Azure-managed identities
-> Encryption of sensitive information at rest and in transit
-> Native integration with popular frameworks
App Configuration complements Azure Key Vault, which is used to store application secrets.
https://docs.microsoft.com/en-us/azure/azure-app-configuration/overviewThe recommended Azure service to meet the requirements described in the scenario is Azure App Configuration (Option C).
Azure App Configuration is a managed service that provides a central place to store application settings, feature flags, and other configurations that are needed by your application. It provides a way to manage configuration data in a hierarchical format that can be accessed by applications running on Azure as well as on-premises environments.
Here's how Azure App Configuration meets each requirement mentioned in the scenario:
Supports feature flags: Azure App Configuration provides a feature flags capability that can be used to gradually roll out new features to users or to enable or disable existing features.
Tracks configuration changes from the past 30 days: Azure App Configuration provides a change history feature that tracks changes to the configuration data and allows you to roll back to a previous version if needed. By default, it keeps the history of the changes made within the last 30 days.
Stores hierarchically structured configuration values: Azure App Configuration stores configuration data in a hierarchical format that makes it easy to organize and manage large amounts of configuration data.
Controls access to the configurations by using role-based access control (RBAC) permissions: Azure App Configuration allows you to control access to the configuration data using Azure Active Directory (AAD) or RBAC permissions. You can define roles and permissions to restrict access to sensitive configuration data.
Stores shared values as key/value pairs that can be used by all the apps: Azure App Configuration provides a feature called Key Vault references that allows you to reference secrets from Azure Key Vault directly in your configuration data. This ensures that the sensitive configuration data is securely stored in Azure Key Vault and is available to all your apps.
Therefore, based on the requirements mentioned in the scenario, the best choice for the configuration management solution would be Azure App Configuration (Option C).
