DVA-C02 Deployment Practice Question
A CodePipeline source stage should start when code is pushed to a repository, without scheduled polling. Which integration pattern should be used?
⚠ Common exam trap
Watch out — candidates often confuse manual approval (a pipeline action) with a trigger mechanism, or assume that CloudWatch Logs Insights can initiate pipeline executions, when in fact only EventBridge or webhook-based integrations provide the required event-driven, polling-free source trigger.
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
✓
Event-based trigger from the source provider/EventBridge integration
AWS CodePipeline can integrate with Amazon EventBridge to listen for repository events (e.g., push events from CodeCommit, GitHub, or Bitbucket) and automatically start the pipeline. This event-driven pattern eliminates the need for scheduled polling, providing near-instantaneous execution when code changes are detected.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Manual approval only
Why it's wrong here
Manual approval stages are designed to pause a CodePipeline execution, requiring explicit human intervention before the pipeline can proceed to subsequent stages. They are a gate within a pipeline, not a mechanism to initiate a pipeline based on an external event like a code push. Therefore, relying solely on manual approval does not fulfill the requirement of automatically starting the source stage when code is pushed to a repository.
- ✓
Event-based trigger from the source provider/EventBridge integration
Why this is correct
AWS CodePipeline natively supports event-based triggers from integrated source providers such as AWS CodeCommit, GitHub, and Amazon S3. For CodeCommit, a push to a repository branch generates an event that is published to Amazon EventBridge. An EventBridge rule can then be configured to detect this specific event and automatically invoke the CodePipeline, ensuring the pipeline starts immediately upon a code push, which is the most direct and efficient solution.
- ✗
A cron job on an EC2 instance
Why it's wrong here
A cron job running on an EC2 instance would involve a scheduled task that periodically polls the source repository for changes and then programmatically invokes the CodePipeline. This approach introduces unnecessary latency between the code push and the pipeline start, as it is not an immediate, event-driven response. Furthermore, it is less efficient and more complex to manage compared to native event-based integrations provided by AWS.
- ✗
CloudWatch Logs Insights
Why it's wrong here
CloudWatch Logs Insights is an interactive query service used for analyzing and troubleshooting operational issues by querying log data stored in CloudWatch Logs. It is a powerful diagnostic and analytical tool, but it is not designed to act as a trigger or orchestration mechanism for CI/CD pipelines. It has no direct capability to detect a code push event in a source repository and initiate a CodePipeline execution.
Go deeper
Related to this question
About these practice questions
One of 724 original DVA-C02 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.