Which solution will meet these requirements?

By:
In: SAP-C01
Tagged:
With: 1 Comment
A startup company recently migrated a large ecommerce website to AWS.The website has experienced a 70% increase in sales.Software engineers are using a private GitHub repository to manage code.The DevOps team is using Jenkins for builds and unit testing.The engineers need to receive notifications for bad builds and zero downtime during deployments.The engineers also need to ensure any changes to production are seamless for users and can be rolled back in the event of a major issue.The software engineers have decided to use AWS CodePipeline to manage their build and deployment process.

Which solution will meet these requirements?

Use GitHub websockets to trigger the CodePipeline pipeline. Use the Jenkins plugin for AWS CodeBuild to conduct unit testing. Send alerts to an Amazon SNS topic for any bad builds. Deploy in an in-place, all-at-once deployment configuration using AWS CodeDeploy.

Use GitHub webhooks to trigger the CodePipeline pipeline. Use the Jenkins plugin for AWS CodeBuild to conduct unit testing. Send alerts to an Amazon SNS topic for any bad builds. Deploy in a blue/green deployment using AWS CodeDeploy.

Use GitHub websockets to trigger the CodePipeline pipeline. Use AWS X-Ray for unit testing and static code analysis. Send alerts to an Amazon SNS topic for any bad builds. Deploy in a blue/green deployment using AWS CodeDeploy.

Use GitHub webhooks to trigger the CodePipeline pipeline. Use AWS X-Ray for unit testing and static code analysis. Send alerts to an Amazon SNS topic for any bad builds. Deploy in an in-place, all-at-once deployment configuration using AWS CodeDeploy.

Explanations:

Using GitHub websockets is not suitable for triggering CodePipeline; webhooks are the standard method. Additionally, an all-at-once deployment lacks zero downtime, which is a requirement.

This option uses GitHub webhooks to trigger CodePipeline, which is appropriate. It employs the Jenkins plugin for unit testing and sends alerts for bad builds. The blue/green deployment strategy allows for zero downtime and easy rollback.

While it correctly uses a blue/green deployment, GitHub websockets are again incorrectly mentioned as the trigger for CodePipeline. AWS X-Ray is primarily for monitoring and debugging, not for unit testing.

Although it uses GitHub webhooks and AWS X-Ray, the use of an all-at-once deployment configuration does not meet the requirement for zero downtime during deployments.

2025-10-08

1 Comment

  1. Patrick
    Author

    I think the answer is:
    Use GitHub webhooks to trigger the CodePipeline pipeline. Use the Jenkins plugin for AWS CodeBuild to conduct unit testing. Send alerts to an Amazon SNS topic for any bad builds. Deploy in a blue/green deployment using AWS CodeDeploy.

Leave a Reply

Your email address will not be published. Required fields are marked *

two × 1 =