The city fees UI needs feature toggles that can roll out or roll back instantly without redeploying Lambda code. Which AWS capability best fits?
Select an answer to reveal the explanation.
Short Explanation
Feature flags should flip like a light switch, not like a full rebuild of city hall. AWS AppConfig is built for dynamic, environment-scoped configuration without shipping new Lambda code. Baking flags into zips or fiddling IAM for UI routes is the slow lane.
Full Explanation
AWS AppConfig is the DVA-C02-aligned capability for managing application configuration and feature flags across environments with controlled config deployment. For a city fees UI that must roll out or roll back toggles instantly without redeploying Lambda code, AppConfig decouples toggle state from the immutable function artifact so municipal operators can enable or disable a path quickly and safely. Instant civic feature control belongs in a configuration service, not in a new package version for every flip.
Baking toggle flags into the Lambda deployment package and redeploying for every flip fails because it couples configuration to code packaging and slows rollback. Storing toggles only in client-side localStorage and never consulting the backend fails conceptually—clients can tamper with local flags and servers lose authoritative control. Changing production IAM policies to enable or disable UI routes fails because IAM is the wrong control plane for application feature configuration.
Exam caveat: AppConfig still needs the application to fetch and honor flags; shipping AppConfig without code that reads it does not toggle UI behavior. Operational check: flip a fees UI flag in AppConfig for the test environment, confirm behavior changes without a Lambda redeploy, and verify production defaults remain safe until intentionally enabled.