A startup moved a high-traffic ecommerce site to AWS and now needs CI/CD that notifies engineers of failed builds, provides zero downtime deployments, and supports seamless rollbacks. Developers use a private GitHub repo and Jenkins for builds and unit testing. The team will use AWS CodePipeline to orchestrate builds and deployments. Which design satisfies the notification, zero-downtime, and rollback requirements?

The correct option leverages GitHub webhooks to automatically trigger the CodePipeline upon code changes, which is standard practice for CI/CD integration with GitHub. It uses the Jenkins plugin for AWS CodeBuild, allowing existing Jenkins unit tests to run within CodeBuild, integrating with the new AWS CI/CD pipeline. Amazon SNS is the appropriate service for sending notifications about failed builds. Crucially, blue/green deployments with AWS CodeDeploy provide zero-downtime deployments and seamless rollbacks by maintaining two identical environments and shifting traffic between them. Incorrect options: Using GitHub websockets is not the standard or most efficient way to trigger CodePipeline from GitHub; webhooks are designed for this purpose. In-place, all-at-once deployments do not provide zero-downtime or seamless rollbacks. AWS X-Ray is a distributed tracing service, not a tool for unit testing or static code analysis. This option incorrectly uses AWS X-Ray for testing and an in-place deployment strategy that lacks zero-downtime and rollback capabilities.