You have a pipeline configured in the AWS CodePipeline service. You want to add a new stage that invokes a Lambda function to test the new build. In this CodePipeline stage, a parameter needs to be passed to the Lambda function and its value should be a valid URL such as http://mytest.com.au. Which of the following methods would you select to pass the parameter from CodePipeline to the Lambda function?

Answer options:

A.Configure the parameter in the user parameters of the new CodePipeline stage. In the Lambda function, retrieve the parameter value from the JSON event that CodePipeline sends to Lambda.
B.Launch a CloudFormation stack in the Lambda function and the parameter is passed from CodePipeline to the CloudFormation stack through the “!Ref” function.
C.Add the parameter in the new CodePipeline stage. In the Lambda function, the parameter becomes an environment parameter. For example, if the Lambda language is Python, the value can be retrieved through “os.environ[`Parameter_Name`]”.
D.Create an API Gateway that passes a querystring to the AWS Lambda function. Configure the CodePipeline stage to invoke the API Gateway.

Correct Answer – A
Option A is CORRECT because you can configure the UserParameters in the CodePipeline stage where the Lambda function is invoked. UserParameters is included in the JSON event sent to Lambda and can be fetched by the Lambda function.
Option B is incorrect because there is no need to launch a CloudFormation stack and the parameter cannot be fetched through the “!Ref” function.
Option C is incorrect because the parameter is included in the JSON event sent to Lambda by CodePipeline. It is not an environment parameter for the Lambda function.
Option D is incorrect because an API Gateway is not required since CodePipeline can pass a parameter to Lambda. Besides, API Gateway is not a supported service that CodePipeline can directly invoke.
Reference:
https://docs.aws.amazon.com/codepipeline/latest/userguide/actions-invoke-lambda-function.html.