What should the development team do to meet these requirements?
Add a Resources section to the CloudFormation templates that contains AWS::Lambda::Function resources.
Add a Mappings section to the CloudFormation templates that contains AWS::Serverless::Function and AWS::Serverless::API.
Add a Transform section to the CloudFormation templates. Use the AWS SAM syntax to define the resources.
Add a Parameters section to the CloudFormation templates that specifies the relevant AWS SAM Globals section.
Explanations:
Adding a Resources section with AWS::Lambda::Function resources is not sufficient for AWS SAM. AWS SAM requires a specific Transform section to process the SAM syntax and recognize the AWS::Serverless resources.
The Mappings section is used for defining static values to be referenced in the template, but it does not directly relate to defining serverless resources. AWS SAM uses a Transform section to define AWS::Serverless::Function and AWS::Serverless::API.
Adding a Transform section is necessary for AWS SAM. This section allows the use of AWS SAM syntax, enabling the definition of serverless resources like AWS::Serverless::Function and AWS::Serverless::API. This is the correct approach for creating serverless infrastructure using AWS SAM within CloudFormation templates.
The Parameters section is used to declare input parameters for the CloudFormation template. While Globals can be specified for resources, they must still be defined within a Transform section for AWS SAM to be valid. The Parameters section alone does not enable the use of AWS SAM functionality.
From my perspective, the answer is:
Add a Transform section to the CloudFormation templates. Use the AWS SAM syntax to define the resources.
My best guess is:
Add a Transform section to the CloudFormation templates. Use the AWS SAM syntax to define the resources.