This solution would allow the company to automate the process of updating the SDK and making it available to web clients. By adding a CodePipeline action immediately after the deployment stage of the API, the Lambda function will be invoked automatically each time the API is updated. The Lambda function should be able to download the new SDK from API Gateway, upload it to the S3 bucket and also create a CloudFront invalidation for the SDK path so that the latest version of the SDK is available for the web clients. This is the most straight forward solution and it will meet the requirements.

To enable cross-account backup, the company needs to grant permissions to both the backup vault and the KMS key in the destination account. The backup vault access policy in the destination account must allow the primary account to copy backups into the vault. The key policy of the KMS key in the destination account must allow the primary account to use the key to encrypt and decrypt the backups. These steps are described in the AWS documentation12. Therefore, the correct answer is A and E.
Reference:
1: Creating backup copies across AWS accounts - AWS Backup
2: Using AWS Backup with AWS Organizations - AWS Backup

The correct solution is to add a report group in the AWS CodeBuild project buildspec file with the appropriate path and format for the reports. Then, create an Amazon S3 bucket to store the reports. You should configure an Amazon EventBridge rule that invokes an AWS Lambda function to copy the reports to the S3 bucket when a build is completed. Finally, create an S3 Lifecycle rule to expire the objects after 90 days. This approach allows for the automated transfer of reports to long-term storage and ensures they are retained for the required duration without manual intervention1.
Reference:
AWS CodeBuild User Guide on test reporting1.
AWS CodeBuild User Guide on working with report groups2.

* Create an AWS Identity and Access Management Roles Anywhere trust anchor Create an IAM role that allows CodeArtifact actions and that has a trust relationship on the trust anchor. Update the on-premises CI/CD pipeline to assume the new IAM role and to publish the packages to CodeArtifact:
Roles Anywhere allows on-premises servers to assume IAM roles, making it easier to integrate on-premises environments with AWS services.
Steps:
Create a trust anchor in IAM.
Create an IAM role with permissions for CodeArtifact actions (e.g., publishing packages).
Update the CI/CD pipeline to assume this role using the trust anchor.
* Create a new Amazon S3 bucket. Generate a presigned URL that allows the PutObject request. Update the on-premises CI/CD pipeline to use the presigned URL to publish the packages from the on-premises location to the S3 bucket. Create an AWS Lambda function that runs when packages are created in the bucket through a put command Configure the Lambda function to publish the packages to CodeArtifact:
Using an S3 bucket as an intermediary, you can easily upload packages from on-premises systems.
Steps:
Create an S3 bucket.
Generate presigned URLs to allow the CI/CD pipeline to upload packages.
Configure an AWS Lambda function to trigger on S3 PUT events and publish the packages to CodeArtifact.
Reference:
IAM Roles Anywhere
Amazon S3 presigned URLs
AWS Lambda function triggers