A. Convert the API Gateway Regional endpoint to an edge-optimized endpoint Enable caching in the production stage.

B. Implement an Amazon ElastiCache for Redis cache to store the results of the database calls Modify the Lambda functions to use the cache

C. Modify the Aurora Serverless DB cluster configuration to increase the maximum amount of available memory

D. Enable throttling in the API Gateway production stage Set the rate and burst values to limit the incoming calls

A. Create RDS MySQL read replica

B. Deploy the application to multiple AWS Region

C. Use a Route 53 latency-based routing policy to route to the application.

D. Configure the DB instance as Multi-A

E. Deploy the application to two additional EC2 instances in different Availability Zones behind an ALB.

F. Replace the DB instance with Amazon DynamoDB global table

G. Deploy the application in multiple AWS Region

H. Use a Route 53 latency-based routing policy to route to the application.

I. Replace the DB instance with Amazon Aurora with Aurora Replica

J. Deploy the application to mulliple smaller EC2 instances across multiple Availability Zones in an Auto Scaling group behind an ALB.

A. Use AWS Lambda to run the applicatio

B. Use Amazon CloudWatch Logs to invoke the Lambda function every 4 hours

C. Use AWS Batch to run the application Use an AWS Step Functions state machine to invoke the AWS Batch job every 4 hours

D. Use AWS Fargate to run the application Use Amazon EventBridge (Amazon CloudWatch Events) to invoke the Fargate task every 4 hours

E. Use Amazon 6C2 Spot Instances to run the application Use AWS CodeDeptoy to deploy and run the application every 4 hours.

A. Use AWS Firewall Manager to manage AWS WAF rules across accounts in the organizatio

B. Use an AWS Systems Manager Parameter Store parameter to store account numbers and OUs to manage Update the parameter as needed to add or remove accounts or OUs Use an Amazon EventBridge (Amazon CloudWatch Events) rule to identify any changes to the parameter and to invoke an AWS Lambda function to update the security policy in the Firewall Manager administrative account

C. Deploy an organization-wide AWS Config rule that requires all resources in the selected OUs to associate the AWS WAF rule

D. Deploy automated remediation actions by using AWS Lambda to fix noncompliant resources Deploy AWS WAF rules by using an AWS CloudFormation stack set to target the same OUs where the AWS Config rule is applied.

E. Create AWS WAF rules in the management account of the organization Use AWS Lambda environment variables to store account numbers and OUs to manage Update environment variables as needed to add or remove accounts or OUs Create cross-account IAM roles in member accounts Assume the rotes by using AWS Security Token Service (AWS STS) in the Lambda function to create and update AWS WAF rules in the member accounts.

F. Use AWS Control Tower to manage AWS WAF rules across accounts in the organization Use AWS Key Management Service (AWS KMS) to store account numbers and OUs to manage Update AWS KMS as needed to add or remove accounts or OUs Create IAM users in member accounts Allow AWS Control Tower in the management account to use the access key and secret access key to create and update AWS WAF rules in the member accounts

A. Use Tag Editor to tag existing resources Create cost allocation tags to define the cost center and project ID and allow 24 hours for tags to propagate to existing resources

B. Use an AWS Config rule to alert the finance team of untagged resources Create a centralized AWS Lambda based solution to tag untagged RDS databases and DynamoDB resources every hour using a cross-account rote.

C. Use Tag Editor to tag existing resources Create cost allocation tags to define the cost center and project ID Use SCPs to restrict resource creation that do not have the cost center and project ID on the resource.

D. Create cost allocation tags to define the cost center and project ID and allow 24 hours for tags to propagate to existing resources Update existing federated roles to restrict privileges to provision resources that do not include the cost center and project ID on the resource