How to Implement Selective Feature Activation in AWS Web Applications?
Short answer
C Create a feature flag configuration profile in AWS AppConfig. Store the feature flag values in the configuration profile. Activate and deactivate feature flags as needed.
Question
Key Takeaways
Tests knowledge of AWS-native configuration management versus custom database solutions, with the common trap being confusion between API, sync, and configuration services.
AWS AppConfig provides native feature flag management for dynamic application control without redeployment. The developer community unanimously confirms that AppConfig configuration profiles are the standard solution for hiding and selectively enabling features.
Common mistake: Option A (AppSync) is frequently selected due to its API focus, but it lacks built-in feature flag deployment and rollout strategies compared to AppConfig.
Expert Analysis
Why the Answer Is Correct
AWS AppConfig is purpose-built for managing application configurations and feature flags securely across environments. By creating a configuration profile, developers can store JSON-based feature flags and deploy them to applications via hosted configurations, allowing instant toggling without code changes. This directly satisfies the requirement for selective activation and controlled visibility.
Why the Other Options Are Wrong
AppSync focuses on real-time APIs and GraphQL subscriptions, not centralized configuration management. DynamoDB Streams are designed for change data capture and event-driven architectures, making them overly complex and inefficient for simple feature toggles. Amplify DataStore handles offline-first synchronization and local caching, which does not address centralized feature flag orchestration.
Community Comment Notes
Multiple users confirmed C as correct, citing official AWS blogs that detail AppConfig feature flag workflows. Comment [1] specifically links to the AWS documentation demonstrating how to structure JSON feature flags within an AppConfig profile, while Comment [2] emphasizes the simplicity of editing values directly in the console or API.
Official Reference
- https://aws.amazon.com/blogs/mt/using-aws-appconfig-feature-flags/
- https://docs.aws.amazon.com/appconfig/latest/userguide/appconfig-introduction.html
These links open the official vendor documentation in a new tab.
Exam Strategy
When a scenario mentions dynamic feature toggles, gradual rollouts, or configuration management without redeployment, immediately select AWS AppConfig. Avoid overcomplicating questions with database streams or frontend sync tools unless they explicitly mention offline capabilities or real-time subscriptions.
Community Votes
100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 3 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 3
-
KarBiswa 👍 6 Answered Chttps://aws.amazon.com/blogs/mt/using-aws-appconfig-feature-flags/
-
albert_kuo 👍 1 Answered Ccreate a Configuration Profile, then edit feature flags { "featureA": true, "featureB": false, "featureC": true }
-
65703c1 👍 1 Answered CC is the correct answer.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All DVA-C02 Questions
Access 100 questions with complete answers and detailed explanations.
View Full DVA-C02 Practice Test →