A bluff-erosion pin API uses the same App Configuration key ApiUrl for test and production. How should environments stay separated without overwriting each other?
Select an answer to reveal the explanation.
Short Explanation
Same key, different worlds: labels (or another store) keep test and prod ApiUrl apart. Overwriting one shared value is how yesterday’s test URL sneaks into production.
Full Explanation
App Configuration labels provide a dimension for the same key across environments, so ApiUrl can differ for test and production without collisions. Overwriting a single unlabeled value risks cross-environment bleed. Application Insights and Service Bus are not substitutes for environment-scoped application configuration.