AWS DevOps Engineer Professional Practice Test

What are the Build action integrations available for AWS CodePipeline?

1. AWS CodeDeploy, GitHub, Jenkins, AWS Lambda

2. AWS CodeBuild, CloudBees, TeamCity, and Jenkins

3. Jenkins, AWS Lambda, AWS ECS, AWS CodeStar

4. AWS CloudFormation, AWS CodeBuild, GitLab, AWS CodeDeploy

The correct answer is: AWS CodeBuild, CloudBees, TeamCity, and Jenkins

The correct answer highlights the most applicable integrations available for the build action in AWS CodePipeline. AWS CodeBuild is a fully managed build service that compiles source code, runs tests, and produces software packages that are ready to deploy. By integrating CodeBuild into CodePipeline, you can automate the build process efficiently. The inclusion of tools like CloudBees and TeamCity, alongside Jenkins, is notable as they represent popular continuous integration (CI) tools frequently utilized in DevOps workflows. While Jenkins is well-known for its extensibility and flexibility in performing build actions, CloudBees and TeamCity also offer robust features that can seamlessly integrate into the AWS ecosystem. The other options contain a mix of services that either do not directly function as build actions in CodePipeline or include integrations that are not typically categorized under build services. For instance, AWS CodeDeploy primarily serves a deployment function rather than being a build service. Similarly, GitHub can be a source provider but does not perform build actions on its own within CodePipeline, while AWS Lambda is used for serverless computing and lacks the broader scope of build integration required in this context.