Activate Amazon Macie on the Production S3 Bucket:
* Macie can identify and protect sensitive data such as PII.
* Create a Step Functions state machine to automate data discovery and redaction before copying it to the development environment.
Example Step Functions state machine:
{
"Comment": "Anonymize PII and copy data",
"StartAt": "MacieDiscoveryJob",
"States": {
"MacieDiscoveryJob": {
"Type": "Task",
"Resource": "arn:aws:states:::macie:startClassificationJob",
"End": true
}
}
}
Create a Development Environment from CloudFormation Template:
* Deploy the development environment in a new account using the existing CloudFormation template.
* Schedule an EventBridge rule to start the Step Functions state machine on a weekly basis.
EventBridge rule example:
{
"ScheduleExpression": "rate(7 days)",
"StateMachineArn": "arn:aws:states:<region>:<account-id>:stateMachine:AnonymizeAndCopyData"
}
* By using Macie for data anonymization and Step Functions for automation, you ensure PII is properly handled before data transfer between environments.
References:
* Amazon Macie
* AWS Step Functions
* AWS CloudFormation Templates

The question focuses on detecting supply chain attacks that bypass CI/CD controls and result in malicious runtime behavior in the deployed serverless application. This requires runtime threat detection , not just static scanning or infrastructure validation.
Amazon GuardDuty is AWS's managed threat detection service. GuardDuty now includes Lambda Protection
, which analyzes Lambda function behavior, including network calls, IAM API usage, and other signals to detect compromised functions, crypto-mining, data exfiltration, and other malicious activity. GuardDuty automatically ingests CloudTrail, VPC Flow Logs (if enabled), and other telemetry without requiring code changes or agents. Findings are published and can be routed to Amazon EventBridge for near real-time notifications or automated remediation.
Option A (AWS WAF) only inspects HTTP requests to API Gateway and is focused on known bad patterns, not deeper behavioral anomalies. Option C (CloudFormation Guard) is focused on infrastructure-as-code validation in the pipeline, which explicitly does not help once malicious code is deployed. Option D (Network Firewall with Emerging Threats rules) protects VPC traffic, but serverless components like Lambda and API Gateway may not all traverse that firewall, and it is not targeted at function-level behavior.
Hence, enabling GuardDuty with Lambda Protection and using EventBridge notifications is the correct solution.

C). Create new ALB and Auto Scaling group resources in the new Region and configure the new ALB to direct traffic to the new Auto Scaling group. This will allow users in the new Region to access the application with lower latency by reducing the network hops between the user and the application servers.
D). Create Amazon Route 53 records, health checks, and latency-based routing policies to route to the ALB.
This will enable Route 53 to route user traffic to the nearest healthy ALB, based on the latency between the user and the ALBs.
F). Convert the DynamoDB table to a global table. This will enable reads and writes to the table in both Regions with low latency, improving the overall response time of the application

The correct answer is C.
Option A is incorrect because using CloudWatch metrics to create a custom expression that identifies the CloudWatch log groups that have the most data being written to them is not a valid solution. CloudWatch metrics do not provide information about the size or volume of data being ingested by CloudWatch logs.
CloudWatch metrics only provide information about the number of events, bytes, and errors that occur within a log group or stream. Moreover, creating a custom expression with CloudWatch metrics would require using the search_web tool, which is not necessary for this use case.
Option B is incorrect because using CloudWatch Logs Insights to create a set of queries for the application log groups to identify the number of logs written for a period of time is not a valid solution. CloudWatch Logs Insights can help analyze and filter log events based on patterns and expressions, but it does not provide information about the cost or billing of CloudWatch logs. CloudWatch Logs Insights also charges based on the amount of data scanned by each query, which could increase the logging costs further.
Option C is correct because using AWS Cost Explorer to generate a cost report that details the cost for CloudWatch usage is a valid solution. AWS Cost Explorer is a tool that helps visualize, understand, and manage AWS costs and usage over time. AWS Cost Explorer can generate custom reports that show the breakdown of costs by service, region, account, tag, or any other dimension. AWS Cost Explorer can also filter and group costs by usage type, which can help identify the specific CloudWatch log groups that are the source of the increased logging costs.
Option D is incorrect because using AWS CloudTrail to filter for CreateLogStream events for each application is not a valid solution. AWS CloudTrail is a service that records API calls and account activity for AWS services, including CloudWatch logs. However, AWS CloudTrail does not provide information about the cost or billing of CloudWatch logs. Filtering for CreateLogStream events would only show when a new log stream was created within a log group, but not how much data was ingested or stored by that log stream.
References:
CloudWatch Metrics
CloudWatch Logs Insights
AWS Cost Explorer
AWS CloudTrail

https://aws.amazon.com/about-aws/whats-new/2016/09/aws-codedeploy-introduces-deployment-monitoring-with-amazon-cloudwatch-alarms-and-automatic-deployment-rollback/