Multiple development groups share a single AWS account. A senior manager wants to be notified via a third-party API call when resource usage approaches service limits, and expects the least development effort. Which solution achieves this with minimal development work?

The correct solution leverages AWS Trusted Advisor, which inherently monitors service limits and can generate events. By scheduling a Lambda to refresh Trusted Advisor checks via EventBridge, you ensure up-to-date service limit data. A second EventBridge rule can then directly capture these Trusted Advisor events when limits are approached and trigger another Lambda to notify the manager. This approach requires minimal custom logic because Trusted Advisor already performs the limit checks. The first incorrect option requires the Lambda to implement all the logic for checking resource usage against service limits, which is more development effort. The third option, using AWS Health Dashboard, is less suitable for proactive service limit monitoring; it's more for operational health and scheduled events. The fourth option, AWS Config, is powerful for compliance but requires developing a custom rule to specifically track service limits, adding more development overhead than using Trusted Advisor's built-in capabilities.