DVA-C02 Deployment Practice Question
A developer is using AWS CodeBuild to compile and package a Java application. The build process takes longer than expected. The developer wants to speed up the build by reusing dependencies that have not changed between builds. Which feature should the developer enable?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Enable caching for the CodeBuild project by specifying an S3 bucket for cache storage
Enable caching for the CodeBuild project by specifying an S3 bucket for cache storage. CodeBuild caching allows reusing previously downloaded dependencies, reducing build time. Option A is incorrect because running builds concurrently does not reuse dependencies across builds; it runs separate builds simultaneously. Option B is incorrect because enabling build artifacts does not affect dependency caching; artifacts are outputs. Option D is incorrect because storing artifacts in S3 does not provide caching for dependencies; it only stores the build output.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Configure the build project to run builds concurrently
Why it's wrong here
Running builds concurrently does not reuse any cached dependencies because each build runs in an isolated, fresh container or virtual machine. CodeBuild's concurrency setting only controls how many independent builds can run in parallel, so every build still downloads the same dependencies from scratch. This may improve overall throughput for multiple teams but does nothing to speed up a single build's compile or package phase. Therefore, it does not address the requirement to reuse unchanged dependencies.
- ✗
Enable build artifacts in the CodeBuild project
Why it's wrong here
Enabling build artifacts in the CodeBuild project defines where the successfully built output (such as compiled code or packaged archives) is uploaded, but artifacts are the final product, not the intermediate dependency files used during the build. Dependencies like Maven, pip, or npm packages are consumed before artifacts are produced, so configuring artifact storage has no effect on how those dependencies are resolved or cached. Artifacts are also typically uploaded only on success, whereas dependency caching needs to happen before the build steps run. Thus, this setting cannot help reuse dependencies across builds.
- ✓
Enable caching for the CodeBuild project by specifying an S3 bucket for cache storage
Why this is correct
Enabling caching for the CodeBuild project by specifying an S3 bucket for cache storage is the intended solution: CodeBuild downloads a cache archive from the given S3 bucket before the build and uploads it again afterward. This lets package managers like Maven, Gradle, npm, or pip reuse previously downloaded dependencies, dramatically reducing build time and network traffic for untouched dependencies. You can configure cache paths in the buildspec to collect and restore the correct directories. This is the standard, documented way to cache dependencies in CodeBuild.
- ✗
Store the build's output artifacts in an S3 bucket
Why it's wrong here
Storing the build's output artifacts in an S3 bucket is for saving the final deliverables for deployment or auditing, not for preserving dependency state between builds. Each new build starts from an environment that has no access to those output artifacts, and the build process would still need to re-resolve all dependencies from their remote repositories. This option confuses artifact storage with cache storage; artifacts are produced by the build, while a cache is consumed during the build. Accordingly, it does not reuse unchanged dependencies.
Quick reference
AWS S3 Storage Class Comparison
| Storage Class | Min Duration | Retrieval | Use Case |
|---|---|---|---|
| S3 Standard | None | Immediate | Frequently accessed data |
| S3 Standard-IA | 30 days | Immediate | Infrequent access, rapid retrieval |
| S3 One Zone-IA | 30 days | Immediate | Non-critical infrequent data |
| S3 Intelligent-Tiering | None | Immediate–hours | Unknown or changing access patterns |
| S3 Glacier Instant | 90 days | Milliseconds | Archive with instant retrieval |
| S3 Glacier Flexible | 90 days | Minutes–hours | Archive, flexible retrieval |
| S3 Glacier Deep Archive | 180 days | Hours | Long-term compliance archive |
Go deeper
Related to this question
About these practice questions
Courseiva writes every DVA-C02 question from scratch — 724 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This DVA-C02 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the DVA-C02 exam.