How to Implement Selective Feature Activation in AWS Web Applications?

A developer is working on a web application that requires selective activation of specific features. The developer wants to keep the features hidden from end users until the features are ready for public access. Which solution will meet these requirements?

Create a feature flag configuration profile in AWS AppSync. Store the feature flag values in the configuration profile. Activate and deactivate feature flags as needed.
Store prerelease data in an Amazon DynamoDB table. Enable Amazon DynamoDB Streams in the table. Toggle between hidden and visible states by using DynamoDB Streams.
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. Source Reference Answer
Store prerelease data in AWS Amplify DataStore. Toggle between hidden and visible states by using Amplify DataStore cloud synchronization.

Community Votes

100%

100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.

Community Insight

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.

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.

Community Discussion (3 comments)

KarBiswa 👍 6 Selected: C

https://aws.amazon.com/blogs/mt/using-aws-appconfig-feature-flags/

albert_kuo 👍 1 Selected: C

create a Configuration Profile, then edit feature flags { "featureA": true, "featureB": false, "featureC": true }

65703c1 👍 1 Selected: C

C is the correct answer.

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

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

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.

Related Analysis

Practice All DVA-C02 Questions

Access 100 questions with complete answers and detailed explanations.

View Full DVA-C02 Practice Test →

← Back to DVA-C02 Study Guide