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:
This option uses GitHub websockets, which is not a standard method for triggering AWS CodePipeline; GitHub webhooks are required. Additionally, it proposes an in-place, all-at-once deployment, which does not ensure zero downtime.
This option correctly uses GitHub webhooks to trigger the CodePipeline. It incorporates Jenkins for unit testing and sends alerts for bad builds via Amazon SNS. It also uses blue/green deployment with AWS CodeDeploy, which allows for zero downtime and easy rollbacks.
Similar to option A, this option uses GitHub websockets instead of webhooks. It incorrectly mentions AWS X-Ray for unit testing, as X-Ray is primarily for tracing and monitoring rather than unit testing. Although it suggests blue/green deployment, the triggering mechanism is not appropriate.
While it correctly uses GitHub webhooks, it suggests using AWS X-Ray for unit testing, which is not its intended purpose. It also opts for an in-place, all-at-once deployment, which does not ensure zero downtime.