<strong>You are just promoted to be the Scrum Master of a new team. You want to try something new and start using CodeStar because of its wonderful project management features. You plan to create a sample project using Node.js template which CodeStar provides and demo to other team members. You create the demo project successfully and the Node.js project is deployed smoothly in Lambda. The project code is in CodeCommit. Later on you want to change the lambda resource name from “XXX-GetHelloWorld” to “XXX-DemoProject”. What option should you use?</strong>

Answer options:

A.As CodeStar has used CodeCommit as its Git repo, you should pull the code from CodeCommit and make relevant changes in buildspec.yml via a Git Commit. Then CodeBuild is able to rebuild the Lambda using the updated name and CodeStar will take care of the following deployment.
B.Unfortunately, you could not change the Lambda name as you chose to use the sample template which is read-only for demo purpose.
C.In this case, as CodeStar has used CodeCommit to manage the code repo, you can modify application resource name in the template.yml file in the CodeCommit Repo. This is also the AWS CloudFormation file that models your application`s runtime environment.
D.The CodeStar template has created resources including lambda using its predefined name. To change the lambda name, you have to go to the lambda console and re-upload the code directly with the updated name.

Correct Answer – C
Instead of manually modifying an infrastructure resource, use AWS CloudFormation to model and deploy your application’s runtime resources.
You can modify or add an application resource, such as a Lambda function, in your runtime stack by editing the template.yml file in your project repository. You can add any resource that is available as a AWS CloudFormation resource. For example, you could modify the Lambda resource name in below code:
Details please refer to https://docs.aws.amazon.com/codestar/latest/userguide/templates.html#update-project.
Option A is incorrect: Because buildspec.yml is for CodeBuild instead of CloudFormation. Lambda belongs to CloudFormation stack so that template.yml is needed.
Option B is incorrect: Because you can still modify the sample code by changing the code in CodeCommit or Github repo.
Option D is incorrect: For CodeStar, although manually changing Lambda resource could work, it is not a good practice. Managing resources in CloudFormation is suggested so that the structure is regarded as Code and can be properly managed.