A team is building up microservices using several Lambda functions. The team consulted you on how to build a pipeline for the project. The requirement is that the pipeline uses AWS CodePipeline which can continuously build the Lambda code and deploy the applications in AWS whenever there is a new Git commit by a team member. In AWS CodePipeline, which combinations of services are valid for this scenario? (Select TWO.)

Answer options:

A.Source stage (CodeCommit), Build stage (CodeBuild), Deployment stage (CloudFormation) 
B.Source stage (GitHub), Build stage (Jenkins), Deployment stage (Code Commit)
C.Source stage (Bitbucket), Build stage (CodeBuild), Deployment stage (Amazon ECS)
D.Source stage (Github), Build stage (Jenkins), Deployment stage (CodeDeploy)
E.Source stage (CodeCommit), Build stage (Travis CI), Deployment stage (CloudFormation)

Correct Answer – A, D
In CodePipeline, various services can be integrated into different stages which are very flexible for users. However, for this particular case, not every service is suitable, although it may be a valid one for other scenarios. Refer to
https://docs.aws.amazon.com/codepipeline/latest/userguide/integrations-action-type.html
for the integrations.
Option A is CORRECT: Because CloudFormation can easily deploy Lambda functions with AWS SAM templates. The AWS SAM templates come from the build stage.
Option B is incorrect: Because the deployment stage is not a valid one for this case.
Option C is incorrect: Because ECS in the deployment stage is inappropriate as it deals with EC2 instead of Lambda.
Option D is CORRECT: All stages have suitable services according to the above link.
Option E is incorrect: Because Travis CI is not a supported service in the build stage.