Accompany wants to track how many Amazon EC2 instances are running and automatically request a service quota increase when the instance count reaches a defined threshold. Which approach satisfies these requirements?

The correct approach involves using Amazon CloudWatch to monitor the Running Instances metric within the AWS/EC2 namespace, which directly reflects the number of running EC2 instances. Service Quotas provides metrics for current usage, making it suitable for monitoring. When this metric crosses a defined threshold, a CloudWatch alarm can trigger an AWS Lambda function. This Lambda function can then programmatically interact with the Service Quotas API to request a quota increase. Incorrect options: AWS Config rules are for evaluating resource configurations against desired settings, not for monitoring real-time service usage metrics or directly requesting quota increases. The AWS Health Dashboard provides personalized views of AWS service health and scheduled activities, not real-time metrics for service quota usage. AWS Trusted Advisor offers recommendations for cost optimization, performance, security, and fault tolerance, including some service limit checks, but it doesn't provide real-time metrics for direct CloudWatch alarming to automate quota increase requests.