- A
Enable retry on the build stage to automatically attempt the build again on failure.
Option A is correct because CodePipeline supports automatic retry on failed actions. Enabling retry on the build stage automatically re-runs the build if it fails due to transient network issues, improving resilience.
- B
Store build artifacts in a different S3 bucket.
Why wrong: Option B is incorrect because storing artifacts in a different S3 bucket does not address the intermittent network issue causing build failures; it only changes storage location.
- C
Add a manual approval stage before the build stage.
Why wrong: Option C is incorrect because adding a manual approval stage before the build stage would introduce a manual gate, which does not automatically recover from network failures and could delay the pipeline.
- D
Configure the build stage to run multiple build actions in parallel.
Option D is correct because configuring the build stage to run multiple build actions in parallel provides redundancy. If one build fails due to a network issue, another parallel build can succeed, provided the stage is set to succeed if any action succeeds.
- E
Use a different source repository, such as CodeCommit.
Why wrong: Option E is incorrect because changing the source repository to CodeCommit does not address build stage network issues. The build stage itself still runs in CodeBuild and is subject to the same network conditions.
How to Retry Failed Builds in AWS CodePipeline for Resilience
This DVA-C02 practice question tests your understanding of development with aws services. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. A key principle to apply: retry on failed actions. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A company is using AWS CodePipeline to automate deployments. The pipeline has a source stage that retrieves code from an S3 bucket, a build stage using CodeBuild, and a deploy stage using CodeDeploy. The build stage sometimes fails due to intermittent network issues. Which TWO actions would make the pipeline more resilient to such failures?
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 retry on the build stage to automatically attempt the build again on failure.
Option A is correct because CodePipeline supports automatic retry on failed actions, including build stages. By enabling retry on the build stage, the pipeline will automatically re-run the build action if it fails due to transient issues like intermittent network errors, without requiring manual intervention. This directly improves resilience against such failures. Option D is also correct because running multiple build actions in parallel allows the pipeline to have multiple build environments executing simultaneously. If one build fails due to a network issue, the other parallel build can still complete successfully, provided that the stage is configured to succeed if any of the parallel actions succeed. This reduces the impact of intermittent network failures on the overall pipeline.
Key principle: Retry on failed actions
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Enable retry on the build stage to automatically attempt the build again on failure.
Why this is correct
Option A is correct because CodePipeline supports automatic retry on failed actions. Enabling retry on the build stage automatically re-runs the build if it fails due to transient network issues, improving resilience.
Related concept
Retry on failed actions
- ✗
Store build artifacts in a different S3 bucket.
Why it's wrong here
Option B is incorrect because storing artifacts in a different S3 bucket does not address the intermittent network issue causing build failures; it only changes storage location.
- ✗
Add a manual approval stage before the build stage.
Why it's wrong here
Option C is incorrect because adding a manual approval stage before the build stage would introduce a manual gate, which does not automatically recover from network failures and could delay the pipeline.
- ✓
Configure the build stage to run multiple build actions in parallel.
Why this is correct
Option D is correct because configuring the build stage to run multiple build actions in parallel provides redundancy. If one build fails due to a network issue, another parallel build can succeed, provided the stage is set to succeed if any action succeeds.
Related concept
Retry on failed actions
- ✗
Use a different source repository, such as CodeCommit.
Why it's wrong here
Option E is incorrect because changing the source repository to CodeCommit does not address build stage network issues. The build stage itself still runs in CodeBuild and is subject to the same network conditions.
Common exam traps
Common exam trap: answer the scenario, not the keyword
A common mistake is to confuse parallel execution with retry logic. While retry explicitly re-attempts a failed action, parallel execution can provide redundancy by running multiple independent builds simultaneously. In this context, both approaches enhance resilience, but retry is more direct for transient failures while parallel execution adds diversity.
Detailed technical explanation
How to think about this question
CodePipeline's retry mechanism works at the action level; when enabled, it retries the action up to the configured number of times (default is 1) with a backoff delay. This is distinct from CodeBuild's own retry logic, which can also be configured via the build project's 'timeout' and 'queued timeout' settings. In a real-world scenario, if the build stage fails due to a temporary DNS resolution failure or a brief S3 outage, the retry will often succeed on the next attempt because the underlying network issue has resolved.
KKey Concepts to Remember
- Retry on failed actions
- Parallel actions in pipeline stages
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Retry on failed actions
Real-world example
How this comes up in practice
A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
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 |
What to study next
Got this wrong? Here's your next step.
Review retry on failed actions, then practise related DVA-C02 questions on the same topic to reinforce the concept.
- →
Development with AWS Services — study guide chapter
Learn the concepts, then practise the questions
- →
Development with AWS Services practice questions
Targeted practice on this topic area only
- →
All DVA-C02 questions
1,616 questions across all exam domains
- →
AWS Certified Developer Associate DVA-C02 study guide
Full concept coverage aligned to exam objectives
- →
DVA-C02 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related DVA-C02 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Development with AWS Services practice questions
Practise DVA-C02 questions linked to Development with AWS Services.
Security practice questions
Practise DVA-C02 questions linked to Security.
Deployment practice questions
Practise DVA-C02 questions linked to Deployment.
Troubleshooting and Optimization practice questions
Practise DVA-C02 questions linked to Troubleshooting and Optimization.
DVA-C02 fundamentals practice questions
Practise DVA-C02 questions linked to DVA-C02 fundamentals.
DVA-C02 scenario practice questions
Practise DVA-C02 questions linked to DVA-C02 scenario.
DVA-C02 troubleshooting practice questions
Practise DVA-C02 questions linked to DVA-C02 troubleshooting.
Practice this exam
Start a free DVA-C02 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this DVA-C02 question test?
Development with AWS Services — This question tests Development with AWS Services — Retry on failed actions.
What is the correct answer to this question?
The correct answer is: Enable retry on the build stage to automatically attempt the build again on failure. — Option A is correct because CodePipeline supports automatic retry on failed actions, including build stages. By enabling retry on the build stage, the pipeline will automatically re-run the build action if it fails due to transient issues like intermittent network errors, without requiring manual intervention. This directly improves resilience against such failures. Option D is also correct because running multiple build actions in parallel allows the pipeline to have multiple build environments executing simultaneously. If one build fails due to a network issue, the other parallel build can still complete successfully, provided that the stage is configured to succeed if any of the parallel actions succeed. This reduces the impact of intermittent network failures on the overall pipeline.
What should I do if I get this DVA-C02 question wrong?
Review retry on failed actions, then practise related DVA-C02 questions on the same topic to reinforce the concept.
What is the key concept behind this question?
Retry on failed actions
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Keep practising
More DVA-C02 practice questions
- A developer is troubleshooting an AWS Lambda function that is triggered by an S3 event. The function occasionally fails…
- A developer needs to call AWS APIs from application code running on EC2. Which credential source should the AWS SDK use…
- A developer needs to allow an IAM user in a different AWS account to assume a role in the developer's account. The role…
- A developer needs to grant an IAM role in Account B read-only access to objects in an S3 bucket in Account A. The bucket…
- An API Gateway HTTP API should allow access only to users authenticated by an external OIDC provider. Which authorizer t…
- A developer needs to allow an EC2 instance to read from a DynamoDB table. Which is the best practice to grant permission…
Last reviewed: Jul 4, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.