How to access AWS AppConfig data in Lambda with least effort?
A developer built an application by using multiple AWS Lambda functions. The Lambda functions must access dynamic configuration data at runtime. The data is maintained as a 6 KB JSON document in AWS AppConfig. The configuration data needs to be updated without requiring the redeployment of the application. The developer needs a solution that will give the Lambda functions access to the dynamic configuration data. What should the developer do to meet these requirements with the LEAST development effort?
Community Votes
100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The question tests knowledge of Lambda extensions versus manual API calls or environment variables, with the trap being the 4 KB size limit on environment variables.
To access dynamic configuration in AWS Lambda with minimal code, developers should use the AWS AppConfig Agent Lambda extension. This approach allows runtime updates without redeployment and handles the retrieval logic automatically.
Choosing environment variables (Option A) is a common mistake because the 6 KB configuration exceeds the Lambda environment variable limit of 4 KB.
Community Discussion (4 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The AWS AppConfig Agent Lambda extension is designed specifically to provide local access to configuration data via localhost. It runs as a sidecar process that fetches and caches the configuration, allowing the function to read it without writing custom API logic, thus minimizing development effort.Why the Other Options Are Wrong
Option A is incorrect because Lambda environment variables are limited to 4 KB, which is insufficient for the 6 KB JSON document. Option C is incorrect because the AWS X-Ray SDK is used for tracing and debugging, not for retrieving configuration data; using the standard SDK would require more code than the extension. Option D is incorrect because including the file in the deployment package necessitates redeploying the function whenever the configuration changes.Community Comment Notes
Community members confirmed that Option B is the intended solution for AppConfig integration with Lambda. One comment explicitly pointed out the 4 KB size limit of environment variables as the disqualifying factor for Option A.Official Reference
Exam Strategy
Always verify Lambda environment variable size limits (4 KB) when configuration data is mentioned. For dynamic configuration updates without redeployment, prioritize Lambda extensions over direct API calls or packaging files.
Related Analysis
Practice All DVA-C02 Questions
Access 100 questions with complete answers and detailed explanations.
View Full DVA-C02 Practice Test →