A dew-pond gauge team proposes Azure Cache for Redis “because we need configuration.” Which service selection matches AZ-204 for app configuration and secrets?
Select an answer to reveal the explanation.
Short Explanation
Need config? App Configuration and Key Vault—not Redis, not Insights-as-a-settings-file. Redis is a great cache elsewhere, but it is not this exam’s configuration skill.
Full Explanation
AZ-204's January 14, 2026 skills for application configuration and secrets center on Azure App Configuration and Azure Key Vault. The dew-pond gauge team should keep non-secret configuration and feature flags in App Configuration and secrets in Key Vault. Azure Cache for Redis is a high-performance cache and session store elsewhere in Azure development, but it is not the exam's designated configuration-and-secrets pair for this objective.
Using Redis exclusively for secrets and Application Insights exclusively for feature flags fails both security guidance and the skill outline: Insights is telemetry, Redis is cache, and neither replaces the managed config and secret services taught here. Using Azure Front Door rules as the primary secret store fails because Front Door configures edge routing and security policies, not application connection-string custody. Storing flags and secrets only in Domain 5 Queue Storage messages fails durability, confidentiality, and domain mapping—queue messages are transient workloads, not a settings authority.
Exam caveat: Redis may still appear on AZ-204 under caching performance scenarios; do not confuse Redis-is-in-the-cloud with Redis-is-where-feature-flags-and-vault-secrets-belong. Operational check: inventory the gauge app's settings, move flags to App Configuration, move connection secrets to Key Vault, leave Redis for actual cached payloads if needed, and confirm startup no longer reads municipal secrets from a cache key or a checked-in file.